That's interesting. I just finished a 15 hour KLAX-VHHH flight using same STAR but 07R. The VAS usage went from 2.6GB at KLAX to 3.6 about 200 miles from VHHH. I wasn't sure I would make without an OOM, so I save the flight and started it from 200 miles out. VAS started at 1.9GB and went to 2.6 on the runway. No way I would have made it without a save. This is in the 777 update that is ready to be sent to Aerosoft. I can't say it is the plane because I did not do a reinstall of ASN. I was doing this flight to see what would happen without an ASN reinstall. Now I know.

When did you input arrival SID/STAR into fmc? I suspect that entering arrival infomation just before descent helps solve oom which may associate with AIRAC Cycle...

Listen up!

 

We'd like to have as many of you from this thread as possible test the fix we think we've come up with. The results with the beta team have been somewhat ambiguous, so we'd like to go to the source of the reports on the issue here and see what you guys think. Email me directly at [email protected] with the subject "777 VAS test" and we'll reply back with instructions.

 

Thanks

Done

 

 

When did you input arrival SID/STAR into fmc?

During the climb out of KLAX but that should not make a difference.

I'll have to try VHHH when I return from Easter weekend travel.

 

But does indeed look like 7L and 7R's missed approaches have the radial intercept to a fix that was characteristic of the KLAX VAS bleed.

I am doing KLAX-VHHH again after a reinstall of ASN, with all weather cleared and no traffic.

I am doing KLAX-VHHH again after a reinstall of ASN, with all weather cleared and no traffic.

Michael, we are still testing a PMDG 777 for VAS use so I'm pretty sure it's not sent to Aerosoft yet.  Perhaps you're crossing types with the PMDG NGX?  Last build that Robert pushed out to us is doing remarkably well. Hopefully it will be ready for release soon... as in PMDG soon of course.

Michael, we are still testing a PMDG 777 for VAS use so I'm pretty sure it's not sent to Aerosoft yet.  Perhaps you're crossing types with the PMDG NGX?  Last build that Robert pushed out to us is doing remarkably well. Hopefully it will be ready for release soon... as in PMDG soon of course.

Dan

I know it hasn't been sent to Aerosoft yet. I am not confusing the T7 and the NGX which has been sent to Aerosoft. The flight is halfway to VHHH and I don't see any VAS leakage.

 

 

The flight is halfway to VHHH and I don't see any VAS leakage.

 

Sorry, I must have misread an earlier post to prompt that.  Anyway, the VAS problem was isolated to certain missed approach procedures and beyond that I'd just be guessing so rather than do that I'll just add that I just lost my B77W AAL VHHH-KDFW flight..... tried turning off some ORBX scenery enroute and I ran into an appHang that never came back.  Note to self: Don't do that!

The flight is halfway to VHHH and I don't see any VAS leakage.

Try to enter arrival SID/STAR on fmc earlier...Some comments above in this post mentioned the possibility of entering problematic approach in fmc leading vas leakage during cruise.

The KLAX-VHHH flight is complete with ABBEY3A and ILS 7L entered into the FMC on the ground on KLAX. The VAS usage was 2.3GB until about 150 miles from VHHH and it gradually increased to 2.7 at VHHH. So the reinstall of ASN did the trick. Now here is the really odd part about this. When I installed the current 777F I am using I reinstalled ASN and did a 12 hour flight from EDDP-KLAX with no VAS problems. After that I went into the OC concerning the NGX. No updates were shown available for either the T7 or the NGX. After that I did the KLAX-VHHH flight mentioned in a post on the previous page of this thread. So the deal is I must reinstall ASN anytime I go into the OC. Odd? But that's the way works on the hardware and software combination I have.

Try to enter arrival SID/STAR on fmc earlier...Some comments above in this post mentioned the possibility of entering problematic approach in fmc leading vas leakage during cruise.

I am not sure I understand what you are saying. Try saying it a different way if you could please.

I just perform a test, flying from RKSI back to VHHH. The arrival SID/STARS is not entered until descent, so far the vas is VERY STABLE without continuously increasing. At past. I was used to input SID/STARS before departure from the origin, and oom always occured then. BUT NOW, I notice vas will be very stable if SID/STAR is not entered/chosen during crusing stage of the flight yet ...

 

 

As shown above, I havent chosen arrival star for VHHH, so vas usage is just 2.2GB, JUST 100MB more than that when initial climb above RKSI. At the past in the same position (waypoint), the vas would be around 2.9-3.1GB!

 

Sorry for my bad English, hope you can understand

The arrival SID/STARS is not entered until descent, so far the vas is VERY STABLE without continuously increasing.

You are correct. Right now if you have VAS leakage due to an approach such as ILS 07L at VHHH this is the only way to make it to your destination without having an OOM. You can enter the STAR (ABBEY3A) into the FMC at your origin airport but not the approach. PMDG is working to correct this issue in a future release.

 

You are doing it correctly as outlined in your post.

I don't know if this P3D related on T7 related but whenever I go outside - spot view. I gained 200mb of vas and it not going back down after I went back to VC

I don't know if this P3D related on T7 related but whenever I go outside - spot view. I gained 200mb of vas and it not going back down after I went back to VC

This is typical of most aircraft, loading the exterior model uses some VAS.

Are there any more developments with this?