The anticipated update addressing the NOT IN DATABASE was released, works now again for me

This is build 145.

The build addresses:

• Continued navigation update logic improvements

• Added FACTORY RESET> option in PMDG SETUP> to purge the navdata from within the sim

• Fixes to the image file bloat that was causing high VRAM use

2 hours ago, DAD said:

The anticipated update addressing the NOT IN DATABASE was released, works now again for me

This is build 145.

The build addresses:

• Continued navigation update logic improvements

• Added FACTORY RESET> option in PMDG SETUP> to purge the navdata from within the sim

• Fixes to the image file bloat that was causing high VRAM use

Now the one in bold is interesting. I noticed that I was getting VRAM messages when loading the F and LR after installing the 2.04.144 update, so hopefully this is the fix for that!!

Edited August 13Aug 13 by Christopher Low

3 hours ago, Christopher Low said:

Now the one in bold is interesting. I noticed that I was getting VRAM messages when loading the F and LR after installing the 2.04.144 update, so hopefully this is the fix for that!!

That issue should be solved Christopher based on the confirmation from users in the 777 PMDG forum today. Looks like a navdata update went awol which increased the folder size in Asset_77L_Common folder by many GBs.🫣

34 minutes ago, 787flyer said:

That issue should be solved Christopher based on the confirmation from users in the 777 PMDG forum today. Looks like a navdata update went awol which increased the folder size in Asset_77L_Common folder by many GBs.🫣

I remember when p3d did that once with a bgl that was 3 gig

• Fixes to the image file bloat that was causing high VRAM use

Just installed the 777 about a week ago and noticed big time VRAM usage compared to other add on planes . Where something like the Ifly737max was using 17GB , the 777 was consistently using over 20GB ( i have a 4090) and sometimes maxing out VRAM.

4 hours ago, 787flyer said:

That issue should be solved Christopher based on the confirmation from users in the 777 PMDG forum today. Looks like a navdata update went awol which increased the folder size in Asset_77L_Common folder by many GBs.🫣

I never really noticed any excessive vram usage with the 777F. And this was during 14-hour flights in and out of major airports. Have to keep a look out. Only issues I've ever had with the 777 was not being able to update navdata using EFB. Always had to use the navigraph hub.

The excessive VRAM usage problem was only an issue after installation of the 2.04.144 update. Have you flown the 777F recently?

32 minutes ago, Christopher Low said:

The excessive VRAM usage problem was only an issue after installation of the 2.04.144 update. Have you flown the 777F recently?

Yes almost eveyday.