That still does not make much sense to me, why would I have memory issues when starting on the ramp with a default aircraft?
That's the only explanation which is consistent with what we observed so far:
- When we had the Teamviewer sessions, you were never able to show me a crash with GSX, once you disabled the modules from FS Labs, by simply placing the plane on an airport and call GSX there.
- You later said it only happens after landing.
Since GSX doesn't behave different, and it creates the same objects, the only possible explanation that makes an "after a landing" different, is the memory usage and fragmentation caused by the flight itself.
When I can fly routes using the PMDG aircrafts that are heavy on VAS multiple legs at a time without any issues as long as I do not call up GSX.
If the memory-hungry airplane already placed you CLOSE to exhausting VAS, calling for additional objects it's the proverbial "straw that broke the camel's back" which placed you in an OOM situation.
Either there is something wrong with GSX dealing with afcad files created in ADE
Which cannot be, otherwise we would have thousands of similar reports, since 90% of the AFCAD out there are made with ADE.
or something in my ADE is broken when compiling afcad files that is causing GSX to crash when reading them.
You never said it only happens in AFCAD YOU made yourself! Is this the case ?