I tend to agree. In fact, I've been trying to figure out what might be causing the conflict.adi518 wrote:Hi Kevin, thanks for that info. However, I have a pretty well maintained fsx configuration here and in no way, it is the fault of other modules installed. I mean, maybe it's colliding with another addon, but I tried the an-2 in various situations and it always ctds when I close the sim with it selected in free-flight, after coming back from a flight. It's truly is something in the gauge coding.
My default flight is a cold start at my local airport. However, it doesn't load because I have "DisablePreload=1" in my FSX.cfg. In other words there are no other gauges loading in memory before I load the An-2 (assuming I haven't started any flight).
The only other thing I can think of that might make our systems different are addon modules. In my instance I only know of two: FSUIPC and the Milviz F-15E.
One other possible conflict might be from something running outside of FSX like a virus scanner. I run McAfee and its a hassle shutting it down just to fly.
Unfortunately, there is no error message indicating if any of these modules or applications are conflicting with the Swan2.dll.