Dreaded OOM error

Daveroo

Daveroo

Members +
ok i have a question...i thought everyone said that FSX only used,saw,recognized,accessed 4gb of system RAM/ROM? ...i have that plus a 2gb RAM/ROM video card....so why am i getting the dreaded OOM?..

can i adjust my virtual memory and have that make a differance?...
 
Dave, what model and scenery were you using when the OOM happened? Was there a warning message followed by a CTD? I've had some OOM CTD's but also VAS max-outs and usually it had to do with one of my high end models(like the PMDG 737NGX and some dense high detail scenery). If you can pass as much information on this as you can, maybe a few of us can help identify the culprit. I know it can be a pain sometimes!
 
ok here goes,

ORBX northern California,with ORBX Monterey,and Lionheart Tri-pacer,i was sitting,idling at the end of the runway...
 
ORBX is a pretty heavy hitter but not enough to cause this in such a setting(beginning of flight, etc). Have you made any adjustments to your FSX config file such as changing the Texture_Max_Load from 1024 to 4096 or increased the LOD_Radius? When are your scenery settings?(density) If you have not made those changes I'd suspect there is a memory leak going on somewhere in your system. Perhaps some of the rest of the crew here can throw in some ideas?
 
Also did you start your flight from that airport? Or had you been flying for a while and landed there?

Over time the VAS can build up to an OOM.

FWIW your physical RAM has nothing to do with OOM's.

Also what settings are you running?
 
well i started at the monterey airport,but i had been testing for awhile,so maybe that was it.but the rest of those comments went right over my head....whoooosh.....i will read seans link and ill go back and look at what everyone else said at a later time.
 
You must log in or register to reply here.
Back
Top