The problem seems to occur when KMEM is loading for the first time when arriving at 6nm. I hope a fix will be find soon.
I just made the following test:
- Created a flight 15 NM south of KMEM
- Saved it as a default flight
- Quit from FSX
- Restarted FSX, and slewed to reach the airport until I was on top of it.
- Repeated this a dozen of times, allowing the whole airport to be unloaded and then reloaded very quickly, which is one of the most stressful testing you can do to *make* it crash.
- Tried with the default A321, then I repeated it again with the PMDG 777, several times, back and forth between the initial point at 15NM out and on top of the airport.
The results ? No crashes whatsoever. I had several 3rd party modules loaded, such as ASN, the PMDG modules, the Aerosoft modules, RAAS Professional, FSUIPC and FSRecorder.
While I was doing this, I was also logging all Simconnect events on a file, to check if any module caused errors. And guess what, there were some errors logged but, guess what, NONE of the errors came from any of our modules (bglmanx and Couatl.exe).
I had:
- Many FSUIPC UNRECOGNIZED_ID errors
- Some SODE OUT OF BOUNDS errors
- Some PMDG 777 errors which are clearly bugs: they mis-named some variables and have a duplicated event id.
- One UNRECOGNIZED_ID error from RAAS Pro
Again, NO errors of any kind from Couatl or Bglmanx.dll. The test lasted about 6 minutes, I wonder how many more errors I could log from those 3rd party modules and IF too many of them might cause a problem to the Sim, along the duration of a flight.
I think the only possible solution would be arranging a Teamviewer session, since I cannot replicate this in any way on my system. PM or email me for details.