I only found that when moving Addon Manager entry in dll.xml to the top down, I don't get CTD FSX, but instead I'm getting blmanx.dll error and Simconnect_text() error.
This indicates another addon is using an OUTDATED version of Simconnect that, when loading it first, will take over and let the sim stuck with it. That's why our installer always put bglmanx.dll on top of the DLL.XML, in order to prevent addons using outdated Simconnect to load their version first.
It's *POSSIBLE* this might be the reason of the crash: the two Simconnect versions are not working together. They are *supposed* to work together, using the Windows Side-by-Side loading (which allows two different .DLLs with the same name to run together in the same process), but sometimes this doesn't work, and everything start to misbehave.
Why some developers still insist using OUTDATED Simconnect version (who's using FSX RTM or SP1 nowadays
), it's beyond me, since the XPack/SP2 version we use works with FSX+SP2, FSX+Xpack, P3D 1, 2 and 3...
As I've said, so many times already ( but nobody has replied to it ), if you have a repeatable crash, I really need to have a look at your system with Teamviewer, because we are still unable to replicate ANY crash so, the only possible explanation, is a conflict with an addon with don't know of.
PM-me to arrange this.