Thanks for the reply. I was just wondering if perhaps you fellows could start loading these large airports more gradually
That's PRECISELY what we do.
In fact, we (and Flightbeam, since they use our software too), are the only ones that actively do memory custom management. We DO NOT try to "slam everything", what we do is exactly the opposite: every class of objects has different loading ranges, based on distance, altitude, etc, carefully optimized to NOT have to load "everything" at the same time, and lots of objects are being loaded very late, some only after you are on ground, having exited the runway and slowing down.
There's no scenery out there as heavily memory-optimized as KMEM and if it wasn't (means = if someone tried to do it not using custom memory management), it would never fit in memory.
This doesn't have anything to do with your "PC power", but it's just an hard limitation of the fact FSX it's a 32 bit application so, it WILL crash, if you expect to be able to just keep adding things.
But of course, if you are already CLOSE to memory exhaustion just before KMEM loads, the best memory management strategies in the world cannot do much. You must lower your settings, plain and simple.
I know my computer can display KMEM because I see everything when I spawn the NGX there, and all the animations you have built into it work
This further proves the scenery it's OK, and the problem it's something. Or, as I've said, the combination of everything.
If you are getting crashes only after a flight, it's because the sim in that situation has LESS available memory compared to when you start a flight, and this might be either caused by the very well known issue of FSX not entirely cleaning memory of scenery areas you passed by during the flight, even after a long distance, but also because some of your loaded addons might be *leaking* memory too, but the effect requires some time to be noticeable.