Greetings!

 

I read somewhere online that un-checking unused scenery library entries will help prevent OOM errors. I have been attempting to fly from Dublin to Heathrow, all ORBX terrain, in a couple of aircraft, but as soon as I get near Heathrow I am OOM. In the Carenado Phenom I would crater about 20 miles out, in the eXtreme Prototypes Lear 28 about 10 miles out. Perhaps if I flew something slower and less demanding (like the trike) my flight would not OOM, but that would be one hell of a long trip from Dublin! I can take off from Heathrow with no problem, but I doubt that Heathrow itself is the real issue: my Task Manager recording indicates a steadily increasing memory load as I approach the coast of England, and it just gives up the ghost soon after.

 

So, I unchecked *every* Orbx scenery library except for EU (including Open LC EU), and I managed to fly over Heathrow in the Phenom to make the turn into the wind (running Opus weather). This is quite an improvement! However, I cratered before I could make the turn.

 

Disabling/re-enabling scenery files "works", but it just ain't worth the hassle in my opinion.

 

I am running P3D 1.4 (waiting for 2.3 to come out before I make the leap), so this is probably as appropriate to FSX as anything. 

 

John waiting-for-P3D-V2.3 Howell

Are you running a 32 or 64 bit version of Windows?

If you have photoreal sceneries, give first priority to disable them, may it be for any part of the world.

Heya JIm, 

 

64-bit Windows 7 Home Deluxe.

 

Heya Rishab, 

 

You reminded me of the context of the article I read. It was indeed discussing photoreal, but I don't use photoreal scenery. However, Orbx does use photoreal as an underlay in some areas, and that is perhaps why my OOM envelope got extended when I disabled the "rest of the world" in the Scenery Library.

What are you using for an LOD value and autogen density value in FSX.cfg?  Try lowering those values.

This is an automatic message.

 

This topic has been moved from "Flight Simulator Tips and Tricks" to "MS FSX Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

HAve you tried dx10? I was having the same issue flying from Anchorage to Seattle, everytime I approached KSEA, it would crash with dx9, since switching to dx 10 it's not a problem

^{Interesting, JV at ORBX quite clearly says disabling scenery does absolutely nothing to lower VAS apparently because FSX can only process what is sees around it for a relatively short distance.}

 

^{since he owns the company he just may know a thing or 2}

^{Interesting, JV at ORBX quite clearly says disabling scenery does absolutely nothing to lower VAS apparently because FSX can only process what is sees around it for a relatively short distance.}

 

^{since he owns the company he just may know a thing or 2}

 

This is true...but...it's more about releasing memory.  If i am flying from Jersey to Manchester all Uk2000 airports and i overfly UK2000 EGLL my FPS and VAS will plummet like a stone, once past the LOD range (3.5 in my case), the FPS will return, but VAS is not entirely released by the sim.  If i go nowhere near the payware airports everything is fine.  

^{Interesting, JV at ORBX quite clearly says disabling scenery does absolutely nothing to lower VAS apparently because FSX can only process what is sees around it for a relatively short distance.}

 

^{since he owns the company he just may know a thing or 2}

 

And funnily enough you can easily prove that it is actually true with a 5 minute experiment. 

 

Photo scenery bases and areas hit VAS no matter where in the world you are. It may not be much, but it can be the tipping point easily enough. 3D objects are what won't load since they have a set LOD radius to work with.

^{Interesting, JV at ORBX quite clearly says disabling scenery does absolutely nothing to lower VAS apparently because FSX can only process what is sees around it for a relatively short distance.}

 

^{since he owns the company he just may know a thing or 2}

 

 

Either John was referring to ORBX scenery only (where the impact of photoscenery is rather small) ... or he was "plane" wrong.   B)

^{Interesting, JV at ORBX quite clearly says disabling scenery does absolutely nothing to lower VAS apparently because FSX can only process what is sees around it for a relatively short distance.}

 

^{since he owns the company he just may know a thing or 2}

He is correct. Only photoscenery will load around the world whether you are flying there or not. Any other sceneries, like FSDT, Orbx/FTX, etc., will not load unless the scenery is near you. You can run Microsoft's Process Monitor and it will show you exactly what is loading during your flight. You will need to filter it though to only load FSX and FSX addons.

 

Best regards,

Either John was referring to ORBX scenery only (where the impact of photoscenery is rather small) ... or he was "plane" wrong.   B)

 

I have been plane wrong before, but yes, I was referring to ORBX scenery in P3D V1.4. 

 

I understand that VAS management/cleanup is one of the objectives of V2.+, and it seems to no longer be an issue based upon Rob Ainscough's testing. 

 

May have to make the leap!

I'm pretty sure there's considerable improvement in P3Dv2 as far as VAS management is concerned ... and BTW, I was referring to the "ORBX John" - John Venema.   B)

 

Anyhoo, the better your sim is at VAS management, the less disabling photoscenery is required.

I would rather turn down scenery than experience an OOM but I will not disable the add on airports that I depart from and arrive at. Having all the FTX regions installed and FTX Global I switch to FTX Global when flying in and out of the UK and also Ireland with Dublin X. This way I never have OOM's with the NGX or 777X.

With FTX Europe enabled I got OOM flying into Dublin X or UK2000 Heathrow both in dx9 and dx10.

Nothing worse than finishing a flight on Vatsim 5 miles from touchdown.