Hello,This is still a temporary report but probably somebody with similar problems and specs can reproduce the results...Just today I was able to reproduce a method how to avoid my OOM problems I regularly experienced at EHAM. I failed in most cases, even when reducing UT2 traffic to 20% (GA even to 10%), ground traffic was set to low and street traffic etc. was set to less than 15%. I did not want to make other compromises regarding the visual impression (clouds, resolution and whatever else). However, today I was able to pinpoint Active Sky 2012 to likely consume more memory than a 32Bit app can handle in this combination as I reduced my settings here in steps, following the sequence:3D clouds 4096 x 4096 and all other maxed and in HD quality in steps down via DXT5 resp. DXT1 compressed, then 3D-clouds in 2048 x 2048 (all other maxed) in HD again (OOM when landing at EHAM again) and finally today 3D-clouds in 2048 x 2048, all other at maxed resolution but all textures DXT compressed. This last setting gave me about 500 kByte reserve space even when I tuned up UT2 traffic to 100% (both sliders). I used the MS Process Explorer on a second screen and looked for the critical "Virtual Size".My system specs you may read below. I'll make some more flights in order to test these settings but I'm quite confident at the moment.BTW, I do not have the intention to blame the guys of HiFi Sim. AS2012 is a great product and it seems that they even addressed some weaknesses in their last Beta-release. It seems to be the interaction of FSX, PMDG's NGX, UTX Europe and AS2012 overstressing the memory space of 4GB.

oh how i wish some programming genius would write a dll or something that would release fsx from these limitations, if only.....btw im planning on getting myself a 2500k to overclock to 4.5ghz, i see yours is at 3.4, what kind of frames do u get at that speed?

Hello Bryan,A bit OT I'm afraid. However, normally I'm getting about 25 fpm but I don't care as long as the look and feel is smooth enough to ignore lower frame rates. Up to now I did not see a reason to overclock. If I really could turn my AI traffic much higher this will likely have a heavy impact to this parameter, I'm afraid - time to reconsider...

oh how i wish some programming genius would write a dll or something that would release fsx from these limitations, if only.....btw im planning on getting myself a 2500k to overclock to 4.5ghz, i see yours is at 3.4, what kind of frames do u get at that speed?

 

That's not possible - the only way to remove the limitation would be for Microsoft to compile and release a 64-bit FSX.exe. We all know that's not going to happen though.

 

4GB of address space with a 32-bit app is a mathematical barrier - 2 to the 32nd power is 4GB. 2 to the 64th power is almost 2 exabytes (1000 terrabytes = 1 exabyte) and there's effectively no limit with today's hardware.

Don't forget that all memory addresses are 64-bit extended so eat more memory even for a 32-bit app.

 

DXT textures are the way to go anyway - BMP textures are copied for every object that references it, whilst DXT textures exist in memory only once and are referenced multiple times. Reduced memory usage by texture size * n - 1 objects and faster to render as well. :)

 

One thing that would help enourmously is if apps would run outside the FSX process. Running inside the process is a sure way to exhaust the memory space.

 

Best regards,

Robin.