So for the first time last couple of flights I have done I have gotten a OOM. One flight was KRDU-KLGA got it basically right in downtown NY. Next was KLGA-KIAD and I got it on final. Before each flight I made sure only the airports that I am using are active in my scenery library. 

 

Flying into LGA I think I understand the OOM because I had my auto gen set at dense and figured that was what caused it. I am also using Drewziski(sp) NY airports. Flying into KIAD like I have TONS of times before has not caused an OOM except for this time. Is it because I left from KLGA that I got the OOM?

 

Which settings can I lower to make sure I don't get a OOM when flying into NY or other scenery intensive areas? 

If you got your autogen set to dense   than there must be some thing else since  your flight plan is only  a short one,   maybe you got your ai traffic setting  to high which is  the can cause oom.

A few things you can do:

 

Lower the LOD radius in FSX.cfg

Lower AI traffic density

Use low-resolution cloud and water textures

Fly a simpler aircraft and not use HD (e.g. McPhat) textures

Only enable scenery that you're flying into

Clear the weather

 

And finally....

 

Save, restart and load regularly to 'flush' the VAS. Save before takeoff, save during climb, save at Top-of-Climb, save at Top-of-descent, save on approach.

- Get rid off all AI traffic. Sorry to say but it really drains VAS

 

- You can save about 200 MB of VAS by setting autogen density to normal

 

- Turning down water effects might help a bit

 

- Only use 512 or 1024 resolution textures (for clouds, airports etc) You probably wont notice any difference

 

- Purchace and install the DX10 scenery fixer. For many, VAS usage drops around 200MB with this fixer installed. Takes some time to set ut, but its worth it.

 

- Only activate, in the scenery library, the two airports you flying between. Disable all others so they wont load into FSX as you pass them. Or you could download the SceneryConfigurator which allows you to set up different set/regions that you can easily load directly into FSX.

fix memory leak.

 

follow that tutorial (on french forum) and you'll be surprised

 

http://www.pilote-virtuel.com/viewtopic.php?id=51466

fix memory leak.

 

follow that tutorial (on french forum) and you'll be surprised

 

http://www.pilote-virtuel.com/viewtopic.php?id=51466

 

This new to me. Can you explain a little on how it works? I dont know french, sorry.

disable any photoscenery that you aren't flying over.  includes orbx regions (not global or vector) cause they have many many photoreal areas.

 

you mentioned having the new york airports,  do you also have the Drewziski city scenery?  if you do,  that carries a hefty VAS hit on it's own, and you may have issues using that when you add on a high VAS plane like pmdg and auto gen, and other high detail airport at the other end of the flight.

Best way to avoid OOM's?

 

 

 

In all honesty, the only reliable way I found to avoid getting OOMs was to change over to FSX Steam Edition.   You will see plenty reports from users on AVSIM who just aren't getting OOMs any more, with the new build.

As I understand it, the Steam Edition does address FSX's flawed handling of its use of RAM.  Otherwise, limit autogen, AI traffic, texture sizes, and don't fly for more than 2 hours.  Saving your flight, exiting, then restarting FSX and resuming your flight also helps, but is a real immersion killer.

It's just those airports (the D airports)- they are OOM generators

The AVSIM CTD Guide has some suggestions too.

 

Best regards,

I don't fly with autogen which has completely eliminated OOM's, autogen is such a huge killer both for FPS and memory.

Is there any relationship between OOM's and your hardware.  Would upgrading a video card, CPU, RAM, etc. help?

Is there any relationship between OOM's and your hardware. Would upgrading a video card, CPU, RAM, etc. help?

No.

I don't fly with autogen which has completely eliminated OOM's, autogen is such a huge killer both for FPS and memory.

 

Might as well go back to FS9 in that case....