So far I get an OOM after an hour flight in aerosoft and fsdreamteam addon scenery. I am using win7 64bit, fsx acceleration. 6gb ram. ultimate terrain europe with all the patches.Why can't I complete one flight???!?! So aggravating ThanksDavid

I get OOM messages also using the new FTX PNW scenery package. I am running a dual core Intel at 2.33 ghz. I find that turning down the autogen generally eliminates this problem forme especially in the high density metro regions of tbe scenery. I have a minimal system so I have to limit some of the eye candy. Once I get in the rural areas I turn the sliders up a bit and no OOM. I also found the switching views frequently also tends to use up memory as well. If you have a 4 core system others will have to help you but give it a try.

I just built a new i7 system, can't believe autogen would do that to me. I even edited the fsx file and set max autogen per cell settings... GRRR

It's the fact how Win7 handles video memory with WDDM1.0 and the use of virtual address space.

is there anything I can do besides downgrade to xp 64bit?

Did you increase your texture size for REX HD clouds i.e?All things like increasing Texture_Max_Load , Lod_Radius speedup OOM errors.Under DX10 you will not suffer OOM's but for me this was no solution because of several disadvantages concerning most addons.I've downgraded to xp 64bit.

So far I get an OOM after an hour flight in aerosoft and fsdreamteam addon scenery. I am using win7 64bit, fsx acceleration. 6gb ram. ultimate terrain europe with all the patches.Why can't I complete one flight???!?! So aggravating ThanksDavid

You have set BP=0 and if you are still using that it is the cause. I was doing fine with BP=0 in PNW with very dense AG, flew into FSDT-JFK or KOrd and same issue.

I just changed rex textures back to default 1024. moved autogen down to dense. tbm up to 120 from 80. I didn't have bp at 0 but 4500000 or what ever nick_n said I copied that from his guide. Now put bp back to 0 and will try again

You have set BP=0 and if you are still using that it is the cause. I was doing fine with BP=0 in PNW with very dense AG, flew into FSDT-JFK or KOrd and same issue.

Increasing BP to lets say 4.000000 only slows down OOM's but doesn't eliminate them if you take settings in FSX with high video memory load.

413X3A couple or so of points to check with Win7You usually have to run the Win 7 power options as balanced or better - high performance.Have you set a paging file? If yes, it may need defragmentation. If "no", then a paging file may be required with min and max values the same.On occasion some sound settings/drivers may cause OOM issues - various posts on the forums.You have an nVidia/ATI driver that you installed manually and not the default WDDM driver?However, having said all of that it's more likely to be due to the VASRegardsPeterH

413X3A couple or so of points to check with Win7You usually have to run the Win 7 power options as balanced or better - high performance.Have you set a paging file? If yes, it may need defragmentation. If "no", then a paging file may be required with min and max values the same.On occasion some sound settings/drivers may cause OOM issues - various posts on the forums.You have an nVidia/ATI driver that you installed manually and not the default WDDM driver?However, having said all of that it's more likely to be due to the VASRegardsPeterH

1. high performance yes2. before it was system managed, I have now set it to manually be 1.5 times my ram for minimum and maximum3. latest nvidia drivers with nicks guide to setup via nhancer

You have an nVidia/ATI driver that you installed manually and not the default WDDM driver?

What do you mean by that?I get the corrupted aircraft/scenery displays regularly. The usually appear when I take off from add on scenery, fly and land anywhere at a scenery intensive airport - default or add on. Most flights are smooth as silk with the majority of the flight taking place over water at FL300+. Everything looks great until after I land. No reported OOM but I am guessing that it is a similar problem.

Try running compatibility for Vista?

If you are running in full-screen mode, try window mode instead.Like you, I'm using Windows 7 64-bit with 6GB RAM and a bunch of addons. My processor is not as good as yours, and FPS does sometimes go low in some areas (e.g. Seattle in FTX PNW), but I've never had an OOM or corrupted aircraft/scenery issue.

What do you have your traffic set at, if it is real high try turning it down.Did you tweak your OS per NickN's instructions? Follow the Vista tweaks for Win7.http://205.252.250.26/cgi-bin/yabb2/YaBB.pl?num=1208959973I have never had an OOM on Win7 on the rig in my signature, I also am a 64 bit version of Win7, not a 32 bit version.NickN's FSX tweaks, you may want to double check your settings.http://www.simforums.com/forums/forum_posts.asp?TID=29041Rod