Jim Young

Just a follow-up on my issue above. MSE fixed the issue with a new username/password for my purchase today. Pretty fast response to my request for support. Best regards,

And so it does for me too. I wouldn't worry about it since it evidently is temporary and no longer exists. Best regards,

No need to remove all add-on's and reinstall FSX yet. It if continues, Move your FSX.cfg, dll.xml (if the file is in the same folder as FSX.cfg as it is not installed by default). Also move the scenery.cfg to a temporary folder. When you restart FSX, the FSX.cfg and scenery.cfg will be rebuilt to the default. If no problems after doing this, then the problem was in your fsx.cfg or an addon scenery. Move your Scenery.cfg that you moved back to the scenery.cfg folder and see if this still stops the crashes. If so, then most likely the crash was in the fsx.cfg. If the crashes continue even after doing this with the MSVCR80.dll as the faulting module, then try uninstalling Microsoft Visual 2005 through your Add/Remove programs and then download and install the Microsoft Visual 2005 w/SP1 again (link to the 2005 Microsoft Visual is in the AVSIM CTD Guide). The fact running sfc \scannow indicates you had corrupted Windows files that hopefully were fixed when the program completed. You can run it again to make sure everything is fixed. Best regards,

This is normal. They are all in different folders. I have seen where sometimes, a developer, will modify the dll to fit their products installation. Best regards,

I would recommend you run a driver update program like the one I use, Driver Booster. It will scan your system for outdated drivers and, if any are found, will download and install the updated drivers. This is important if you have Windows 10 or Windows 8.1 installed as manufacturers are constantly updating their hardware for these new platforms. It may not be your joystick drivers but it could be one of the USB ports that needs updating. You can also try removing the joystick from the USB connection, trying another USB port or waiting a few seconds and plugging it back into the same USB port. Best regards,

The AVSIM CTD Guide has guidance for using the AppCrashView program and how to use the Event Viewer to diagnose your problem. An AppHang normally will not show any faulting module so you have to investigate the scene of the crime yourself. There is no known 'one' solution for AppHang's. It all depends on where the apphang hung. You say after 10 to 30 minutes into a flight it freezes. The AVSIM CTD Guide (link in my signature) has guidance for freezes: 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,

According to the AVSIM CTD Guide: Microsoft.net Repair Tool – Whenever you get a Microsoft.net error or Microsoft Visual C++ error (faulting module), run the Microsoft.net repair tool. The MSVCR80.dll belongs to Microsoft Visual C++ Redistributable 2005, SP1. It is the correct version and up-to-date. Switching aircraft while FSX is loaded is not advisable. For instance, the Phenom 300 installed Microsoft Visual C++ 2010 in order for the product to run. You then switched to another product, maybe the default, and that required another version the developer of that aircraft used to make sure his product worked. That's my theory that could be correct or I'm totally off base. Still, every product installs the version of the Microsoft Visual needed for their application to run. Microsoft Windows is basically saying "hey! Make up my mind!"... It appears you might have had a side by side error too. Some individuals have fixed this problem by placing one of the versions of the uiautomationcore.dll in their main fsx folder. See page 8 of the AVSIM CTD Guide (see link in my signature) for links to the two versions of the uiautomationcore.dll and more information. Since you have FSX installed in the default folders, you want to make sure you have UserAccessControls disabled. This program may have denied access to you as the user when you switched aircrafts. Best regards, Best regards,

I'm sorry but I had to remove most of the posts in the final page of this discussion as the discussions clearly have gone South. The OP wanted to know if there is a reason to get the CJ2 if he owns the S550. I think that has been mostly resolved so I will now close this topic. Best regards,

Once our website is upgraded, we plan to post some of the best images on the front page and in the forums if possible. Much like some other sites do such as FTX. We are also thinking of some kind of monthly contest but contests are difficult to manage and you want to be as fair as possible. Best regards,

