I think Kyle is correct with the assumption that the version of NAVDATA installed contributes to the VAS leakage and ultimate OOM when approaching KLAX.

With 1503 I started to experience OOMs when approaching KLAX for the first time. I lowered my FSX settings and repeated the same flight from KIAH (Flightbeam) to KLAX (FSDT) and observed VAS usage using Sysinternal Process Explorer. ASN was the weather platform used.

I observed the gradual increase in VAS which coincided with imputing the approach and destination runway while enroute to KLAX. The arrival SEAVU 2 for 25L. On final OOM. This could be reproduced again and again.

I then rolled back to 1412, increased my FSX settings including autogen and then repeated the flight. No OOM with VAS after landing 3237204.

On the runway at KIAH prior to takeoff, VAS was 2761708 which dropped to 2740884 2 hours into the flight.

I have no idea why this has occurred but rolling back the NAVDATA from 1503 to 1412 has allowed me to again fly to KLAX without running out of memory.

 

Thanks for sharing the information and your experience!

 

 

 

It is my understanding this issue is with 777 not NGX

 

On my system, yes, the 777 seems to be the only culprit here.  I personally haven't had any problems with the NGX (including SP1d).  Have flown some of the problematic approaches multiple times in the NGX and couldn't repeat the results seen in the 777.  If anyone out there can systematically and repeatably put the NGX in a scenario where they are seeing a VAS leak like the 777, please speak up and share details/data.

I didn't have the time to fly my planned KLAX-NZAA flight so I did a shorter one. I know this is probably useless info for you, but I flew EHAM (no scenery) to TNCM (FlyTam Scenery) overnight with practically no VAS issues. I did reinstall ASN first though. I suspect the reinstall + the fact that the NAVDATA isn`t bugged for TNCM both helped.

 

Left EHAM with a total VAS usage of 2.7GB, cruise VAS was actually at 2.4GB and landed at TNCM with a VAS usage of 2.6GB.. no problem.

 

 

As for FSX SE, I`m going to think about it. I would like to move on to P3D one day, only when they get 64-bit support.

 

 

I will let you know when I fly to (or from) KLAX again next time, and will downgrade my NavData.

No data is useless. Flights without the leak are just as informational as ones with the leak. Thanks for sharing!

Well this is extraordinary I did the test and with the T7 on the runway at some out of the way place and the approaches mentioned above loaded there is VAS leak of about 200mb/hr.  With nothing loaded on the FMS or other approaches eg CYVR 26L no VAS leakage. Curiously seem to be T7 thing - no VAS leakage with the NGX! This is with 1502 - how do you roll back to an earlier AIRAC cycle? 

 

Bruceb

If there's an error in the data presented, or the NavData is fine, but some obscure condition in the data fools the T7, the T7 should handle it gracefully and free up memory. So it seems like an obscure problem found, but no doubt could be fixed fairly soon by PMDG if the information posted in this discussion is repeaatable.

Are the same results found with NavDataPro and Navigraph?


 

how do you roll back to an earlier AIRAC cycle?

With the PMDG we get two folders you may have backed up:
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X ORG\PMDG\NAVDATA
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X ORG\PMDG\SIDSTARS

Bruce, you may find an older .zip in your downloads from Navigraph contains the NavData installer.


 

Last night I tried a flight from YSSY to KLAX and after about 3hrs P3D crashed due to the mentioned VAS leak. I wasn't aware of the problem regarding KLAX and entered the STAR (BUFIE3 with ROSIN transition) and ILS 25L into the FMC before I departed SYD. 13hr flight screwed up. :(  Unfortunately I don't have any numbers regarding VAS usage, the only thing I noticed was the ding dong sound of FSUIPC due to low memory after about 2hrs.

 

Hopefully PMDG fixes this issue. The used AIRAC was Navigraph 1503. I hope to give it another try in the night of thursday to friday, this time without entering the STAR and ILS...

Thanks Martin and Bruche, for trying this and sharing your results. Again, if anyone identifies a repeatble approach that leaks VAS outside of those at KLAX and KJFK identified already, please share that too so we can investigate any differences or commonalities.

 

Probably no difference in results, but has anyone tried these "leaky approaches" in the -300? (I only have the -200, but for completion's sake to test out another variable or two)

 

And while I'm thinking about it, how about FSX:SE for anyone?

A little remark to my former post: my earlier flights EDDF-KATL and KLAX-YSSY were uneventful. No VAS problems at all. All flights with the Delta B77L until now, didn't try the -300ER yet.

Still with the defective 1413 data, KLAX-NZAA (exactly 12hrs) did not cause any issue. I maybe even would have been able to fly back to KLAX without quitting the sim.

 

I probably won't have the time for a few days, but when I do, I will downgrade to 1412 and fly EGLL-KLAX and load in 25R ILS for KLAX while still on the ground in EGLL. That should tell me if 1412 is fixed.

I have FSX-SE installed with PMDG 737 NGX  & PMDG 777 I have done several flights from NZCH to YSSY ( Christchurch NZ to Sydney Australia). 2 hours and 20 minutes get OOM. I have registered FSUIPC and autosave enabled so I was a able to recover the saved flight and continue to make  safe landing a Sydney Airport. I have logging enable and save to log file.

 

I think the FSUIPC is great as there is no BLACK and WHITE solution as everyone has previously mentioned Addons, Software etc all have percularities that affect everyone diffrently. A new genearation 64 bit flight sim software is the only solution.

 

If you have no OOMs great dont change anything (pretty difficult when every developer has new SP etc)

If you have OOMS there is still hope. My advise disable every addon or uninstall and retest until flight sim stability returns like a long lost friend. Get FSUIPC and enable Auto saving your flight. AWEsome you can at least pick up were you left off I like this especially if you fly in a virtual airline. 

 

Paul

No VAS issue KTPA-EGLL on 1412 data.

 

Looking to do a 10hr+ flight from anywhere to KLAX, and fly the 25R ILS with the 1412. See what happens. If I get no VAS error, the problem is definitely a mixture of PMDG 777+1413 or more recent data.

No VAS issue KTPA-EGLL on 1412 data.

Navigraph or NavDataPro? Can't assume these are the same...

Oh sorry, Navigraph.

I still haven't tried the approaches causing the leak on the old Navigraph data though, but according to this thread, the VAS issue happens with 1413 or later.

Navigraph

Cheers. Would be interesting to try the NavDataPro AIRAC...

Okay, I just arrived at KLAX after an 13h30min flight from YSSY and no OOM so far! This time I didn't enter the STAR and RWY until I was almost at the end of my route (about 80nm from FICKY) and at first I just entered the STAR and while descending through FL250 I entered ILS 25R. That seems to be a good workaround until there's a fix from PMDG. I'm still using Navigraph 1503.