Where do you find this? I tried looking the other night when I did my flight however I must have looked over it and ended up dialing in the Baro for about 5 minutes. Unbearable! 
I will use your method until they fix it in an update. I must admit I thought we would have seen the update for the 777 by now that was meant to release shortly after Sim Update 4.
Thanks mate!
Select the MENU button on the CDU, then enable EFIS CTL by selecting ON at 1R, then select EFIS at 2R. (1 than 2 in the image below.)
From the EFIS CONTROL page, you can directly enter any valid value in the MINS SET field at 3L.
I fly the 777F most of the time without too much issue except the wing texture/tire fix. Switched to do the 773 for a pax flight and there are still LOD issues and the wing/tire fix only works via the FMS menu and not via the EFB.
These are both Marketplace versions and the PAX Version is still one version behind.
What is PMDG waiting for to just push their latest PAX version to Marketplace ?
What is the status on the sounds for the 77W? Still the regular old vacuum cleaner 
or is it already updated?
I noticed this the other day and wondered what was going on. @TheFalconOne Is this known for Xbox users or should I file a ticket? Thanks.
Today, 22:16
Captains,
I just posted my first information update of 2026 in a separate thread you can read here.
I wanted to address one additional topic separately because I think it is important.
What the Heck Happened to the 777 Sound Update?:
We currently have a sound package for the 777 fleet in development.
We have been talking about this for some time, and it has left some users rightly wondering “what gives?”
I want to offer an apology for the fact that it has not been released. There are a ton of reasons why, all of them related to decisions I have to make when allocating developer resources on projects at PMDG. All of those decisions were the right decisions to make, most of those decisions were easy, but a few of them were really complicated and difficult. None of them really matter to you, and none of them would have come to your attention except for one thing:
I made the mistake of telling you about this new 777 sound feature before I should have.
I love our products, and I think I work with a team of the most talented devs in the business. Any one of you should be so lucky as I am to sit down every day and problem solve with a team of developers who are so genuinely innovative, thoughtful, creative, funny and hard working. I don’t impress easily, as my perspective in simming is reality based, so when members of the dev team roll into a meeting to share something they have done that impresses me- my inner-simmer comes out and I get excited. Most times I sit on my hands rather than telling you about these things, because it will be some time before you see the feature in finished form.
We rebuilt our sound team in 2024/2025 in order to improve that weak area of our products. When they shared their 777 update work, I really liked what I heard, and I was excited to know that we were going to succeed in addressing this problem area in our dev work. But I should not have told you about it.
It was too early.
Look, I’m an optimist. When we green-lit the updated sound package for 777, we had a timeline built in that wound up getting decimated by delays in the 777 development pushing it into competition with 737 development needs. That was bad planning on my part, and we simply reached a point where I had no choice but to strip resources from 777 in order to get 737 finished. The 737 package has a world-class sound environment and it was the right decision to make because there was just no way we could release the 737 with it’s old, outdated sounds.
But that has given many the impression that we simply walked away from the 777 sound update.
We haven’t, but that perception is entirely valid.
My natural tendency to be candid with you would normally have me inserting some timeline expectations and other assurances right here in this part of the post. I am going to take the feedback and refrain, however- as that tendency is what created the disappointment in the first place.
So, yes, I am aware that we failed to meet your expectations. Yes, I hear your feedback that this is a bad habit pattern for PMDG. Yes, we are working to change that facet of how we communicate.
And lastly, yes- the sounds are still in the update plan for 777. We will tell you more about them when the time is appropriate.
Thank you for your patience. Sometimes we make mistakes.
No - it was definately not a mistake telling us about the new sounds at all - maybe it would just have been more appropriate to advise about the delay earlier when it became clear.
I applaud you for taking responsibilty - that deserves respect. Thank you and looking forward to those sounds being released some other future date.
Please link BATC in the ACARS/Datalink Coms menu…
Why hasn’t pmdg fixed the 777 issue where the wing surface textures aren’t loaded properly? It’s been over 6 months since I first saw it. It just kills the entire vibe of the plane. This is the for marketplace version.
lets hope it won’t be sound “groundup build” behind paywall… 
I really count on boris update coming to xboc… pmdg is less and less predictable.
Yes exactly this! I mentioned it further up as well!
…and don’t imply that in reality they’re not working on the feature even though they claim they are, otherwise you get banned from their forums 
To be honest I’ve spent just a couple of bucks on Boris 777 soundpack and I’m not waiting for this sound upgrade from PMDG anymore. It’s awesome.
Besides the sounds, are they going to fix texture and core bugs, especially the main one - the stuttering every five seconds? It helps if you select Weight and Balance on both the left and right tablets.
This „banning in their forums“ is the easiest and most convenient, effective method of avoidance. Actions are usually speak more than words.
However some posts of „worship and praise“ in the official forum are just over the top cringeworthy.
I appreciate the 737/777 developments more once they are fixed and come with BATC integration.
I am not sure if it is me - but I had problems with the AFCS capturing RNP approaches in both 777 and 737 - although the modes are pre-armed on the PFD, they do not activate and capture at all.
Also not sure if it is normal and if I remember correctly it worked in the 2020 model: the Autobrake switch solenoid no longer disarms the knob after takeoff or landing in the 737. In the 777 it works.
If Boris would have send his sounds to Marketplace, I would also be inclined buy them now…
So I’m lucky that I’ve never experienced this issue even though I use only the left EFB…
Isn’t that just because of the 737 old design? I’ve always thought that’s normal because (I’m not 100% sure now) in iFly Max the autobrake switch doesn’t jump back to off position when airborne as well…
Yes that could well be the case that that is the correct way it behaves and you have to manually select „OFF“.
I’ve never had a problem with RNP in 737. But regarding 777… I fly RNP’s very rarely in it (yeah, because that bird feels at home at large airports mostly equipped with ILS) and for that I keep a screenshot of what was posted by one IRL 777 pilot here on this forum (as an IRL pilot you probably know it) - it’s flown a different way than in the 737 and I always have to refresh my memory before dealing with the non-precision approach in this airplane
