Jim Young

Did you rename your FSX.cfg (so that you can bring it back if it does not work), restart FSX and let the config rebuild. Do not mess with the settings. Go fly.

Split from another topic.

Did you ever read the suggestions in the AVSIM CTD Guide, page 37, regarding the weather.dll? These recommendations were collected from AVSIM and searching all the other flight simulation websites. See my signature for a link to the CTD Guide. Best regards,

Aw, a manned drone! Thanks for posting. Best regards,

There is no known fix to this error other than fsuipc trapping the error. I think there is a problem with a texture in one of the sceneries but an attempt to find a solution went to 41 pages and over 600 responses until Pete gave us the fix to trap the error (does not work for every g3d.dll error but most of them) - http://www.avsim.com/topic/353179-g3ddllhelp/page-41 If you get them and you cannot stop them using fsuipc, then I recommend uninstalling any and all scenery you added just before you started getting the error. It is obviously not the fault of FSX but the fault of an addon.

It should trap the error whether it is the registered or unregistered version. If you are flying in the Pacific Northwest with Orbx/FTX scenery, suspect that as the fault.

Only if it is employed properly. The first things you look at when you have a freeze or crash are high settings and tweaks because it most likely did not occur when you had default settings.

Get rid of the AffinityMask and Bufferpool tweaks. Tweaks bad! You do not need to delete the entries, just comment them out so they do not load. You comment them out by place two slashes before the entries: [JOBSCHEDULER] //AffinityMask=84 [bUFFERPOOLS] //Poolsize=0 Also comment out these two entries. Go fly! Jim

Agree. AS16 uses its own Simconnect. It does not use the Simconnect that comes with P3D and FSX. Legacy simconnects are not needed for AS16 (or ASN). If you are getting the error at startup, then SteveW is correct. As stated in the AVSIM CTD Guide, if you get an issue at startup, there is a problem with your dll.xml. If you move your dll.xml to a temporary folder, FSX should start up without any problems. You just need to find the corrupted entry in the dll.xml. The module linked to by the dll.xml may be corrupted too. The AVSIM CTD Guide provides guidance on how to disable a module until you find the one that is causing your problems. I would suspect the last 2 or 3 entries. Best regards,

Sad. At least he got to spend most of his life living his dream of building and flying this aircraft. Now, sadly they are both gone. A military fighter pilot and test pilot, he had the experience but something obviously went wrong. Maybe he had a medical condition or the aircraft failed as he had successfully completed two previous flights. May he rest in peace knowing he got to do what he wanted to do and succeeded in living his dream of building the aircraft and then flying it. I hope they find out exactly what went wrong. Thanks for posting. Jim

Definitely not a fix for the AppHangB1 "Unknown Module" Freeze. The AVSIM CTD Guide has some suggestions that I picked up from AVSIM Forums and other flight simulator websites but it is pretty much a hit or miss solution. Best regards, Jim

I do not believe in this tweak (or any tweak). The real tweak is "tweaking" your settings and "tweaking" your computer system so it is running well. The AVSIM FSX Configuration Guide (see link in my signature) are my FSX settings and tweak recommendations. Best regards,

SteveW is one of the experts here regarding the employment of the AffinityMask tweak. It comes under [Job Scheduler] (which is NOT in your default config). Perhaps the following link will help - http://www.avsim.com/topic/444793-one-tweak-to-rule-them-all-how-to-set-affinity-mask-correctly/. This is actually not a tweak but an fsx fix. Microsoft forgot to put it into Acceleration/SP2 when those updates were released. AppHang occur frequently and most likely a cause external to FSX. They do not happen all of the time. In the Event Viewer, you might want to look at other issues that are creating a critical error or a warning. See page 7 of the AVSIM CTD Guide (see link in my signature) for information on how to look at your Event Viewer properly. Hopefully the problem is fixed with the input of the highmemfix=1 fix. Best regards,

