Jump to content

Jim Young

In Memoriam
  • Posts

    18,287
  • Joined

  • Last visited

  • Donations

    200.00 USD 

Everything posted by Jim Young

  1. I would send a bug report to the developers of Concorde X so they can fix this anomaly in future updates. Best regards,
  2. You're not the only one. This is one of the most common errors reported here since FSX was first released. Something gets caught in memory and messes up the install. I would scan your system for corruption - https://support.microsoft.com/en-us/kb/929833 If that does not work, you may have to do a clean install of Windows 10 (ugh!). Best regards,
  3. It takes a super long time for the Navigraph loading. If you believe it really is hanging, then reinstall. Make sure the navigraph data is in the right folder - K:\FSX\CarenadoNavigraph\Navigraph\NavData. There should be a PROC folder under NavData which contains the SID/STARS. Best regards,
  4. Do not need to purchase Smart PC Fixer. That's just another name of a commercial product that does things like in CCleaner. So, did you try the fixes on the Microsoft link - https://support.microsoft.com/en-us/kb/910816 ? They do have a fixer whereby they rename the installshield folder for you and you can try to reinstall. Best regards,
  5. Members are reminded to follow the AVSIM rules regarding using the signature space in your profile - http://www.avsim.com/index.php/AVSIM%20Pages/sig.html Members are encouraged to place information about their computer system in their signature as well as their favorite flight simulator and the addon's installed with your computer. Please remember you cannot exceed five lines of text. Placing your system specs in your signature will help other members assist you in the event you have problems with your flight simulator. It may also help members decide on future computer hardware purchases when they see what others are using to run their simulator. A sample entry of system specs is in my signature. Best regards,
  6. Yes. Do not uncheck the scenery where you won't be flying. It will not load unless you are within approx 100 miles of the scenery. If it is photoscenery (and Orbx/FTX stuff is not), then that scenery should be disabled if you are not flying in that region as all photoscenery enabled will load. If you want verification of my comments, run Process Monitor but configure it to only monitor FSX, FSX-SE, P3D, or X-Plane as shown in the AVSIM CTD Guide, page 4: Startup FSX/P3D/FS9, as appropriate, to the Setup Screen. Open Process Monitor Click on the Filter tab and then Filter…. Click on Architecture and scroll down to Process Name Click on blank box and select FSX/P3D/FS9, as appropriate Click Ok or Apply The scenery configuration editor should not be used to disable/enable Orbx/FTX stuff too. That could cause problems. If you want to disable/enable Orbx/FTX stuff, you need to use FTX Central otherwise your scenery.cfg will get corrupted. Best regards,
  7. My mistake. In your OP, I failed to read where you were indicating post #5 in the link you had posted. When I went to that link you posted, I immediately saw the following: https://mega.nz/#!rgRxWY6J!kvSfOr6tfAIanzkXkqZzshTU7iTooTjxfXt-LXdkAdQ Thus I thought you were having a problem posting a link. I did not read your post completely and that was my error. I have no idea why post #5 appeared like it did. I have little or no knowledge of computer coding. Perhaps one of our members or another moderator who has computer code knowledge will be able to provide you an answer. Best regards,
  8. You have to provide specifics in order for us to help. It does not occur all of the time but in just certain searches. What did you do to get the error? I need to replicate in order to see if there is a problem with our system or with your system. Best regards, Okay, I'm getting the error message every time I'm on the main forum page and then enter flight as the search term (and any word) so there is definitely a problem. I'll pass it to our tech. Thanks to all for bringing it to our attention. Best regards,
  9. I apologize for the confusion. I made my comments because of your following comments, "Editing a post often (well, sometimes, not often, but this is by no means a one off) causes this. As a courtesy to readers I clean it up in a text editor, but it can take a while..". Is your problem solved with my recommendation? Best regards,
  10. That's what I was talking about too. Editing one's own post. You can do that w/i 24 hours (I think) but outside that it is not possible. Best regards,
  11. I get this message all of the time and I'm an Admin! There is obviously a glitch somewhere on our system. In order for me or anyone else to assist you, please provide us exactly what you tried to do. For instance I clicked on the Search button and looked for Store (meaning the AVSIM Store). I immediately got the message because the information and any links to the Store have been removed as we shutdown the store some time ago. I then went into the Advanced search and click on to search just the Store and it came back with there were no hits for what I was searching for. So we need something to replicate your error message so that our techs can take a look at it and try to duplicate. Best regards,
  12. Whenever you post a link (or edit a link), you should click on the "link" button in the menu and copy and paste the link into the link box. That allow integration using BBCode. I did have HTML format authorized where allowed in the settings and removed that option in the forum settings. Wondering how you have the ability to edit a post. Only moderators are allowed that option. Best regards,
  13. It's obviously caused by the Estonia Migration Tool (maybe, perhaps). P3D works great out of the "box" and then you begin to add addons that were not made for P3D and P3D freezes or crashes (whichever comes first). IMHO, you should never ever fly a 10 hour flight with a product that was added using the EMT. Not even a flight longer than 2 hours as you will be frustrated. If there was no event in the Event Viewer, then that means it was caused by your computer system. Your system cannot handle what is being thrown at it. It cannot render textures fast enough. It does not have the virtual address space to accomplish a task. Of course there will be no Event as there was no memory available for your computer to record the event. You simply ran out of VAS and the AVSIM CTD Guide provides some solutions for running out of VAS like turning down all of your settings. You had everything running for 10 hours with no problems whatsoever so you can be almost assured none of your addons, alone, caused your crash. You just ran out of VAS. I run out of VAS after 2-3 hours as I begin my descent about two hours out and I'm flying into a storm and hi res airport scenery. I get an OOM 99.9% of the time. There is no fix for this problem for me other than to turn off ASN and use a default weather setting and turn down my P3D.cfg settings. I have REX too and you cannot use 32 bit textures with much success as it can bring your system to its knees pretty quick. There is currently no computer in the world that can run P3D or FSX for any length of time with high settings and lots of eye-candy like addon scenery and commercial weather engines. I think you should only use ASN for local area flights to place flying in rough weather but never any long flights. Again, this is not P3D's issue, this is a computer system issue and it occurs in FSX and FSX-SE too. Microsoft only provides 4 GB's of virtual address space (VAS) with their operating systems. When VAS runs out or gets very low, your application will freeze or crash. You can monitor the amount of VAS usage by following the instructions in the AVSIM CTD Guide using a freeware utility called FSUIPC. Best regards,
  14. Glad that fixed your problem. A lot of people keep their old fsx.cfg and use it in a new install and the "experts" (I'm not one of them), say that you should never use an old config and I think they are right. Let's hope FSX continues to work great for you and you can enjoy this little hobby. Best regards,
  15. I agree. I also recommend getting the following app - http://blog.ultimateoutsider.com/2015/08/using-gwx-stopper-to-permanently-remove.html Best regards,
  16. You had a crash caused by a StackHash. There is no module on your computer system named StackHash so no need to look for it. If the StackHash is shown as the faulting module, it will have four characters next to it like StackHash_0a9e. That represents the memory address of where the fault occurred. Do not try to look for it. You will not find it. There is no known solution to BEX/StackHash errors other than reinstalling Windows and P3D but some have accidentally fixed their problem by lowering fsx or P3D display driver settings, rebuilding the FSX or P3D.cfg, changing voltages/overclocking settings in the BIOS, disabling all scenery add-ons in the Scenery Library, and/or shutting down FSX only in Windowed Mode and starting up in Windowed Mode but never in Full Screen. If you are not overclocked or have not messed with the BIOS, you can forget about changing voltages/overclocking. There are a lot of addons to P3D that were made compatible with P3Dv3.1 and there are many that can be installed manually but not really intended for installation in P3D. If this is the case for you, then moving your scenery.cfg to a temporary folder and letting P3D rebuild the config back to the default scenery may help you find a fix for your problem. If there is no StackHash using the default scenery, then the problem is most likely associated with an addon installed into P3D. You can also move your dll.xml to a temporary folder. This file will not be rebuilt as it is not needed in P3D and is used by developers to load their modules into P3D. The only bad thing about moving this over to a temporary folder is the fact your addon modules, like FSUIPC will not load and may by needed by an addon. StackHash errors don't happen all of the time and you might see another error later on showing the faulting module as the ntdll.dll. It is all associated with memory. The fact they don't occur every time can be frustrating but, the addons, the aircraft, and modules loaded when you received a StackHash or ntdll.dll error can be a clue. For instance, if you had addon scenery in Europe and you were flying around in California, you can pretty much discount scenery in Europe. I always suggest one try to bring their installation of P3D back to the default as P3D runs great when you first run it then you mess everything up and install addons and things start going downhill after that. To bring your installation back to the default, you move the p3d.cfg, the scenery.cfg, and the dll.xml and exe.xml to a temporary folder. The p3d.cfg and scenery.cfg will rebuild. In the AVSIM CTD Guide, page 2 (see link to guide in my signature), we discuss moving the dll.xml or disabling all the modules within and then enabling them one at a time until the StackHash or NTDLL.dll error shows up again. That's a long investigative process though if you have a lot of modules. Still, you are going to have to investigate "the scene of the crime" as there is no solution that fixes this problem for everyone. I would also suggest downloading one of those driver updater programs as a bad USB port driver might be the cause. Perhaps you plugged your Mouse or joystick in a bad port. I use Driver Booster which is freeware but has a lot of nags to get you to purchase a license. Still you can download the new drivers and install them w/o purchasing a license. Just a lot of nags. In these days where manufacturers are slowly but surely coming up with drivers for Windows 8 and now Windows 10, outdated drivers could be the real cause and a fairly quick fix. Hope this helps. Best regards,
  17. If I understand the OP correctly, P3D does not load to the startup or setup screen. Whenever P3D (or FSX) does not load to the setup screen, the problem is with your dll.xml (located in the same folder as your P3D.cfg). You simply move the dll.xml to a temporary folder, restart P3D and see if this fixes the problem (it will). This means you have a corrupted entry in your dll.xml and you have to find the one that is corrupted. The AVSIM CTD Guide provides instructions on locating a corrupted entry in your dll.xml (see page 2)(link to the AVSIM CTD Guide is in my signature). Best regards,
  18. See page 12 of the AVSIM CTD Guide (link in my signature): Freezes During Flight – Freezes are most commonly caused by – High application/display driver settings. Check. High settings within commercial weather programs like REX, ASN, and OPUS. Check. Some raise settings to the highest texture settings (4096 HD) within weather programs and/or texture programs like REX. This coupled with high applications LOD_Radius and Texture_Max_Load settings may take up too many resources and application will freeze. Complications with weather server updates. Application may try to update the weather and the weather server is down or cannot comply with a request. Running out of Virtual Address Space (VAS) especially on one hour or longer flights (see VAS/OOM discussions). Bad tweaks. BufferPools and or Affinity Mask are most often attributed to freezes. Rebuild the application configuration to see if this fixes the problem or disable the tweaks. ENBSeries Module – DirectX hack for better visuals. SweetFX Module – DirectX hack for better visuals. Best regards,
  19. This should be unchecked. Make sure you have all of your hardware drivers up-to-date. I use the freeware Driver Booster which does not require a license but has many nags to try to get you to buy a license. Still it is very accurate so I got an annual license. This has fixed this problem for a couple people last month. Move the dll.xml to a temporary folder and make sure the problem is not associated with any of the modules loading in this file at startup. Best regards,
  20. I plan on being a truck driver. Thanks for the heads-up. Best regards,
  21. In the main forum showing all topics - Best regards,
  22. One of the things I like about the FSUIPC VAS setup is the fact you can tick the "log" option and, when you shutdown P3D, you can open up the FSUIPC.log and it will show you the amount of VAS used when P3D was loaded to the setup screen and then loaded when you start up the flight. I use it for testing various aircraft/scenarios. For instance with real weather, w/o weather, with the PMDG 777, with the Phenom 300, etc., etc. I can save the fsuipc.log to something like KSTL to KORD_PMDG777. Then I can see who's eating up what and where. The FSUIPC also has a warning system that tells you when you are running out of VAS and will show this information in the fsuipc.log too. My VAS monitor is located at the top of left corner of my monitor and I can monitor the VAS usage constantly. It works for the freeware version too! Best regards,
  23. http://www.simforums.com/forums/setup-utx-all-versions-update-new-lights-settings_topic46147.html Look down in this topic for UTX Settings for Performance and Visuals... Best regards,
  24. The only 64 bit simulator is X-Plane. FSX, FSX-SE, P3D are all 32 bit applications. Best regards,
  25. That's always good to know. I don't own any of the Aerosoft stuff or the Q400 so never saw the issue(s). I own most of the Carenado and PMDG stuff and no problems whatsoever with those aircraft (except learning to fly them). Best regards,
×
×
  • Create New...