I have some advice, do not edit the missed approach data via the fmc! Before I edited the txt files of the airports I fly to and from, I tried removing the lines after the runway and the fmc sure did not like that. It locked up, wouldn't let me change anything.C ould not change even the cruise settings, or go direct to another waypoint. It flied the route fine but was locked in. I learned my lesson only edit the data in the txt files! - David Lee

I have some advice, do not edit the missed approach data via the fmc! Before I edited the txt files of the airports I fly to and from, I tried removing the lines after the runway and the fmc sure did not like that. It locked up, wouldn't let me change anything.C ould not change even the cruise settings, or go direct to another waypoint. It flied the route fine but was locked in. I learned my lesson only edit the data in the txt files! - David Lee

I've edited YVR and SFO so far as Dan suggested in his post here from May 30th. So far is working great. I plan to save a copy of the edited files and paste them into future AIRAC updates. Hope PMDG can get a fix pushed out soon.

 

 

I've edited YVR

What approaches were you having problem with? I have done EDDF-CYVR probably ten times by now but I have always an done an ILS Approach to 08L/26R without incident and approach has been part of the active route for the whole flight - no time acceleration.

What approaches were you having problem with? I have done EDDF-CYVR probably ten times by now but I have always an done an ILS Approach to 08L/26R without incident and approach has been part of the active route for the whole flight - no time acceleration.

Someone in this thread I believe mentioned they were getting the memory leak with 8L/26R so I went ahead and removed the missed approach stuff just in case.

 

 

Someone in this thread I believe mentioned they were getting the memory leak with 8L/26R so I went ahead and removed the missed approach stuff just in case.

How quick we forget. I wrote the post on 15Dec2015.

they dont care mate.  one day they might acknowledge the 777 is buggy as ###### in p3d... but they wont.

 

 

but they wont.

 

Nonsense, they've been very clear that there are known bugs but they're not going to stop working on the 747v3 to revise the 777.  Bugs are tracked in a system they use to keep track of them until they do assign resources to the product.  The best way to get things fixed is to do as Michael and a few others do and that is submit it on a trouble ticket. This gets it into the bug tracker if it is validated.

Nonsense, they've been very clear that there are known bugs but they're not going to stop working on the 747v3 to revise the 777.  Bugs are tracked in a system they use to keep track of them until they do assign resources to the product.  The best way to get things fixed is to do as Michael and a few others do and that is submit it on a trouble ticket. This gets it into the bug tracker if it is validated.

A bug that crashes and causes us to not be able to finish our flight, is HUGE. And going in ourselves and editing navdata files is unrealistic because it removes the go around procedure, and will cause navigraph to not support if we edit the files ourselves. This should have been fixed a long time ago - David Lee

No need for theatrics... just don't select your approach until 100 nm before TOD or thereabouts. Fairly realistic procedure.

FWIW, I hald to delete the missed approach stuff from LSZH. Got an OOM with the 777 coming from Dubai. Redid the flight after the edit and had no issues.

No need for theatrics... just don't select your approach until 100 nm before TOD or thereabouts. Fairly realistic procedure.

If I do not change the approach files and remove the approach, it doesn't mater if it is 100 or 50 miles out, I will leak enough vas to cause an OOM on landing, or after landing. That isn't theatrics, that is the fact of life for those of us stuck with FSX. I have to fly with all custom AI traffic I worked hard to put in, OFF. I can't use any ship traffic either. I only have enough VAS for the departure airport, my airplane, and arrival airport. Do you want to help me pay for a nice new P3D v3 and the PMDG 777 products for P3D? I am unemployed and stuck with my FSX installation with all the addons I had purchased when I had a well paying job. Finally was able to afford the -300ER addon in May for FSX. - David Lee

 

 

is the fact of life for those of us stuck with FSX.

David

I understand  where you are coming from and feel sorry for you but look at the title of this thread - "P3D V3 FMC memory leak back?" P3D is certainly not a solution to the VAS leakage problem.

A bug that crashes and causes us to not be able to finish our flight, is HUGE. And going in ourselves and editing navdata files is unrealistic because it removes the go around procedure, and will cause navigraph to not support if we edit the files ourselves. This should have been fixed a long time ago - David Lee

I believe that the approach-related VAS bug is specific only to the P3D version of the 777. The FSX version had a similar bug, which WAS finally fixed in an update.

 

As far as I know, PMDG has not acknowledged that this bug does actually exist in the P3D version, but it appears to have been pretty conclusively demonstrated by many of the same individuals who uncovered the similar issue in the FSX version, using repeatable and methodical test procedures.

 

P3D in general, has much better VAS management than original FSX, which is to say that with the exception of the approach VAS bug, (which only affects a small subset of airports), it is much more likely that one can complete a 777 flight in P3D without running out of VAS, than in FSX - all other things (weather, AI, scenery etc.) being equal.

 

I understand that P3D is not an option for you for financial reasons, but have you considered trying FSX-SE, which has much better VAS management than original FSX? I'm not sure of the current price for SE, but DTG often puts it on sale for just a few dollars.

 

My apologies if you are already using SE...

 

 

I believe that the approach-related VAS bug is specific only to the P3D version of the 777. The FSX version had a similar bug, which WAS finally fixed in an update.

The issue still exists with FSX such as all VHHH runways, ILS KMEM 36R, and ILS EDDP 26L. The update in May 2015 fixed some of the issues such as ILS KLAX 25L. So the VAS leak affects all three platforms.

 

FSX-SE and P3D should handle the leak better than FSX but as far as I know the only method that is close to beating the leak is to use time compression to reduce the amount of time the 777 is exposed to what ever is going on in memory.

If you read through the whole thread I think there is a post where someone said they submitted a support ticket and pmdg acknowledged the bug but had no solution as of yet.