I do not see anywhere on the product page where it is compatible with FSX-SE. When you install products into incompatible programs, you take the risk of it not working properly. Perhaps one day Flight1 will upgrade it to make it fully compatible. You are now asking our membership to tell you how to install it into an incompatible product. The product was actually made for FS9 and then upgraded to work with FSX (I suspect changing the textures, the model, and aircraft.cfg). I would fly your other aircraft in your hangar and hopefully Flight1 will be gracious and update the product for compatibility with FSX-SE and P3D.

You have other addons that were not made for XP. I have seen many crashes that were caused by telling Windows 7 to make the product you are using compatible to XP. So, go ahead and use it. If it works for you, great. Just remember if you get a crash in the future that you cannot figure out, then remember this warning. Best regards,

One appears to be off a few minutes. I would use the PMDG. Why would you be concerned about flight time in a simulator? Best regards, Jim

Normal behavior. Moving the LOD(Radius) slider might help or changing the resolution to 2048 might help reduce this. The faster your aircraft, the harder it is for your computer to keep up.

All I did is uninstall the Prepar3D Professional Client and then downloaded the latest version and installed it. I did not have to mess around with any of my aircraft, none of my Orbx scenery, my scenery.cfg was still there with no changes, there was no changes to the P3D.cfg, there was no changes to dll.xml or exe.xml. Use Elaine's excellent uninstall the client and reinstall the new version topic - http://www.avsim.com/topic/484945-how-do-i-update-prepar3d-v3-using-the-new-installers/ I think the main change with the client update is the update of P3D.exe and that does not affect your aircraft or scenery. Best regards, Jim

You're right Greg. Uh, maybe someday soon.... Well, I have to check out the new PMDG 747 when it's released first. Thanks for the suggestion. :smile: Best regards,

The upgrade does not affect any of your current scenery or settings.

This you must not do under any circumstances. Just make sure "Run as Administrator for ALL Users" is selected. Do not check any of the other stuff above that or you will have further problems. Best regards,

Thought I would tag this topic with a Scam Alert! Hopefully not too many around the web bought the software before it was removed.

Your system is capable of running P3D but the thing you will have to be concerned about is Virtual Address Space (VAS). Microsoft Windows only gives 64 bit users 4GB's. Back in the old FSX days we had to keep our sliders down a bit in order to get it to run around 20-30 FPS. The problems today is everyone thinks they have fast systems (and they do) so they think they can crank up P3D settings plus any of the addon's setting. High settings might work with a flight around an hour or two but more than that you risk running out of memory (VAS). The more eye-candy software addon you have, the more likely you'll see crashes if you don't keep your settings down. An SSD will give you faster load times but I do not think you'll see any significant performance boost while running P3D. Scenery density. I would keep it normal or dense. Nothing higher. Depends how long the flight and the other addon's you will have enabled. If you have the PMDG 777 with PMDG's777, flying over photographic scenery, into eye-candy commercial scenery airports and with AS16 running, you won't get far. The enjoyment of flight simulation, at least for me, is to learn the various systems on an aircraft. Pilots don't spend too much time sight-seeing and trying to find people sitting on top of buildings. They are too busy making sure the aircraft is flying properly. I personally enjoy learning the various types of flight management. I learned the G1000 recently and I'm very proficient with the FMC in the 737, 767, 777, and 747. Of course it gets a bit more daunting when you have real world weather simulated by weather programs like OPUS and Active Sky. If you every have a crash, I highly recommend the AVSIM CTD Guide (see link in my signature). It provides some suggestions on how to avoid crashes and what to do if you do get one. Enjoy! Best regards, Jim

All four components.

It appears you have to update your Mouse drivers - http://forums.windowscentral.com/windows-10/372782-why-cant-i-copy-paste-windows-10-allows-me-copy-but-will-not-paste.html. If you cannot copy and paste there is nothing we can do. If you see a faulting module maybe that will help.