This is for anyone receiving an OOM when using FSX and you have a Windows 64 bit operating system.  Check your LOD_Radius setting in the FSX.cfg.  Anything above 4.5 (the default max), will eventually cause a crash depending on where you are flying.  I just suffered one of those crashes and I had my LOD_Radius set at 7.5 for flying over MegaSceneryEarth V2 States.  It works mostly okay over MSE V2 products but, if you go to another location, say, an Aerosoft product airport or scenery, or FSDT KLAX, KSFO, and other non-default, commercial airports, you will likely get an OOM.  If you have FSUIPC4 installed, it will chime when the memory starts to get low until you get the OOM message.  I had no problems whatsoever flying FSX over MSE V2 Illinois but recently I decided to try a flight from FSDT KLAX to KSFO over MegaScenery SoCal.  I loaded the PMDG737NGX and got the OOM right at the gate.  I opened up Windows Task Manager and watched the CPU Usage and Physical Memory slowly move to 100% then the OOM error.  Lowered the LOD_Radius setting to 4.5 and the OOM went away. 

 

If you have other settings set high too, this will even increase the speed of the OOM errors.  Fortunately I can get my 'eye-candy' over California with the 4.5 LOD and running Shade too.  Word Not Allowed, in his Software and Hardware Guide indicated you will eventually get an OOM with a high LOD setting and I just proved he was right.

 

I have also seen OOM's when individuals raise their texture and cloud settings in REX and AS2012 and OPUS to 4096 or 2048 (HD settings) and also have these texture settings in the FSX.cfg.  Evidently FSX just cannot render that high degree of detail everywhere.

 

I hope others who get this OOM error will visit here and let us know if lowering the LOD_Radius or other settings fixed their OOM. 

 

Best regards,

Jim

I thought it was common knowledge to not exceed 4.5 or your asking for OOM's/high VAS usage. I see some setting 8.5. Good luck!

 

"One of the biggest culprits when VAS is concerned is LOD_RADIUS in FSX.cfg. This setting alone offsets the VAS usage by couple of hundred MB when bumped from default 4.5 to 6.5 (I also suggest this in my guide, but with the caveat that it can pretty quickly cause an OOM)." Old Word Not Allowed's

Rendi,

 

Thanks for the info.  I am well aware of it though.  In fact I quoted the same as you when the folks at PC Aviator recommended a 7.0 or 8.0 LOD setting for MegaSceneryEarth V2 - http://forum.avsim.net/topic/402757-help-understanding-megascenery-earth-blurries/ - see Post 14/15.  I have made several successful flights in Orbx territory at LOD's above 7.0 (once 9.5).  It's something you can try once in a while.

 

I think it does work okay with MSE V2 scenery.  It's only when you go out of MSE V2 scenery and fly in/out of say an Aerosoft scenery in Europe or, like in my case, KLAX.

 

In the CTD Forum, there are a lot of people getting OOM's with Windows 7, 64 bit systems.  I just wanted to bring it to everyone's attention that if you do set your LOD higher than the max (4.5), you are bound to get an OOM.

 

Best regards,

Jim

This is for anyone receiving an OOM when using FSX and you have a Windows 64 bit operating system.  Check your LOD_Radius setting in the FSX.cfg.  Anything above 4.5 (the default max), will eventually cause a crash depending on where you are flying.  I just suffered one of those crashes and I had my LOD_Radius set at 7.5 for flying over MegaSceneryEarth V2 States.  It works mostly okay over MSE V2 products but, if you go to another location, say, an Aerosoft product airport or scenery, or FSDT KLAX, KSFO, and other non-default, commercial airports, you will likely get an OOM.  If you have FSUIPC4 installed, it will chime when the memory starts to get low until you get the OOM message.  I had no problems whatsoever flying FSX over MSE V2 Illinois but recently I decided to try a flight from FSDT KLAX to KSFO over MegaScenery SoCal.  I loaded the PMDG737NGX and got the OOM right at the gate.  I opened up Windows Task Manager and watched the CPU Usage and Physical Memory slowly move to 100% then the OOM error.  Lowered the LOD_Radius setting to 4.5 and the OOM went away. 

 

If you have other settings set high too, this will even increase the speed of the OOM errors.  Fortunately I can get my 'eye-candy' over California with the 4.5 LOD and running Shade too.  Word Not Allowed, in his Software and Hardware Guide indicated you will eventually get an OOM with a high LOD setting and I just proved he was right.

 

I have also seen OOM's when individuals raise their texture and cloud settings in REX and AS2012 and OPUS to 4096 or 2048 (HD settings) and also have these texture settings in the FSX.cfg.  Evidently FSX just cannot render that high degree of detail everywhere.

 

I hope others who get this OOM error will visit here and let us know if lowering the LOD_Radius or other settings fixed their OOM. 

 

Best regards,

Jim

 

so very true.

I can't manage to finish any long flight with lod 6.5 or fly with pmdg over london with orbx england. No way. The main cause of OMM on 64 bit systems is lod radius set higher than 4.5.

The main cause of OMM on 64 bit systems is lod radius set higher than 4.5.

 

No, that's just incorrect tweaking of your CFG, (which you shouldn't do much anyway)

 

The main cause of an OOM on a 64-bit system, is way too many addons stuffed into one particular area. If you can remember the OOM disaster when FSDT CYVR came out, the oom problem didn't have anything to do with FSDT CYVR, it was because there was way too many addons in one area, using up the finite recourse of 4GB in FSX. This was fixed by FSDT releasing options to turn down texture resolutions to reduce the memory footprint.

 

