Just making sure I get this rights: so you need to do this 4 point procedure even if your FSX default flight uses a default AC, and you want to set up a flight with the T7 right after starting the sim?

 

I had default FSX AC setup, that apparently wasn't enough to solve the issue.  The 4 step process I listed worked for me, I no longer leak VAS.  I'm certainly not trying to establish a golden rule, just letting you know what seems to have solved my VAS leakage problem after eliminating other variables.

I use res 2560x1600x32 and after a EGLL-KORD flight (UK2000 Heathrow X v2 / FSDT KORD), with UTX "world", FTXG, FSGRW with Rex 1024 textures and 1024 in cfg (DX9), I was at 2,8 Gb VAS.

 

So not much of a memory problem here

I envy you. These are the settings and the resolution that I run, buy my VAS starts higher and keeps disappearing the longer I fly. Wish I could figure out what's wrong. I deleted RAASPro and A2A's AccuFeel (which was disabled already) last night. Maybe that will improve matters.

I had default FSX AC setup, that apparently wasn't enough to solve the issue. The 4 step process I listed worked for me, I no longer leak VAS. I'm certainly not trying to establish a golden rule, just letting you know what seems to have solved my VAS leakage problem after eliminating other variables.

Thanks a lot for that answer! I'll try this and see if it improves matters. Fingers crossed.

VAS is a strange beast indeed. If I fire up FSL Concorde it will OOM before I reach FL100, even with 1920 res and only default scenery (!)

 

But any other aircraft, MD-11X, J41, NGX, 777, Duke / GNS530 with all scenery enabled, it never happens.

 

 

Thanks a lot for that answer! I'll try this and see if it improves matters. Fingers crossed.

 

Please do report back -- as I linked to another thread, this wasn't my idea, I used information from another user ... I honestly didn't think this was related to my VAS issue at all, but so far I can't explain any other reason why my VAS is no longer leaking.

FWIW, disabling HD Virtual Cockpit textures knocked a solid 1/2 GB off my VAS footprint w/ a near imperceptible reduction in visual quality (of the T7 at least).

 