8" of snow is not good for driving even in an SUV! Hope it goes away for you soon. I use mine to get to/from the golf course every day but today it is in the 30's so it's sitting in the garage. You have had some exceptional images lately and causing members to post in the forums about the "blurries", "no night lighting" and "why do I have popcorn clouds" as your photos are nearly perfect. No blurries, night lighting looks great and beautiful night time clouds. You're an excellent aircraft painter too so suspect you got a lot of your creativeness with that hobby too. Keep it up! AVSIM loves you! In fact, I would be remiss if I did not mention all of the other members here posting images that are absolutely stunning and keeps this hobby going! Work hard! Best regards,

Bought this product over the weekend. I am having problems installing it. The username and password they provided to download Texas Northeast was the same for MSE4X Texas Southeast (which I also purchased) and their system will not accept it. I was just wondering if anyone else has this problem. I sent an e-mail to MSE telling them of my problem and hope to hear from them soon. Best regards,

Some beautiful images you are posting here Rich! Love the night lighting too! When do you find time to drive the StingRay? :smile: Best regards,

Flight One has GEP3D specifically developed for P3D and it works great. I also use it with UTX. GEX will not work in P3D and installation would be in violation of their EULA as it would not be possible to install GEX in P3D using the GEX installer. This ends discussions of the GEX/UTX EULA's. Any additional posts about it will be removed. Best regards,

You should see the link to the Scenery Library - Best regards,

Good to hear you were able to solve your problems. The 1402 error is very common but complicated to fix in most cases. Thanks for your comments about the AVSIM community. We are proud to have you aboard too. It is the largest so you are surrounded with a lot of friends in the community. Like in all communities, there are rules everyone must abide by and many of them are posted in the Terms of Service located under the Forums tab above (or the link is in my signature). There is another general rule throughout the Internet and here too and that's 'shouting'. When you type in all caps, that is considered 'shouting' and it is rude to shout in forums - https://newrepublic.com/article/117390/netiquette-capitalization-how-caps-became-code-yelling. I hope you will not do this in the future as many of our members do not like it. In the future, your post or topic will be removed from view if you use all caps. Thanks for your cooperation. We welcome you to the community and hope you enjoy your visits. Thanks for providing a solution to your issue. Perhaps it will help many others in our community. Best regards,

Topic closed as this is the Screenshot Forum. Post your screenshots in separate topics. I will now have to go through this topic and split the screenshots from this topic to separate topics. Lots and lots of work.... So, if you have a topic to show what the great night lighting from Night Environment shows, then post them separately. Please confine your issues with something in the main forums. Thanks for everyone's cooperation. Best regards,

Perhaps the following link will help - http://www.avsim.com/topic/473093-reshade-dx10-fixer-ctd-dxgidll/

The dll.xml is loading some of the tools in the SDK. Are you a developer? I would move the dll.xml to a temporary folder or rename it to dll.old. It is not needed in your investigation of your CTD. Did you move the dll.xml to a temporary folder and run fsx again? FSX will use the .net the developer (Microsoft) used when they developed FSX. FSX needs version 1.1 (which was installed when you installed FSX/Acceleration) or version 2.0. Either version will work just as well as the other. If you did not have 1.1 or 2.0 installed, then there would definitely be a problem. We had one member a couple of years ago who wanted to get rid of his "old" dotnets and Microsoft Visual 2005 and 2008 as later versions had been installed on his system and he wanted to clean things up. I told him not to do it as dotnets and MIcrosoft Visuals are not backward compatible (according to Google) but he went ahead and uninstalled the old stuff. FSX would not start up. Your crash is not abnormal. Many members have this type of crash. It's just that there is no solution to the problem. You have to investigate what is happening on YOUR computer system. What fixed a problem on a computer belonging to someone else may or may not work on your computer. For instance, we almost have to go to the basics of computing to figure out what is wrong with your installation. That means moving your fsx.cfg, your dll.xml, your exe.xml (if you have it), and your scenery.cfg to a temporary folder and then restart fsx. This brings FSX back to the default installation and your fsx should now run (now that we know you have to proper Microsoft Visual and dotnet installed). If not, then, it is a problem with Microsoft Windows as it would be impossible for it to be a problem with FSX. This means you need to make sure your UserAccessControls are disabled and any anti-virus program is not running or scanning FSX when you run it. If UserAccessControls were enabled when you installed FSX, this may be the problem. If any anti-virus program was enabled when you installed FSX, this could be the problem. Since you do not appear to have any addons installed, I would uninstall FSX per the uninstall guide and then reinstall it using the reinstall guide - http://support.precisionmanuals.com/kb/a87/how-to-uninstall-and-reinstall-fsx.aspx. I would do this only if deleting or moving your fsx.cfg as recommended above in this post did not fix the problem. Make sure any anti-virus program has been disabled. Anti-virus programs - Bad! Make sure UserAccessControls are disabled too. Best regards,

