Scenario. Aircraft QW BA146. Installed in P3d and FSX. P3d install works great.

Fsx install has a fatal error CTD upon selecting any of the 3 versions. Any other aircraft work fine.

Appcrashview reports it as the qw146.gau file as at fault. Recent tries yielded that fsui.dll is at fault as well.

 

 

Things Ive done in attempts to try and solve it.

 

Uninstall and remove all remnants of the 146 and cleaned the registry of it with ccleaner.

Reinstalled.Once as administrator.

Redownloaded fresh install file with another browser.

Redownloaded new license key

Avscanner is already set to ignore FSX root and sub dirs.

Avscanner disabled on installs.

Brand new fsx.cfg

Copy all gauge files associated with 146 from p3d

Copy all QW files folders from p3d including the root QW and simobjects folders.

 

Both flight1 and QW have no more suggestions. Anyone have any more ideas?

 

Thanks

Do you have same addons in P3d? Maybe you should try to remove to one backup folder all dll's and gauges of planes that you don't use in that moment. I had a situation with dll's conflicts in past and that was my solution which works.

Just bring them back after QW146 flight. I'll think about this more tomorow when i wake up fresh

Could be an activation/registration problem. The fsui, api, and main dlls are the main files needed for activating fsx/acceleration. What version of FSX is installed? Acceleration? Make sure the version is the same as Acceleration (10.0.61637.0) or FSX w/SP2 depending on what version of FSX is installed. I would install the product first into FSX then P3D. Perhaps those gauge files you are copying from P3D were modified to work only with P3D.

 

According to Google, this same type of situation occurred with the QW 757 (when selecting an aircraft) and here was the fix for that. Perhaps the installation of the QW146 is the same - http://qwsim.flight1.net/forums/forum_posts.asp?TID=20&title=crash-to-desktop-troubleshooting. In any case, it's something to do with trust apparently.

 

Best regards,

Jim

Do you have same addons in P3d? Maybe you should try to remove to one backup folder all dll's and gauges of planes that you don't use in that moment. I had a situation with dll's conflicts in past and that was my solution which works.

Just bring them back after QW146 flight. I'll think about this more tomorow when i wake up fresh

 

Hmm interesting but alot of sifting. I did a backup restore from a month ago, but no go. I would think if its a common dll file other aircraft would not work either. Anyway the dll error only happened once. The rest of the faulting module was pointed at qw146.gau

Super frustrating is all I can say. But thanks for the idea.

Could be an activation/registration problem. The fsui, api, and main dlls are the main files needed for activating fsx/acceleration. What version of FSX is installed? Acceleration? Make sure the version is the same as Acceleration (10.0.61637.0) or FSX w/SP2 depending on what version of FSX is installed. I would install the product first into FSX then P3D. Perhaps those gauge files you are copying from P3D were modified to work only with P3D.

 

According to Google, this same type of situation occurred with the QW 757 (when selecting an aircraft) and here was the fix for that. Perhaps the installation of the QW146 is the same - http://qwsim.flight1.net/forums/forum_posts.asp?TID=20&title=crash-to-desktop-troubleshooting. In any case, it's something to do with trust apparently.

 

Best regards,

Jim

 

Sorry I missed your post. Yes you could be right. I had seen that on the 757 with the add on manager. Which is why is redid my license key for a new one. The qw146 doesn't even show up or use the add on manager though.

 

And I have fsx sp2.

I'll try uninstalling P3D one and install fsx version first.

Thanks