VHHH-KLAX in T7 using 1502 except for KLAX.txt in SIDSTARS from 1407 R2.  Takeoff 2.3GB, across the Pacific 2.2GB, 2.4GB over California and 3.0GB at KLAX. No VAS leakage.

Typing on my phone, sorry for the brevity:

 

Flew my usual JFK-LAX test case overnight with the hybrid KLAX.txt file. Added in the APPROACHES section from 1502. OOM'ed over Nevada, about 4.5 hours into flight. So up to this point, since everything in KLAX.txt was 1502 except Gates and Approaches, and changing only the Approaches section last night led to the VAS leak, our problem is possibly pointing to that section.

 

I'll divide and try to isolate if it's an individual procedure.

I'll divide and try to isolate if it's an individual procedure.

If it helps any the two approaches were 25L. The first one had a IAF of RIIVER and the second was a vector to GAATE.

 

Hi Richard,

 

Congratulations to your useful and well written post !

 

After PMDG SP1d  has been installed along FTX vector and FS Global 2010 I've passed to have OOM issues ( VAS beyond 3.45..... ).

 

I'm going to test what you have been POST here.

 

 

Thanks for sharing with us.

 

Warmly,,

 

 

Marco Aurélio

 

You are very welcome Marco, hope this helps with your OOMs, there is nothing more frustrating than losing the sim after that 9 hour haul and executing the perfect approach...

 

Richard Bansa

If it helps any the two approaches were 25L. The first one had a IAF of RIIVER and the second was a vector to GAATE.

Good info, thanks. I think I'm going to try my test scenario for an hour or so a few times tonight, selecting a variety of different approaches and runways.

If it helps any the two approaches were 25L. The first one had a IAF of RIIVER and the second was a vector to GAATE.

 

Do me a favor, if you can, try an RNAV approach to 25L and a different approach to a different runway.  I'm noticing on this attempt that if I select ILS25L or ILS25R, I'll see the VAS leak, but if I select the ILS24L approach, it seems to stop bleeding.

Do me a favor

When I read your post I was already doing a EDDP-KLAX flight. In RTE2 I entered an RNAV 06R and activated it. After 6 hours I changed it to RNAV 25R and left RTE2 active for another 2 hours. No VAS leakage on either of the two approaches. Sorry I didn't do 25L but I mistakenly selected 25R and by the time I realized it there was not enough time left in the flight to get any meaning full data on 25L.

Hi simmers,

 

 

it´s quite funny, I will get the typical DING DING warning from windows, but my P3D 2.2 is not crashing with the truly unloved OOM message ..... My VAS is round about 2.8 MB when the DING DING sound will appear.

 

In another forum, someone gave the tipp to press ALT+Enter twice in a second to avoid a crash.

 

Greets Pepe

Hi simmers,

 

 

it´s quite funny, I will get the typical DING DING warning from windows, but my P3D 2.2 is not crashing with the truly unloved OOM message ..... My VAS is round about 2.8 MB when the DING DING sound will appear.

 

In another forum, someone gave the tipp to press ALT+Enter twice in a second to avoid a crash.

 

Greets Pepe

The "ding" tone is actually being generated by FSUIPC. If you don't have FSUIPC installed, you won't get the audio warning of low VAS. 2.8 GB VAS in use is way below the warning threshold in any case - Could something else on your system be responsible for the sound?

Do me a favor

On second thought I believe there was VAS leakage on RNAV 25R. Part of the time that 25R RNAV was an active approach, Process Explorer stayed at 2.884GB. Task Manager showed it still running but the Virtual Size for all services stayed the same. Once I got Process Explorer working again the VAS usage jump to 3.1GB. At that time the plane was over ORBX Pacific Northwest which I don't think caused the increase in VAS.

On second thought I believe there was VAS leakage on RNAV 25R.

 

No problem, at this point, I'm trying to systematically go through each approach.  Then I guess I need to try to decipher what the difference is between them; other than that, unfortunately, I'm going to be flat out of ideas if there isn't anything that stands out (since, obviously, I'm not as smart as the folks who coded the aircraft or understand how it interfaces with navdata).

