Jim Young

Please do not spam AVSIM with your issues. In regards to the menus.dll error, please see my comments at http://www.avsim.com/topic/493242-ctd-p3d-error/. Exception Code: 0xC000041d = STATUS_FATAL_USER_CALLBACK_EXCEPTION so, what I think is you have a product running in P3D that is not compatible with P3D and you had to use EMT or you had to manually try to get the application installed and working.

Pro-ATC does not work with GA aircraft. You'll have to use the default ATC program for GA aircraft. Perhaps in the future. Right now it's fighting perfection for handling airliners. Everyone wants perfection and, when it is perfected, it still is not perfected to many and needs many more updates. I would be shocked if it ever works with GA aircraft (other than Jeroen's suggestion).

Sweet FX is not compatible with DX10 or very, very few individuals are successful using SweetFX with DX10.

This is part of the FSDT program for your sim. It is loaded via the dll.xml when you first startup FSX or P3D. I am shocked that Windows10 would crash FSX because you said yes. It means the dll.xml, which has the link to the module so it can be loaded at startup, may have two entries or the module is corrupted. I would check the FSDT site for a solution. I'm positive someone else had this issue. You uninstalled and reinstalled but did you download and run the latest Addon Manager? I believe there's a component missing in your dll.xml or exe.xml. There's an entry in the exe.xml too but your message. My version of the SimObjectAnimationModule is 1.3.3. Yours is 1.3.4. I thought I had the latest. Perhaps there is something wrong with v1.3.4. Best regards, Jim

Hi Ray, I went and edited your signature and removed the . You should only need the link in between [img.....img]. The same as when you post an image inside a post. We use BBCode so you would select the link for the BBCode and then, in the menu in the signature (same as the menu in new posts), you want to click on the image icon and paste the link inside that box. Best regards, Jim

I thought the installation of the directory as_srv with the dll as_btstrp.dll was the simconnect for P3D/FSX. I thought the installation of the directory as_srv with the dll as_btstrp.dll was the simconnect for P3D/FSX. But now, reading the manual it states: Automatic ASConnect Module Installation When you run AS16 for the first time, the ASConnect interface module must be installed for proper AS16 operation. You will receive a notice when starting AS16 advising that the simulator must be CLOSED to perform this operation. It is important that the simulator is properly closed (and restarted after) to ensure proper configuration. If running a local (non-networked) installation, you can then automatically launch the AS Connect installation when prompted by AS16. Networked installations must manually copy and run the installation from the server machine (The ASConnect installation file is located in your AS16 installation folder as ASConnect_2016_P3D_Install.exe or ASConnect_2016_FSX_Install.exe). Maybe that's what that as_btstrp.dll program does. It installs AS16 and then states, hey, do you want to open AS16? I respond "Yes" and it installs the program. The module is linked in the dll.xml too. Hope this hleps!! Best regards, Jim

I would recommend Dan's suggestion to wipe and clean install. Just delete the directory as your system does not know it is installed. Make sure too you go and delete the folders where your P3D.cfg and your scenery.cfg are located. I would backup your scenery.cfg as it will probably find all of the scenery addons you have installed (especially any photo scenery). FSDT stuff will have to be reinstalled. So will any FTX/Orbx stuff. I didn't have to reinstall FlyTampa and Taxi2Gate stuff. But you can worry about that after you have reinstalled P3D. Best regards, Jim

Probably best you report this to Lockheed Martin but the Add-on Menu is set up via the dll.xml. You could have duplicate entries as most have two dll.xml's now. Once in the same folder as your P3D.cfg and the other in the C:\ProgramData\Lockheed Martin\Prepar3d folder. Check both (if you have them) to make sure nothing is duplicated. An add-on caused this error so I would suspect the last add-on software you installed for P3D. Best regards,

An apphang or freeze is difficult to solve. The AVSIM CTD Guide has some suggestions and you should try them (see the last section on probable causes/solutions for Application Hangs). When only the sound is running in the background, it means you ran out of resources (not Virtual Address Space) and your sim is struggling to continue running. Means high settings somewhere. In the FSX.cfg or in the display driver settings. Of course, something running in the background like a program that is running on a schedule could cause this too. If you cannot find a solution looking at the probable causes in the AVSIM CTD Guide, then I would rename or move your fsx-se.cfg to a temporary directory, restart FSX-SE and see if this fixes the problem. You could have had a tweak in your config that is causing the problem. When you first installed FSX-SE and ran the default, not adding any tweaks to the config or raising any sliders, you had no issues. FSX-SE ran great! Then you added add-ons and things started going downhill afterwards. You raised some of your config settings and might have added a tweak or two because you had heard they really do super things to ones performance when running FSX-SE. ASN is totally brutal on resources when you have it set beyond the default settings and you have real world weather and the weather is really bad and you are flying something like the PMDG 777 and landing at a commercial add-on airport with a lot of eye-candy. This is why I recommend moving or renaming your fsx.cfg because that fixes most of the problems and some say is the same as doing a repair of FSX-SE or uninstalling/reinstalling only easier. If rebuilding the config does not work then you can bring back the one you had before and you can start looking elsewhere for a solution. But high settings, using ASN coupled with using payware aircraft and flying over commercial payware scenery is usually a recipe for disaster sometime during the flight. You can find a link to the AVSIM CTD Guide in my signature. Good luck! Best regards,

How do you get the file FSSAVE in the same folder as the fsx.cfg? I have a wx file. No fssave anywhere on my computer. I just tried FSX and the real world and I had no problems whatsoever loading the real world. I wonder if your logbook.bin is corrupt. Did you try renaming it to logbook.old? Are you loading a saved flight? Best regards,

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,