Hello everyone, I am on my second flight with the 777 and I am having oom issues.  Would it be possible for a bad repaint to cause this?  I ask because I had no issues yesterday on my first flight but today after modifying the textures of a ual repaint on avsim to include an alpha channel for see through cabin windows I am getting a slow continuous climb of vas usage until fsx crashes.  I have read and followed all of the common oom fixes.

 

Thanks,

 

Mike Iacovetta

Are you flying w/ the same parameters as yesterday's flight? ie. same locations, same weather, same add-ons running, same configuration?  That would help establish a baseline to find out what is driving the VAS usage up.

 

Richard

Well yesterdays flight was ksfo to phnl using fsdt phnl and ksfo scenery.  The only difference is today I am flying phnl to kiah and have megascenery az socal nm and west tx loaded as those are the states I am flying through.  The inital 3 hours of the flight were over the same area with pretty much the same weather and I was getting an oom issue.  I dont think the photoscenery is to blame as  I have never had a problem with those scenery areas with the ngx and the vas starts out fine once fsx is loaded.

You need DX10.

Well yesterdays flight was ksfo to phnl using fsdt phnl and ksfo scenery.  The only difference is today I am flying phnl to kiah and have megascenery az socal nm and west tx loaded as those are the states I am flying through.  The inital 3 hours of the flight were over the same area with pretty much the same weather and I was getting an oom issue.  I dont think the photoscenery is to blame as  I have never had a problem with those scenery areas with the ngx and the vas starts out fine once fsx is loaded.

 

In the PMDG manual for the 777, it states that photoscenery is a big factor for the OOM issues, especially with the 777.  It's a different product than the 737, and thus has different limitations.  Read the manual if you haven't done so already.

 

John

I was experiencing OOM's frequently with a very powerful machine, I was instructed after several areas to check from PMDG tech support, turns out disabling my MegaScenery Socal V2 was the culprit. I was advised that photoscenery never leaves the VAS or the cache and hangs in there causing the inevitable OOM. Now I have it disabled (777 Flying Only) my airports are HD, clouds HD, TML 4096 and life is great! Left sim running for DAYS, no joke, DAYS and she is still flying.

 

Angelo 

I've been having my own OOM issues. I haven't found the culprit(s) yet, but i am about to investigate to get to the bottom of my issues.  A few things. You are dealing with FSX and the apps that run through it competing for VAS allocation.  There is an app or I should say program called process explorer, I would suggest getting that (a search of the forums will give you a link) and with that or alternatively (you can use FSUIPC) with these tools you can measure the VAS space that the different sceneries, and addons are using. And based on your findings you can adjust LOD, or texture resolutions, or sliders to try and reduce the overall VAS footprint of FSX.

 

The one thing I can't answer as I haven't found any reference to it in my research is why VAS is used up very quickly in some circumstances and grows very slowly or not at all in other circumstances.  In KSEA for me w/ ORBX PNW, ASN, and the NGX, my VAS hits 3.8 in about 20 mins of sitting at the gate.  If I find and answer I'll share it with you.

 

Richard

I was experiencing OOM's frequently with a very powerful machine, I was instructed after several areas to check from PMDG tech support, turns out disabling my MegaScenery Socal V2 was the culprit. I was advised that photoscenery never leaves the VAS or the cache and hangs in there causing the inevitable OOM. Now I have it disabled (777 Flying Only) my airports are HD, clouds HD, TML 4096 and life is great! Left sim running for DAYS, no joke, DAYS and she is still flying.

 

 

 

Angelo

 

 

Hi Angelo - if you don't mind could you list the add-ons that you leave running when using the 777.   With both the 777 and 737NGX, I use ORBX regionals (PNW, SAC, etc. and some of their local airports), ASN w/ Rex Textures, FS2Crew, GSE or GEX (ground services), Ezdok, and Track IR.

 

Pilot53 - what else are you running besides the MegaScenery and FSDT airports?

 

Richard

Sure I have all PMDG, FSDT all, Flightbeam all, flytampa, ASN, UTX, GEX, REX, UT2, FSG2010, GSX, AES. Throw in a couple of aerosoft and Latin VFR airports as well.

I have unchecked the aerosoft airports and the fsdt airports I fly infrequently. However my SoCal area is dense all those airports are on except megascenery SoCal.

I have unchecked the aerosoft airports and the fsdt airports I fly infrequently. However my SoCal area is dense all those airports are on except megascenery SoCal.

Ok here's an update, to much photoscenery does indeed cause issues with some users but if you ready my post something else is causing a problem for me.  The problem I am having is: vas usage increased over time eventually hitting 4gb over the course of 3 hours or so.  Ive tried running fsx again with the same scenery installed but this time the vas usage remained steady.  I think the problem might have had to do with switching aircraft over and over and alt tabbing fsx.  Earlier today I had problems causing controller disconnects so I was forced to switch from the 777 to a default aircraft and back to the 777 again to get my controller online.  Also because of problems with ezdok I was switching views to play with the settings.  Maybe some of this had caused a memory leak?  It seems in this case its not just a matter of high res settings causing issues but instead a memory leak that causes vas useage to climb continuously.  

Ok here's an update, to much photoscenery does indeed cause issues with some users but if you ready my post something else is causing a problem for me.  The problem I am having is: vas usage increased over time eventually hitting 4gb over the course of 3 hours or so.  Ive tried running fsx again with the same scenery installed but this time the vas usage remained steady.  I think the problem might have had to do with switching aircraft over and over and alt tabbing fsx.  Earlier today I had problems causing controller disconnects so I was forced to switch from the 777 to a default aircraft and back to the 777 again to get my controller online.  Also because of problems with ezdok I was switching views to play with the settings.  Maybe some of this had caused a memory leak?  It seems in this case its not just a matter of high res settings causing issues but instead a memory leak that causes vas useage to climb continuously.  

 

If you are switching aircraft without restarting FSX, I would expect problems.

 

John

Update:  I tried replicating the problem again this time switching from the 777 to a default aircraft and back again with no memory leak.  Seems it might have something to do with switching tasks back and forth between fsx.

Explain a bit more about your controller ceasing to communicate with the 777. This has happened to me and I assumed my yoke was going bad, but restarting my PC and all is well. This never happens with any other aircraft so I am glad you mentioned that.