I can almost guarantee this is texture thrashing at work (a 2GB+ video adapter may be in order). HD environment textures + HD cockpit textures + photoreal scenery and high terrain LOD all look very bad &@($* but it really hammers on the rendering engine. Scaling back on the texture load (even by 1 order of magnitude) has a significant impact on the simulation and also keeps the CPU less busy.

 

Dropping TEXTURE_MAX_LOAD down from 4096 to 2048 dropped me another 1/2 GB. These 2 changes alone took me down from 3+ GB to just below 2 w/ only a very minimal loss of fidelity (good texture filtering on your video card can make up a lot of that too). FPS went from 12 to 26 (this is parked at 4R at FlyTampa KBOS w/ MSE Mass 2.0, UT2, REX, and ASE) and my fans are a lot quieter

I made test flight from EDDP(payware) to LIME(freeware),

everythings normal, on arrival at LIME i had min 500000 free mem,

 

now im doing a flight from LIME to VHHH and free mem is slowly

rising up again, now at 900000 so lets see what is the result at the end VHHH.

 

Just testing to see if my modifications to the settings have done any good as i had OOM also when closing in the arrival airport...At least everything is performing nicely so far..

 

 

Please do report back -- as I linked to another thread, this wasn't my idea, I used information from another user ... I honestly didn't think this was related to my VAS issue at all, but so far I can't explain any other reason why my VAS is no longer leaking.

 

Hi Rob,

 

I have just completed my longest flight to date 11:20h from LIME to VHHH, and only my second flight without OOM. I followed your advise and loaded a default AC, then the 777F house livery, default AC again and then the 777F in Aerologic livery (all in the FSX main menu only). In addition I didn't load my flight plan into FSX (flew without MS ATC), disabled the LevelD.dll, did not use the checklist and used the PMDG default panel state (as opposed to the panel state I had created for myself). 

 

The end result is that VAS started at 2GB remaining at LIME, which dropped quickly to 1.6-1.7GB remaining after panning around the cockpit and preparing my flight. It dropped a little further to 1.5GB after takeoff, but crucially it did not drop further for the entire cruise which included day/night transitions. During approach to HK the VAS dropped to 1.2GB remaining and seemed to stay there once I was parked at the apron.

To give some frame of reference: yesterday when I flew the first leg of this trip from EDDP to LIME (just 1h) I had under 500MB left! And that was flying into a default airport with all other sceneries except EDDP (Aerosoft) disabled.

 

Now I have to figure out if this was just a coincidence and if not which of the above actions fixed or prevented the issue from occurring. In any case I am relieved that finally something is working! Thanks a lot for suggesting the AC loading procedure!

 

Have you done any more further testing with adding things back?

Have you done any more further testing with adding things back?

 

Good news, thanks for getting back to me, much appreciated.  Obviously I don't think we could ever positively say that the 4 step AC load process is a "golden" rule ... the software developer in me says that the 4 step AC process should not make a difference at all, but I have to keep my mind open to the positive results I got (which were good results) by implementing it. 

 

But in your case you changed a few other variables (LevelD.dll, etc.) so now you need to decide if it's worth your time validating the 4 step AC process.  Obviously I would like you to, but I can understand it takes time for all this testing.

 

I've added bglmanx.dll and couatl.exe (FSDT Add-On manager stuff) back without any VAS issues - but have not tested at a FSDT airport yet.  I still have A2A_Feel.dll (A2A C172 stuff) disabled and AccuFeelMenu.dll disabled (Accu Feel).  PMDG seems to have it's own "feel" so I'll probably leave Accu-Feel disabled for the PMDG.  I am having problems getting RAASPro to work, no errors or VAS usage, but it's not calling out runways or calling out anything for that matter (sound test worked but only when sound driver is set to stereo which is odd since PMDG sounds and all other sounds work fine with my 7.1 settings in my audio driver).

 

Rob.

 

EDIT: oh, and of course tried new REX textures and setup weather using FSGRW, all good on the VAS front with no leaks.

 

EDIT: Have you tried turning it off and on again?    Love that show!

In regards to this topic I think almost everybody is just guessing on what to do with those anoying OOM !!!. PMDG should release a patch ahortly to help manage these issues. Obviously, the T7 has issues with high VAS usage !!!

Edward

I had no problems after doing a 11 hour leg from ORD-DOH and that is with the FSDT ORD although the default Doha is installed.

In regards to this topic I think almost everybody is just guessing on what to do with those anoying OOM !!!. PMDG should release a patch ahortly to help manage these issues. Obviously, the T7 has issues with high VAS usage !!!

 

Wouldn't that mean your guessing also?   Without the source code to both FSX and PMDG 777 our only options are to best guess and work with what we have.  For sure PMDG 777 uses a lot of VAS so adjustments need to be made.  My original assumption/guess that my VAS memory leak was due to the PMDG 777 turned out to be false ... having a wrong assumption/guess was actually a good thing as it has helped me find a real solution.

 

I can avoid OOMs, what I was trying to do is locate/stop a VAS memory leak.  I've been successful with my 4 step AC process prior to flight ... I agree it doesn't make much sense (and it was someone else that put me on to this and is also part of an acknowledge FSX bug) but it's working for me and yes it's a guess but so long as it keeps working for me it's a guess I plan to keep using.

hey guys what is VAS?

 

 

hey guys what is VAS?

 

Virtual Address Space on a 64bit OS you get 4GB, on a 32bit you get 3GB (with appropriate settings).  I like to leave myself about 500MB VAS headroom when flying from A to B ... but for special case screenshots I push it as close as I can to the VAS limit.

Obviously I don't think we could ever positively say that the 4 step AC load process is a "golden" rule ... the software developer in me says that the 4 step AC process should not make a difference at all

That is a good example of what I meant when I said computer problems or the solutions to computer problems are often not very logic :-)

 

I was just waiting for an example like this to pop up, haha.

 

But its a great find, and I have this thread stored in case I have similar problems.

 

I hope you can identify the source of the memory leak so it can get fixed.

 

 

I hope you can identify the source of the memory leak so it can get fixed.

 

It is fixed, that is what the 4 step AC process did for me, fixed my VAS leak. 

 

 

 

That is a good example of what I meant when I said computer problems or the solutions to computer problems are often not very logic :-)

 

Well my friend, they may not appear logic, but there will be a very logical answer ... but without source code it would be difficult if not impossible (and time consuming).