i can understand your enthusiasm, but OOM free FSX can be achieved in many ways. The problem is what you want to sacrifice for that. 

This is what i did:

 - TML in fsx.CFG is 2048

 - REX clouds 1024, max 2048, DXT optimized

 - Microsoft patch for heap limitation applied: http://support.microsoft.com/kb/947246

 - i use SceneryConfigEditor every time before i start FSX, to enable only scenery i need for my next flight http://: http://sourceforge.net/projects/fs-sceditor/files/v1.1.1/

Important is to disable all payware, especially photoscenery. I enable only 1-2 continents(2 for long haul)and 2-3 airports. 

- Virtal memory management should be system managed on windows 7 / 64bit(don't change default paging file like some people suggest)

 

This way i can set allmost all sliders to the right and enjoy all graphics and animations.

 

And i use a lot of payware scenery and airliners, PMDG, Maddog, Concorde X. No OOM erros for approx 2 years now

Ditto Zeljko!  I did exactly the same except I use AS2012 clouds instead.  Good suggestions.

 

Best regards,

Jim

 - i use SceneryConfigEditor every time before i start FSX, to enable only scenery i need for my next flight http://: http://sourceforge.net/projects/fs-sceditor/files/v1.1.1/

Important is to disable all payware, especially photoscenery. I enable only 1-2 continents(2 for long haul)and 2-3 airports. 

 

Do you by chance also use AES Airport Service? Somehow I think that this little software will go crazy if sceneries are constantly activated or deactivated, but I don't know. Otherwise I will give this SceneryConfigEditor a chance for my next long haul flight...

Do you by chance also use AES Airport Service? Somehow I think that this little software will go crazy if sceneries are constantly activated or deactivated, but I don't know. Otherwise I will give this SceneryConfigEditor a chance for my next long haul flight...

 

No, i don't use AES anymore, i use GSX. I actually stoped to use AES becouse of bouncing issue, i don't know if that is solved. Also i can't remember how AES "read" airports, maybe you can run(after sceneryconfigeditor)makerwys, or AES indexing/configuration option if that exists

Ok, so how do you feel if I tell you now that you could have used

 

a) the "repair for pushback" option within AES, resolving 90% of all bouncing issues

 

or

 

b ) simply adjust the two parameters "static_cg_height" and "static_pitch" in the aircraft.cfg to manually get rid of any bouncing issue?

 

Reading the manual or looking once in the forums would have prevented you from putting AES away because of "bouncing" :lol:

 

But thanks for the heads up, so I will simply try the tool and see what it does B)

Well, that happened a long time ago, maybe "repair for pushback" did not exist at that time. I remember that i have tried everything, all tips from forums. I didn't replaced AES with GSX, i actually didn't used AES for some years before GSX release.

 

I liked some AES features, BTW - is that Simulation of water and snow on runways works with payware airports too? I liked that very much.

 

I just didn't checked what happened in the meantime, mostly becouse i am much more interested in flying then in that kind of addons, but i must admit - it can be a nice addition when everything works properly. With GSX, i don't like that stutters caused by simconnect, and i don't use it too often becouse of that  :lol:  

I run on Windows Vista 32bit , my settings are Global scenery Extremely dense Autogen Dense Water 2Xlow 100%UT2 traffic, TML =2048 now was 4096. LOD radius is 4.5. My system is a 3GHZ E6850 C2D system with a 1GB GTX 460 video card. The only time I ever had a problem with OOMs in FSX was when I first got the NGX. I could never complete a flight into a complex airport like FlyTampa or FSDT when flying the NGX. Since then I started managing my startup DLL's by setting Manual load to True in the dll.xml file, on all my optional addon dll's. Now when FSX starts it asks me what dll(s) I want loaded. I say no to all but what I am using on that flight. There's no need to load Capt sim dll's when flying a PMDG aircraft, and vice versa. Since doing this I could run any aircraft, including the NGX for any length of time, without problems. I've flown the NGX transcontinental both in the US and Europe. I've flown 14 hour flights on the PMDG 747-400, MD-11, and Captain Sim 777-200LR aircraft. This has been the most effective defense against OOM's for me, which is more critical for me, since I'm on a 32bit O/S.