Only happening with PMDG777 (aerosoft sceneries): if you got OOM with yours and fixed it. Please be kind and share your solution.

Thanks 
Regis -- an bho dhearg

Save Flight - Restart FSX - Load Flight. Save before entering runway, save at ToC, ToD, and on final. Save separately.

 

FSX doesn't effectively purge VAS Space used up at the departure airport and enroute, so OOMs can become commonplace during landing. Restarting FSX fully purges VAS space, I usually do it at ToD.

 

If you're still struggling with OOMs even with this, then lower LOD_Radius and autogen density in FSX.cfg, Or start disabling any nearby sceneries.

 

Windows 7 x64 is essential, and I always monitor FSX VAS usage with Process Explorer when it goes above 3.5GBs. (I have it up on the 2nd monitor.)

Save Flight - Restart FSX - Load Flight. Save before entering runway, save at ToC, ToD, and on final. Save separately.

 

FSX doesn't effectively purge VAS Space used up at the departure airport and enroute, so OOMs can become commonplace during landing. Restarting FSX fully purges VAS space, I usually do it at ToD.

 

If you're still struggling with OOMs even with this, then lower LOD_Radius and autogen density in FSX.cfg, Or start disabling any nearby sceneries.

 

Windows 7 x64 is essential, and I always monitor FSX VAS usage with Process Explorer when it goes above 3.5GBs. (I have it up on the 2nd monitor.)

Exactly

OOM's had been fixed even before the B777 was out: This document is based on an AVSIM discussion, dealing with a support issue of a fellow simmer, who had experienced OOM's due to his vast amount of installed photoscenery:

 

http://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors

Fresh fsx.cfg, put in a few tweaks OOM no more....Highmem fix a must.

Save Flight - Restart FSX - Load Flight. Save before entering runway, save at ToC, ToD, and on final. Save separately.

 

FSX doesn't effectively purge VAS Space used up at the departure airport and enroute, so OOMs can become commonplace during landing. Restarting FSX fully purges VAS space, I usually do it at ToD.

 

If you're still struggling with OOMs even with this, then lower LOD_Radius and autogen density in FSX.cfg, Or start disabling any nearby sceneries.

 

Windows 7 x64 is essential, and I always monitor FSX VAS usage with Process Explorer when it goes above 3.5GBs. (I have it up on the 2nd monitor.)

Oh my gosh, if I had to go through that every time I flew the T7 of FSX I would never touch either again. Fortunately and surprisingly I have never had an OOM since I started with FSX back in '08 and that is with tons of addons.

 

For the OP, if you're struggling with OOM's at certain Aerosoft airports you might want to look at the textures in the airports texture folder that is giving you problems. As an example, I used to get bad FPS at Aerosoft's Madrid and Barcelona. Turned out they both had some 32 bit textures in the ground polys that were consuming a lot of memory. By re saving them as DXT5 textures, I waw able to gain a lot of memory and performance back. Some devs use a lot of 2048 or 4096 textures that if you don't convert to1024s they will consume a lot of memory as well. Lastly, check your cloud and water textures and install DXT 1024 or smaller versions and that will help you free up some space as well.

 

 

Sean Campbell

t7 uses a ton of VAS. even more than NGX.  so you you have to make room for it.

 

LOD radius not more than 4.5   Autogen on dense or lower

Disable ANY scenery with Photoreal areas that you aren't flying over, including ORBX regions which have a ton of small photoreal masks.

I usually disable any airports other than the two in use.

 

DX10 will help a lot, if you aren't already using it, consider it and the fixer.  it has its own problems, but it does offload a lot of VAS to the graphics card, where it will not cause an OOM.

 

I use the freeware scenery configurator and have everything set in groups, so it doesn't take very long to enable/disable scenery before my flight.

 

biggies are LOD radius - I did a test flight, and there was greater than 500 mb difference during 2 hour flight between LOD 6.5 and LOD 4.5  I will sometimes fly with 5.5 as a compromise.  Also FSX loads a footprint of every photoreal scenery in memory, even if you are on the other side of the world from it,  that's why disabling photoreal is important.

 

Shawn Gray

Oh my gosh, if I had to go through that every time I flew the T7 of FSX I would never touch either again.

 

You're going to spend hours doing pretty much nothing anyway, so an extra 5 minutes restarting FSX shouldn't be an issue - unless of course you fly on VATSIM/IVAO.

 

 

 

Lastly, check your cloud and water textures and install DXT 1024 or smaller versions and that will help you free up some space as well.

 

Agreed. If you have HD clouds like REX, always replace them with ones at the lowest resolution. Dense clouds generated by 3rd party WX programs will eat heavily into your VAS space.

 

Read my post here

 

http://forum.avsim.net/topic/441009-disappointed/

 

I use 4094 texture setting in fsx.cfg file, but cloud textures I keep at 512 installed by REX4 Texture Direct. I use 4.5 radius as well. The big solution for me was duplicate afcad files, it must confuse fsx somehow and leads to oom errors.