i can see you on vataware Robin !  B)

Photoscenery is he worst. If you're not flying over the photoscenery, definitely disable it. No messing with the scenery config. Use the scenery library in fsx or use a program called scenery config editor to enable and disable sceneries before loading fsx

 

 

I had one OOM, but to be fair I was pushing my FSX to its limits. High LOD RADIUS

 

I'm going to take a look at my radius when I get home.  I really hope it's set too high.  Also my problem MIGHT be just the FS Dreamteam CYVR airport.  Who knows.  I'll figure it out hopefully.  

You mean uncheck areas you won't be flying through? I have a gazillion sceneries and to do this before each flight is ridiculous.

 

If you want FSX to work well, this is a VERY important step, ridiculous or not, it is what it is.  I'm hoping someone will produce a flight planner that can detect the scenery areas and/or at least allow "saved" scenery area selections so that it makes this task much easier ... auto select the scenery en route.

Photoscenery is he worst. If you're not flying over the photoscenery, definitely disable it. No messing with the scenery config. Use the scenery library in fsx or use a program called scenery config editor to enable and disable sceneries before loading fsx

 

Bookmarking this program for later.  Thanks.  

If you want FSX to work well, this is a VERY important step, ridiculous or not, it is what it is.  I'm hoping someone will produce a flight planner what can detect the scenery areas and/or at least allow "saved" scenery area selections so that it makes this task much easier ... auto select the scenery en route.

 

This is new to me.  Don't know how I never knew this before.  Thanks for the advice, I'll give it a shot.  

If you want FSX to work well, this is a VERY important step, ridiculous or not, it is what it is.  I'm hoping someone will produce a flight planner what can detect the scenery areas and/or at least allow "saved" scenery area selections so that it makes this task much easier ... auto select the scenery en route.

Now there is a splendid idea!

There seems to be something with 777... Just landed at FSDT CYVR after long haul(EDDM - CYVR) and FSUIPC warned me several times. I have all unused scenery disabled(even default unused scenery), texture max load to 2048, REX DXT optimized 1024 cluods, microsoft heap patch etc, etc... This happened to me after 2 years without OOM's, and i did this long haul before with MD11 and Concorde X. So, must be something about 777... 777 performance manager would be fine i think

 

 

There seems to be something with 777... Just landed at FSDT CYVR

 

Yep same here.  It's only this plane.  My first OOM ever.  It happened at the same scenery too.  Hmmm....

How in the world could you guys say this is PMDG's fault?

 

Really? What is PMDG supposed to do, dumb down it's quality because you don't understand FSX?

 

You really don't understand anything about OOM's, really, if you did, you would know that One single addon in FSX cannot cause an OOM. It's never the Addon's "fault", it's nobody's fault.

 

The PMDG 777 probably was the one thing that pushed you to your 4GB limit, along with your sliders which are probably to high to begin with, with hundreds of addons stuffed into one area, it's no wonder you are having OOM's.

 

So before you start blaming PMDG for you errors, check out what's really happening. You have to start making choices on what you load up in FSX, because it is unfortunately limited to 4GB.

 

 

How in the world could you guys say this is PMDG's fault?

 

Hello Mr. 35 posts and no signature.  Who said it was PMDG's fault?  That's right, nobody.  

Since getting Scenery Config Editor, my flying has certainly got a lot more stable. It is so easy to setup and just have the specific areas you're flying between enabled. For instance, if I'm flying OMDB to EDDF I only enable Dubai and Germany scenery areas, everything else disabled. I used to get constant OOM for any flight over Germany, but could never figure it out why. No problems now, though!

 

As it happens, my first flight in the 777 last night was from KPAE to FSDT CYVR and I got an OOM there too. No worries, I'm pretty sure that I have AI running at 100% so will tone that down a bit.

 

Am going to test a few of the FSDT and Flightbeam airports out over the next few days to ensure I can run them and the 777 together.

 

I've also got into the habit of checking the ProcessExplorer to see how VAS is coping.

 

 

As it happens, my first flight in the 777 last night was from KPAE to FSDT CYVR and I got an OOM there too. No worries, I'm pretty sure that I have AI running at 100% so will tone that down a bit.

 

Seems to be an issue with FSDT CYVR so far.  I'll take a look at that software for managing scenery.  So were you managing your scenery using this tool when you got the OOM at YVR?  

Before you start uninstalling stuff try just reducing autogen to sparse and see if that's enough. It was for me when I was dealing with oom errors. These guys are right about the cause of oom errors.

I'm stuck on a 32bit Vista system, so I'm even more conscious of VAS/OOMs then those on Win 7 64bit systems. One of the best things you can do to reduce the occurrence of OOM's is managing your startup DLL's You do this by setting the following line to your optional dll's in the dll.xml file. Do not touch the ones you use on every flight.

 

<ManualLoad>True</ManualLoad>

 

Now when FSX starts, it will ask you what dll's you want loaded. Say no to all but the ones you are going to use during your current session. There's no sense loading Captain Sim dll's when flying the PMDG 777 is there. This has practically eliminated OOM's for me since doing this (Which I always got with the NGX before), until today with the 777, on my test flight between KJFK and FlyTampa KTPA.  but I can still turn some settings down that will probably help.

 

Tom Cain

Seems to be an issue with FSDT CYVR so far.  I'll take a look at that software for managing scenery.  So were you managing your scenery using this tool when you got the OOM at YVR?  

To be honest, I don't know! Was just so keen to get in the 777 and fly that I never checked what my current setup was at that point. Will check it out again tonight when I get home. 

What Andres suggests, I also agree with - have done this in the past too.

For myself, I think the major culprit for OOM will be AI traffic.

 

I certainly want to be able to fly the 777 into payware airports so am going to carefully check setups (autogen, ai etc) to ensure all is compatible.

 

But certainly get the Scenery Config Editor - as they say, you'll never go back to Scenery Library again!