Perhaps this will help - http://www.avsim.com/topic/467576-ctd-p3d-v25-xactengine3-4dll/ Best regards,

Hi Ed, If you have a 64 bit operating system, your application (FSX/P3D) will use up to 4GB's of VAS. If you have a 32 bit Windows Operating System, FSX can only use up to 2GB's of VAS but someone came up with a "switch" that could make FSX 'see' up to 3GB's of VAS. It was called the /3GB switch or the UserVA switch. This was years ago and most individuals have the 64 bit Windows operating system installed (if not, you should). In any case, there is no switch on your computer. You have to use the run command and tell the system to use up to 3GB's. Here's one link that provides info on how to employ the switch in Windows 7 - http://scorpion.tordivel.no/help/GettingStarted/3gswitch.htm Best regards,

Whenever FSX fails to load to the setup screen, it means you have a corrupted, outdated, or missing module. The first thing FSX does when it starts up is to load the dll.xml and the exe.xml. Many developers provide updates to their modules regularly. Most crashes occur if you have the wrong version of the FSUIPC utility as it is updated frequently to fix bugs found when products are updated such as PMDG aircraft, the RAASPRO utility, ASN, etc. What got me confused was the fact your AppCrashView report appeared complete. You would not receive a complete AppCrashView report in most cases if the sim crashed at startup. Best regards,

The AVSIM CEO and Board of Directors' have modified the signature rules to eliminate links to any commercial website or flight simulator (FS) related websites. You may still have up to five links to your personal website or blog or to other members personal websites or blog that display, for instance, Flight Simulator images and videos. You may also have signature banners (no change) included in your signature that shows your favorite product but the banners must not contain active links to any websites. You can also have up to five lines of text and many members use that to provide information about their system specifications and their favorite FS products as well as their name (required for posting in the PMDG Forum hosted by AVSIM). The signature rules are located under the Forums tab above or at the following link - http://www.avsim.com/index.php/AVSIM%20Pages/sig.html We have had some members who have tried to abuse our rules and place active links in banners or place links to virtual airlines, FS stores or FS product pages (these links are still allowed in topics when notifying events, new products, or updates). If your personal website has links to FS stores or FS products, then do not place the link in your signature space. If you want to advertise your virtual airline or product, please contact our Advertising Department. Signatures placed at the end of our messages set us apart from other members of the community and provide an opportunity to tell your fellow members something about yourself. They are important parts of our "persona" within the AVSIM Community. We encourage you to create a unique and informative signature for your account. Since 1996, we have learned (and are continuously learning) important lessons about signatures and user implementation of them. Please abide by these requirements.

There is something in your system registry which is not allowing you administrative privileges/permissions. This is not a FSX SP1 issue but a Microsoft Windows issue. Here is an excellent tutorial for locating and fixing each key - http://www.okino.com/conv/changing_windows_registry_permissions.htm If this does not work, you are going to have to reformat and reinstall Windows and then FSX. Best regards,

By default, it's only 8TB's for each 64 bit process. So, if FSX, FSX-SE, and/or P3D were converted to 64 bit, it would be essentially unlimited as there's not too many terebyte SSD's or HDD's yet available. Best regards,

Thus the pinned topic. For a long time I thought they were extensions to AVSIM until Tom abruptly informed me they were scams. Best regards,