I've finished the Teamviewer session with cj_strawbs, we found the cause of his problem and was due to the following:
- The Addon Manager (bglmanx.dll) has a special mode of operation when used with P3D AND the Prepar3D Migration Tool. Since that tool "fools" applications to make them believe they are running under FSX, when in fact P3D is running, this wouldn't normally work with the Addon Manager, which must really know if it's running under P3D or FSX, because it needs to access specific memory areas which are different between the two. This won't be a problem with just P3D or FSX, the problem happens ONLY if using the P3D Migration Tool in Legacy mode.
- In order to overcome this issue, the Addon Manager can be forced to work in P3D mode even if it's being fooled by the Migration tool, using an environment variable. We explained the procedure here:
http://www.fsdreamteam.com/forum/index.php/topic,7237.0.htmlWith a sample batch file that, as you can see, SETS the variable before calling Prepar3d.EXE and UNSET the variable on exit. This for the precise reason that in case you want to run FSX after that, the variable must be cleared, otherwise the Addon Mananger will still run in P3D mode, even under FSX.
Unfortunately, cj_strawbs probably thought that, instead of using such batch file, he could achieve the same by setting a *permanent* environment variable, and that caused the crash, because now the Addon Manager was stuck in P3D mode, even when launched from FSX.
So, if you have the AddonManagerForcedVersion variable set to something, and run FSX, this will crash causing that error. Removing the variable from the permanent environment variables, fixed the problem for cj_strawbs. You can check your environment variables as explained here:
http://blogmines.com/blog/2010/02/12/how-to-change-environmental-variables-on-window-7/As I've said, this was the cause on cj_strawbs system, it doesn't necessarily mean it will fix the issue on YOUR systems too, but it might be worth checking.