Flew from Aerosoft Oslo (ENGM) to their EHAM and then on to Taxi2gate LTBA. On arrival and just after leaving the runway, bam OOM.
Is it possible to still get OOM with DX10?
- Yes - FSX is still a 32-bit app, Eric, and is still subject to that 4GB limitation.
I thought with DX10 the memory from a previous scenery was dumped from the virtual memory?
When the DX9 API allocates memory for FSX to use - it allocates an amount 1). into the
system's memory which will be roughly equal in size to that which is allocated 2). in the
GPU's memory.
A pipeline (approximate term) is then established between the two memories, with both the CPU and the GPU taking part in the graphics rendering process. This consumes a good chunk of the system's processor power, carrying out this work - but more importantly - it also consumes a good chunk of the system memory - hence when using the DX9 api - one is
much closer to an OOM than when using the DX10 api.
When the DX10 api allocates memory it only uses the GPU's memory, and all graphics operations are carried out by the GPU's own processor(s). Nothing (graphically) gets done on the system's CPU or has any interaction with the system memory. This should give the system a performance boost and the system's memory some "headroom" - but - if there are memory leaks, or memory is not released properly, or the amount of in-use files increases without control - then an OOM can certainly occur.
4096 textures - many layers of clouds - cloud visibility distance - lots of traffic - increasingly complex scenery - numerous other addons - high scenic LOD - complex aircraft - highest water detail - anything else which is spawned or called from FSX -
excess usage of any or all of these will cause an OOM.
However - there's also the not-so-well-known "
DeskTop Heap Limitation" which may also cause an OOM. This needs to be checked too, Eric.
Hope this helps some more!
All the Best,
pj