I'm trying to systematically go through each approach.

I count 27 approaches on the 05 Feb 2015 Terminal Procedures You realize I got the VAS leakage for RNAV 25R using 1407 R2. So 1407 is not the panacea I thought it was. I am fortunate that I use ILS 25L for all approaches and landings.

Hi guys

Just trying to get back into my T7 after months of non use due to OOM frustration. Hence trying to plough through this, and many other threads.  I'm intrigued....  All you guys flying in and out of KLAX....  Are you using DEFAULT KLAX or an aftermarket addon?  I do not have ASN installed but do use Opus.  I use Aerosoft LAX, and cannot get my T7 within 10 miles of the place before being hit with OOM;( This applies with pretty much ANY scenery or traffic settings applied!  Got ALL my other airport and scenery addons DEselected too.  Bah humbug! ;-)

Here is something interesting from real world aviation. I maintain several aircraft for a 135 charter operator. I am responsible for loading the monthly FMS database updates - which are supplied by either Jeppesen (for Rockwell Collins systems) or Honeywell for their own FMS models.

 

One of the aircraft is a Gulfstream G-200 with a Collins Proline 21 FMS - pretty much state-of-the-art, though this particular installation is 6 years old. We subscribe to the Jeppesen worldwide database for this aircraft, as it does a lot of international trips.

 

Never had an issue loading the Nav Data updates until last month, with cycle 15-01. I normally download the data from the Rockwell Collins web site to a USB thumb drive, which is then plugged into the data port in the aircraft. I then configure the two FMSs to load the new database from the thumb drive, and walk away. It typically takes about 45 minutes, after which the FMSs reboot, and the new database shows on the Ident screen.

 

But... Not this time. After 45 minutes, I went back to the aircraft to find... The two FMS CDU screens blank, except for a single text message "OUT OF MEMORY"!!

 

After an initial "WHAT THE..." moment, all I could do was to start laughing, considering the utter irony of the situation - which only a devoted simmer could appreciate. I had just literally OOMed a real aircraft!

 

Anyway, a call to Rockwell Collins tech support revealed all. The worldwide navigation database has been growing enormously over the past few years, with dozens of new RNAV procedures being added every month. The long and short of it is that the world database will simply no longer fit in the available NVRAM memory of specific Proline 21 FMS modules manufactured before approx 2010. We are now facing a very expensive hardware update to the two FMS modules to add more NVRAM if we want to use worldwide Nav databases on this aircraft. The short term solution is to either load a regional database (North and South America only) or one of two truncated worldwide databases that Rockwell Collins has made available for aircraft operators in our situation. Unfortunately, the truncated databases make it impossible to have western and eastern hemisphere airports loaded at the same time - which makes trips from North America to Europe impossible - so we have no choice but to do the hardware upgrade.

 

In any case, if the 15-01 database is the "straw that broke the camel's back" for real aircraft FMS systems, I wonder if something similar could be going on in the simulated FMS for products like the 777?

 

Thanks for sharing this, I'm not having OOM problems but it is very interesting how this arises from a software development and engineering point of view. At the end of the day the real thing and FS both use the same Navdata and this data is stored on a computer. Unfortunately the sheer fact that to be used, anything loaded into a computer must be loaded into memory is something often overlooked by software/hardware developers in the longer term. It may soon be necessary for us to split our FS navdata into regions as the files grow in size.

 

My guess is a revolutionary change is required to solve this rather than an evolutionary one but ultimately the problem will get worse year on year, many manufacturers are already wising up and future proofing their existing FMS hardware. The paper link below may be of interest, most interestingly is the fact the 787/380, both the very latest aircraft are fitted with almost 20x the amount of memory of any other aircraft... Maybe a sign of things to come.

 

https://www.mitre.org/sites/default/files/pdf/12_1324.pdf

Are you using DEFAULT KLAX or an aftermarket addon?

I am using FSDT KLAX and MegaSceneryX So Cal.