Have flown about 12 flights from KBOS to NY, circling over Manhattan ( NY drew Design) and try landing at 04R. Everytime before about 6 NM or just after landing OOM appear.
If you search around, you'll find plenty of similar reports of OOM with that Manhattan scenery.
Flight number 13 exactly same flight and settings deactivated KJFK to default..This time I a have NO OOM..
That doesn't obviously mean JFK was the problem. If you are very close to OOM with that huge Manhattan scenery, adding a detailed airport might be enough to cross the memory exhaustion boundary.
OF COURSE, if you remove that huge Manhattan scenery, you will see NO OOM either with FSDT JFK and all the rest of the things you are running so, who's to blame ?
When people will start realize (and after all the discussions about CYVR, we thought this was already taken from granted) that is NEVER a single add-on causing OOMs ? It's the SUM of EVERYTHING you run in an area, because FSX can't use more than 4GB in total. This is an hard limit, and can't be changed, and this means you should start limit what you are installing in a certain area, because you can't expect to just add stuff, those 4GB WILL eventually be filled.
Fsdream team KJFK seems to really eat a lot..Any solution..
No. JFK is one of the lighter sceneries we have done BECAUSE it was carefully made to run in a very crowded area.
But you can't expect it to use LESS memory than the default. This because the default JFK uses a lot of canned library objects, but nobody would want to buy a payware add-on scenery with default libraries. Since JFK is 100% custom textures and objects, it will obviously use a bit more RAM of the default JFK. But BECAUSE of this, is even lighter on fps than default.
Drews Design says they will make their own JFK, so no OOM appear with the new Manhattan..
That's to be seen, but taking less memory in FSX is also a way to lower the fps. FS8/9 code, for example, is more compact (= takes less memory) but is MUCH slower. So, even if they manage to save a bit of memory, it will be at a greater cost in fps. And New York is not an area where you can afford losing even a single frame per second.
Since we use only FSX native code, we use a bit more RAM compared if we used FS8/9 code, but it also means we can use the GPU better AND you'll save MORE memory with our sceneries, if using DX10. This because, the more VRAM (video memory) a scenery use, the more is penalized by running under DX9, and the more memory savings you'll see when switching to DX10.
Do you have a solution for FSdream KJFK ?
Since JFK is not the problem, there's obviously no solution to speak of, not related to JFK in any way. The memory savings solutions might be:
- Apply the released patches for that huge Manhattan scenery, which will save some memory, of course reducing texture quality a lot.
- Turn off HD textures
- Use DX10.
