ftx global and fsgenesis mesh.
Both are not obviously "free" to use, memory-wise. Try to switch them off.
Water 1x high. Lowered autogen. No ground shadows. Still OOMs on approach to any of your airports from any of your other aiports.
No, you have an OOM that can happen everywhere, but you only noticed at our airports, because those are the flights you tried. You'll have it at any other airport of a comparable size.
And it's not just that, of all airports around, our will be the one suffering LESS from OOM because, since we handle scenery creation independently from FSX, we are sure that, outside the area of the airport, almost NOTHING is loaded for the airport, except very few things like the AFCAD or the low-res photoreal background, which are still handled by FSX.
Another airport scenery from any other developer ( except Flightbeam, which enjoy the same memory-saving abilities ) is in the hands of the FSX memory handling, and is very well known that FSX sometimes loads data from scenery that doesn't have much to do with the area you are flying in.
Of course, if you don't believe this, you can easily verify this. Start at KIAH, and measure your allocated memory. Slew out about 15 NM ( the scenery range for KIAH is 11 NM ) and see A LOT of memory (all the memory taken by airport) being reclaimed almost immediately.
That would PROVE you those OOMs don't have anything to do with the airports.
But you don't even have to do it yourself. I did it for you ( don't you think we already made all the memory tests before release ? ), here's the results:
First two around KIAH (over the airport and 15NM out ) show how memory is correctly reclaimed when exiting the KIAH area.
The one on a default airport in Texas ( Austin ), shows that the memory globally used by the sim on a default area, is similar to the memory used when being just outside KIAH, clearly proving that "just" have KIAH installed, doesn't affect memory at all.
The one on KLAX shows that KIAH takes way less memory than KLAX, which is impressive, considering how large KIAH is. KLAX uses 4096 textures, KIAH doesn't. My settings were with textures at 4096, of course.
The one 18NM outside KLAX ( KLAX has a 16NM loading range ) shows that KLAX also correctly reclaim memory outside its area.
The one 18NM outside KLAX with the PMDG, shows the airplane takes the same memory of the whole scenery, all by itself.
The one with the PMDG at KLAX, shows that without any other add-ons used (no 3rd party mesh or Landclass or global vectors and no AI) the memory is already at 2.3GB. Of course, as we proved with the previous screen, the situation at KIAH would be better.
The one at KIAH with UT2 AI, shows that UT2 adds another 300 MB at KIAH, compared to no AI from the 1st screen
The last two shows Austin with a default airplane with UT2 AI, and with the PMDG 777. Using the PMDG 777 with AI, on a DEFAULT airport, takes MORE memory than using a default airplane at KIAH, with traffic too!
I'd say the results speaks for themselves: KIAH is very well optimized and memory friendly so, please, just stop discussing about OOMs, as they might be "caused" by KIAH.
