I was monitoring my VAS usage amid some freezing issues. From what I observed, the 777-300ER take up between 800-900MB, does that sound about right?

Yes, Yes and more yes.

 

I would say use the search function and you will find loads of post about the PMDG 777 and OOMS, but I am sure that somebody else on the forum will say that, because that is what a search is for.

 

The PMDG is a very high quality add on with very advance programming. This uses a lot of memory and increases the VAS usage.

So your response basically means 800-900mb sounds accurate? I'm just trying to do a breakdown of how much VAS each addon uses

Some 800 MB sounds about right for the -200. The sound caching option alone "weighs" about 200 MB in VAS.

 

I would expect the -300 to be about the same (with taxi cam off!), so my main heads-up is to make sure you have the sound caching option set according to your needs. (Less caching - less VAS.)

Some 800 MB sounds about right for the -200. The sound caching option alone "weighs" about 200 MB in VAS.

 

I would expect the -300 to be about the same (with taxi cam off!), so my main heads-up is to make sure you have the sound caching option set according to your needs. (Less caching - less VAS.)

Hi Olli you funny dude ;-)

 

Sound cashing - off, means less VAS, correct?

Sound cashing - on, is to prevent freezes correct?

Hehehe ...

 

Yep, off means the lowest VAS usage, all means the highest VAS footprint (there is also a selective sound caching setting in between).

 

The caching thingy hasn't prevented my freezes (still the same freezes as pre-SP1), so I go with the lowest VAS option (sound caching completely off).

Hehehe ...

 

Yep, off means the lowest VAS usage, all means the highest VAS footprint (there is also a selective sound caching setting in between).

 

The caching thingy hasn't prevented my freezes (still the same freezes as pre-SP1), so I go with the lowest VAS option (sound caching completely off).

 

Well gentlemen just choose the lower bit rate sound and resize the livery textures from 4096 to 2048 and watch your VAS :blink:

Well gentlemen just choose the lower bit rate sound and resize the livery textures from 4096 to 2048 and watch your VAS :blink:

That was literally all it took for me to eliminate them. It's quite strange how prevalent they are on other people's systems.

 

As I always say, When all else fails and you've tried everything... Reload your flight before descent.

OK where/how do I resize livery textures from 4096 to 2048 in the 777?

 

I have seen the lower sound setting and will change my option to the lower/lowest possible.

 

Franklin Duncan

OK where/how do I resize livery textures from 4096 to 2048 in the 777?

 

I have seen the lower sound setting and will change my option to the lower/lowest possible.

 

Franklin Duncan

 

You have to do it yourself via Photoshop ;-)

Just tried to do a long-haul flight from Heathrow to Tokyo in the PMDG 777-300 and I get out of memory 5 hours in over Russia.  This is the first long flight I've done and never had any issues with V1 of the PMDG with my current settings.  Very odd indeed.

I didn't have any OOM's yet but I did have the warning ping when I landed on a flight from EGLL to KLAX. I have since followed the recommendations people have posted in this forum and have completed a KLAX to EGLL without any issues. Turning off scenery not being used seems to be a big saver.

You have to do it yourself via Photoshop ;-)

I have never used photoshop but I guess it would not be much different than using Windows Paint?

 

I am not sure if I need to reduce the livery textures.

So far I have been able to reduce VAS enough with not using HD airport or other HD scenery textures, FSX slider settings, reducing or no AI traffic, etc.

 

but I have not done any long haul flights with SP1 either.

 

Would it be an idea that you post the reduced textures somewhere (I think you can share with dropbox) so others can use them as well?

Hi, I had succeeded in avoiding oom's with sp1 until yesterday. But then I made a quite short hop EDDM-LIRF with newly downloaded Alitalia 777-200LR and already in my freeware EDDM scenery I had only 1gb available vas ( I'm using fsuipc for monitoring remaining vas). Flying over the city of Munich available vas dropped to 800Mb but then after reaching fl370 increased to 1,25 Gb. When approaching Lirf ( ISD freeware) my available vas was reducing rapidly so that when parked to the gate only 150mb was left. And after couple of minutes oom and simulator closing.

 

I used ASN, FS Global mesh, FTX and FTX vector plu those two airport sceneries mentioned above. All my other scereis were ticked off in scenery config manager.

 

I doubt whether it was the alitalia livery or one or both of the airport sceneries but vas usage was at alarming level ( a leak maybe?) making pmdg t7 sp1 nearly unusable.

 

Petteri

 

 

I'm just trying to do a breakdown of how much VAS each addon uses

 

That will not help much!

 

To avoid OOM permanently you'd better go to your most demanding airport/surrounding with your 300ER, setup the most ugly possible weather switch from cockpit to outside and back and monitor if you still have at least about 300mb VAS left. (FSUIPC warning beep starts at 250mb if i remember correctly.)

 

if you achieve this without difficulty and uncheck every airport exept departure and destination in scenery library you should never have an OOM again.

 

But there is a second possibility having OOM due to missing desktop heap patch with Windows Vista/7 64bit

 

http://support.microsoft.com/kb/947246/en-us