...Without lowering sliders, or is this the only way? I fly in big city Orbx Land with the PMDG NGX and I automatically get OOM's within about 30 min. Granted my settings are really high, LOD 6.5 with extremely dense autogen and max scenery sliders, but zero ai traffic. Do these only happen because of the way was programmed? Or would this happen with any 32bit application?

Start running my checklistIf done, start FSXPres CTL ALT DElLStar Taskmanagerand goto the Performance Tab and Press Resource monitorSelect FSx in the Overview tabSelect the Memory tab and see...Check in the fsx.cfg if the AffinityMask setting is at least 15

Why not turn down your extreme settings and see what will happen? Or better: Get that i5 of yours up to 4.8 Ghz! Or buy a new i7 2600K, because of the larger cache... Or try a "System Managed" Virtual memory size. PS: Get a new mobo, your Gigabyte P67A UD4 B3 is cr*p, excuse me my blunt French!

Processor speed or cache is not going to make any difference whatsoever to OOM errors. I honestly don't think there's any way to eliminate them completely when using high density scenery/settings/addons. I'm still plagued by them unless i remove AES, turn autogen down, and reduce LOD radius back to default. The latter of those is a nightmare for me given that I fly almost exclusively over photoscenery.

LOD is a VAS hog Ryan. With just default 4.5 I easily hit 3 - 3.5GB at ORBX PNW in the NGX. It's a memory hungry plane too, so you can't have it all.They are revising the VAS "problem" at PMDG as you surely know already, but I think that amazing VC at high resolution and those system simulations have to come at the price of a higher VAS requirement

I guess I was under the impression that OOM's are caused by virtual memory saturation, rather than physical memory??? I turned down my settings (not what I wanted to do), and here's the shot:

Processor speed or cache is not going to make any difference whatsoever to OOM errors. I honestly don't think there's any way to eliminate them completely when using high density scenery/settings/addons. I'm still plagued by them unless i remove AES, turn autogen down, and reduce LOD radius back to default. The latter of those is a nightmare for me given that I fly almost exclusively over photoscenery.

Yep, this is what I thought.... so it's essentially a function of the software and how it's programmed... ie there's nothing we can do except turn stuff down... ugh

OK, seeing the cpu performance, shut down all programs in background that you dont need; may be you gain someDo you use multi screen or single screen

so it's essentially a function of the software and how it's programmed... ie there's nothing we can do except turn stuff down... ugh

I think so. FSX is really a very unfinished piece of software. Hugely frustrating when you can get it to look and run great, only to then have the sim throw a hissy fit at that very fact.

Yes OOM is about virtual memory, not RAM. You can't use the task manager to monitor it. Try Process Explorer and compare

So here we are again with FSX? NO matter whatever new CPU/GPU/RAM etc. you buy and install we are f*cked?!! But why oh why turn up the settings everytime there´s new hardware on the block, then you´ll just "elevate" the problem, right? Be comfortable with normal settings if you can´t run it, or remove the "FSX Hog" from the PC! I´m very tempted to do that, I´m fed up with this crap...

I'm slightly confused Ryan. You say "would it happen with any 32 bit application?" the answer is more than likely yes, in my opinion, because you are limited to only 3gb RAM with 32 bit. But your signature says Win 7 64 ????

RockyI believe that Ryan is referring to a 32-bit application such as FSX even if it runs in a 64-bit OS. In a 32-bit OS a 32-bit app without Large Address aware can only address 2GB of the Virtual Address Space (with the userva/3GB option set this will rise to around a max of 3GB VAS if you are lucky).In a 64-bit OS with Large Address aware set (eg FSX SP2) then FSX can occupy the whole 4GB of the VAS.This has nothing to do with physical RAM or the paging file (the latter MS sometimes refers confusingly to as 'virtual memory').However in this VAS the space must be contiguous otherwise OOM's will happpen. (OOMs may also occur if the VAS is depleted by lots of processes, etc etc)So you could have plenty of VAS available and still suffer an OOM.Now when you consider what loads into this VAS besides FSX (ie planes, scenery, weather engines, fps limiters, video card settings, etc) and its easy to see why OOM's can occur.I have never seen an OOM with a plain install of FSX on a 32 or 64-bit OS. You can use sysinternals VMMap to monitor use of Virtual Memory, but I can't see that it helps with 'solving' OOM's in FSX.The trouble starts when you start to add in sophisticated complex add-ons.IMHO the causes of OOMs are multifactorial, so lets hope that Flight has been written with a code that utilises the modern cpu's, RAM and video cards, and you can load every bit of software without seeing an OOM. I hope that it is a 64-bit app!RegardsPeterH

RockyI believe that Ryan is referring to a 32-bit application such as FSX even if it runs in a 64-bit OS. In a 32-bit OS a 32-bit app without Large Address aware can only address 2GB of the Virtual Address Space (with the userva/3GB option set this will rise to around a max of 3GB VAS if you are lucky).In a 64-bit OS with Large Address aware set (eg FSX SP2) then FSX can occupy the whole 4GB of the VAS.This has nothing to do with physical RAM or the paging file (the latter MS sometimes refers confusingly to as 'virtual memory').However in this VAS the space must be contiguous otherwise OOM's will happpen. (OOMs may also occur if the VAS is depleted by lots of processes, etc etc)So you could have plenty of VAS available and still suffer an OOM.Now when you consider what loads into this VAS besides FSX (ie planes, scenery, weather engines, fps limiters, video card settings, etc) and its easy to see why OOM's can occur.I have never seen an OOM with a plain install of FSX on a 32 or 64-bit OS.You can use sysinternals VMMap to monitor use of Virtual Memory, but I can't see that it helps with 'solving' OOM's in FSX.The trouble starts when you start to add in sophisticated complex add-ons.IMHO the causes of OOMs are multifactorial, so lets hope that Flight has been written with a code that utilises the modern cpu's, RAM and video cards, and you can load every bit of software without seeing an OOM. I hope that it is a 64-bit app!RegardsPeterH

So true Peter, if they insist on 32b with Flight I won't touch it with a ten foot pole

So true Peter, if they insist on 32b with Flight I won't touch it with a ten foot pole

I doubt they will, but if they do, I won't either. Cheers, - jahman.

RockyI believe that Ryan is referring to a 32-bit application such as FSX even if it runs in a 64-bit OS. In a 32-bit OS a 32-bit app without Large Address aware can only address 2GB of the Virtual Address Space (with the userva/3GB option set this will rise to around a max of 3GB VAS if you are lucky).In a 64-bit OS with Large Address aware set (eg FSX SP2) then FSX can occupy the whole 4GB of the VAS.This has nothing to do with physical RAM or the paging file (the latter MS sometimes refers confusingly to as 'virtual memory').However in this VAS the space must be contiguous otherwise OOM's will happpen. (OOMs may also occur if the VAS is depleted by lots of processes, etc etc)So you could have plenty of VAS available and still suffer an OOM.Now when you consider what loads into this VAS besides FSX (ie planes, scenery, weather engines, fps limiters, video card settings, etc) and its easy to see why OOM's can occur.I have never seen an OOM with a plain install of FSX on a 32 or 64-bit OS.You can use sysinternals VMMap to monitor use of Virtual Memory, but I can't see that it helps with 'solving' OOM's in FSX.The trouble starts when you start to add in sophisticated complex add-ons.IMHO the causes of OOMs are multifactorial, so lets hope that Flight has been written with a code that utilises the modern cpu's, RAM and video cards, and you can load every bit of software without seeing an OOM. I hope that it is a 64-bit app!RegardsPeterH

Ahh, oops, I'll have another g&t please Thanks Peter