The main cause of an OOM on a 64-bit system, is way too many addons stuffed into one particular area.

 

That's certainly another way.  But the LOD_Radius setting above the FSX max is definite.  You might get away with many FPS unfriendly addons in one area for a while with a 4.5 LOD_Radius but it is almost a sure thing if you raise the LOD_Radius higher than that.

 

Best regards,

Jim

I loaded the PMDG737NGX and got the OOM right at the gate.

 

Hi Jim, PMDG NGX did this with me also (KSFO to KLAX).  I keep a "special" configuration just for PMDG, lose a lot of visual quality but it allows me to fly the PMDG NGX.  As of right now I have 4 configurations, 1 for PMDG NGX, 1 for other medium complexity commercial jets (Just Flight and Flight 1), and 1 for GA (real air), and 1 for FSX Default Aircraft.

 

I can run PMDG NGX on a 9.5 LOD, but no clouds, never add a view (major source of OOM), and disable Traffic 360, and turn off boats, vehicles, and run 1024 textures.

 

Sadly, because I have to "de-tune" FSX so much to run the PMDG NGX, I find myself using the PMDG NGX less and less :(  Which is a real shame because their Aircraft are VERY nice high quality products.

 

Rob.

Gents, I just dont see any pleasure in this, hence my reason for simply walking away.  3rd party add-ons wont make any money with me, enough is enough!

 

Sadly, because I have to "de-tune" FSX so much to run the PMDG NGX, I find myself using the PMDG NGX less and less Which is a real shame because their Aircraft are VERY nice high quality products.

 

Hi Rob,

 

I almost fly the PMDG737 exclusively and had no problems flying my flightplans over all of my MSE V2 photoscenery.  I had LOD at 7.5 and Texture_Max_Load at 4096 with no problems.  Great fps at a steady 40.  At the FSDT airports though, FPS came down near the one-digits but everything was smooth and all flights ended successfully with no CTD's.  Oh!  I had real weather (AS2012) turned on too.  Then I went to SoCal with my PMDG737 at the FSDT KLAX V2 airport.  Real weather turned on and suddenly I get the out of memory messages telling me to adjust some of the high FSX settings.  So there are places where you can go with high settings and not suffer a crash (at least I have been successful so far with MSE V2 products). 

 

I have on my desktop a Flightsim folder which, when opened, contains a link to my fsx.cfg, scenery.cfg, NI settings, ProATC, AS2012, XPAX, well about all of my flightsim stuff.  So if I'm flying over MSE V2 stuff, I'm going to set the LOD back up to 7.  That's the only setting I have to change.  If I want to make a flight over California over MegaScenery SoCal stuff, where I know I'll get an OOM, I'll change the LOD back to 4.5.  It's an easy switch for me.

 

Last night I tried flying over the MSE V2 State of Illinois at LOD 4.5 and the resolution really was horrible so it is a must that I have the ability to raise this to 7 or higher.  Eventually I'll have all MSE V2 States and this won't be much of an issue.

 

Like someone famous once said, "Man has to know his limitations..."  :lol:

 

Best regards,

Jim

Agree, finite limits ... but it does make me think twice before buying any 3rd party products, which I don't think is good overall (big picture).

 

There are many more "add-ons" I'd like to buy that I'm not buying because I'm already at the limit of OOM (I fly dangerously close to OOM all the time).  Constantly testing out flights to see how close I get to OOM and what (if anything) I can do to manage the OOMs ... it's almost a game within game   ... weather is what usually puts me over the top ... starting off a flight with minimal clouds or clear skys and then landing in a storm with lots of clouds.

 

weather is what usually puts me over the top ... starting off a flight with minimal clouds or clear skys and then landing in a storm with lots of clouds.

 

Totally agree.  I think I'm seeing a lot of people doubling up on weather texture settings.  If you have a TML of 4096 in your FSX.cfg and also set your weather program settings to 4096 or 2048, I think you are going to see a lot of crashes.  It's one or the other.  I have kept my weather settings in AS2012 at the default and never open up AS2012 before a flight.  The box says AS2012 replaces your default weather with AS2012 weather so I just turn on weather in the FSX setup.  I have HD clouds as my TML in FSX.cfg is set at 4096.  For some reason, if I turn on AS2012 as set up a flight plan with AS2012 open, the FPS will plummet and I feel like I'm going to see a ctd any moment.  But, same scenario for the flight, but I use the default weather and no issue at all.  I'm think SimConnect with AS2012 is not working as well as the connection through the default weather program.

 

Best regards,

Jim

 

But, same scenario for the flight, but I use the default weather and no issue at all. I'm think SimConnect with AS2012 is not working as well as the connection through the default weather program.

 

Interesting Jim ... I've used AS, Opus, and REX and to be honest, none of them have met my expectations in terms of weather engine.  Maybe, I'll go back to FSX weather process and just use REX textures.  Either they all just aren't getting good weather stations data, or their weather engine code has some issues.  My search for a good weather engine continues -- if you or anyone has recommendations that would be appreciated.  I might try Opus again when they release v3.0.

 

I don't have much experience with SimConnect other than seeing the data streams.  I know P3D installs a SimConnect Client (v1.0.20.0).  I'm using WideFS for networked PCs (FS Commander) but as I understand it, the latest version is a wrapper around SimConnect ... maybe Pete can clarify.

 

AS, Opus, and REX I've always ran locally as they don't seem to have any impact on FSX performance (I've got 6 real CPU cores).  I think REX has to run locally?  But AS and Opus can run on other computers.