I was trying to post the same thing, but Boone was faster...basically, if you followed all discussions about OOM, it was clear that the scenery is NEVER a "cause" for OOM in itself, and fact you didn't had this with JFK V1 or you don't have this anywhere else, doesn't mean anything.
It's not a scenery that causes OOM. What causes OOM it's the COMBINATION of your installed add-ons, your sceneries (all of them, not just the airport, and this includes the default), your memory-hungry airplanes, your AI, fact you use DX9 or DX10, everything contributes to reaching the absolute maximum limit of 4GB that FSX, as a 32 bit app, can use. And the real, usable limit, is even lower than that, because the OOM message appears before all of 4GB are taken.
Yes, of course JFK V2 takes more RAM than V1, because native (= faster) FSX code takes more memory. But if you see OOMs now, it means your situation was ALREADY close to the limit with JFK V1, with your combination of installed add-ons, airplane used and settings. Obviously, if you were close to the limit, installing a scenery that takes even a *bit* more RAM than before, will cause OOMs, without this being a scenery's fault.
As explained in all threads about CYVR that discussed OOMs, you have several options at your disposal, you choose which one to apply:
- Lower your settings in the most dense areas
- Switch to DX10, which saves quite a bit or memory
- Don't use 4096x4096 textures.
- Use less memory-hungry airplanes (or configure them to use less memory, if the allow it)
