In SU3 Release 1.5.27.0, the PMDG 777 overhead panel becomes non-functional in VR mode. The panel is visible, but no switches, knobs, or click spots respond.
In 2D mode, the overhead works perfectly.
This issue started only after updating to 1.5.25.0 and may be related to the re-activation of the new LoD Curve in VR.
NOTE: I submitted a ticket to PMDG. Unfortunately, they say this issue is an MSFS 2024 issue because it affects other third party planes as well. At this time, they plan to wait for Asobo to fix this issue.
FREQUENCY OF ISSUE
Every time when flying in VR (100% reproducible).
REPRODUCTION STEPS
-
Launch MSFS SU3 Release 1.5.27.0 in VR mode.
-
Load a flight with the PMDG 777.
-
Attempt to interact with the overhead panel (switches/knobs).
-
Observe that no interactions work in VR and switch look non functional
-
Switch to 2D mode—overhead functions normally.
YOUR SETTINGS
-
VR Headset and Peripherals: Meta Quest 3 via Virtual Desktop, Honeycomb Bravo Throttle Quadrant
-
Developer Mode: Off (no changes made).
-
GPU: NVIDIA RTX 5090.
-
CPU: AMD 9950X3D
-
Mods/Add-ons: Community folder cleared for testing—issue persists.
MEDIA
image453Ă—329 16.1 KB
2 Likes
Exactly the same problems as stated, with NVIDIA 4090 and intel(R) Core™ i9-14900KF (3.20 GHz) Obviously an SU3 update issue.
1 Like
Since Sim Update 3, I have a similar problem while using the PMDG 777F and 777-200er with the Quest 3 VR headset.
As soon as I switch into VR mode, I can no longer interact with the switches and knobs in the cockpit, and the writing on the switches disappears. As soon as I switch out of VR everything works as normal.
This problem does NOT occur when using the 2020 version of the PMDG 737 (having deleted the old WASM file) in 2024 with the Sim Update 3, nor does it occur with the Asobo 737 Max or the TBM 930 (the only other aircraft I tried).
Again, the 777’s work completely fine until I enter VR mode. I first noticed this problem on 8/21/25, the first time that I tried to fly them in two days.
Going back to DCS. This pOS game breaks after every update. My 777 not working.
Same problem..Its an absolute joke that we have to deal with these issues.
Thanks for posting.. I have also voted on the LOD issue
Hi,
I am having the same issue as well with inibuilds A350 in VR, Q3, with SU3, and yes, also with PMDG 777F and ER…
None of that issue with default aircraft like A330.
And the VRAM is still kind of high, why is MSFS not utilizing all of the dedicated VRAM? Its always 2gb less for the game to use?
This is very frustrating to say the least.
It seems every SU, Asobo breaks some of the 3rd party aircraft.
This time is it in VR.
Sigh…..I am really disappointed…
This solved for me the issue in VR for 777 and A350 too. Probably it influences global performance by a bit but i didn’t notice it. I think this is just a quick fix, the problem still need to be addressed by Asobo
2 Likes
I lost 11 fps with this setting (101 <> 90). Pretty acceptable for a workaround.
Mathijs Kok
PMDG
This also worked for me, and I completely agree…this needs to be addressed by Asobo!
Not true, they screwed up their own aircraft too (H125, Cabri), H125 Airspeed Indicator Shows 0 in Default VR View
1 Like
Just had a flight in the Fenix A320 which worked perfectly in VR in 2024.
Is it really an Asobo problem or are some 3rd party devs not getting the new LOD structure correct?
Whether its a Asobo or a dev problem, I wish someone would fix this.
Not being able to fly the PMDG 777 is getting old.
1 Like
What if you read the post right above yours?
I’d encourage you to check the Fenix again. The issue is more subtle than in some aircraft but still there. Take a look at the radio panel and move your head forward and backward any you’ll see the dials disappear.
That post deals with an airspeed issue.
My issue is a total failure of the 777.
I am unable to click on any buttons in the overhead.
Very different.
Seeing the dials disappear when I move my head…..lol
On the 777, I can’t click on any buttons in the overhead. A total failure.
I am just glad I can use the Fenix A320 for my flying fix. My last flight in VR was quite enjoyable 
I think you”re missing the point. This is an Asobo issue and affects MANY third party aircraft as well as the default ones. Great that your Fenix experience is ok, big congrats to you on that. It doesn’t however change the fact that an issue that appeared only in the last two beta builds has broken or hindered the experience of essentially all VR users.
Check this: https://forum.pmdg.com/forum/microsoft-flight-simulator-2020-2024-products-discussion/pmdg-777/model-animations-documentation-aa/368134-workaround-for-vr-problems-su3
The issue is, in fact, that the developers who followed the SDK to the letter are being affected. If you did not follow the SDK (like some devs chose to do) you will not be affected. This is not an option for us because only following the SDK to the letter gets you to a aircraft that has great performance. (And xbox compatibility etc)
Mathijs Kok
PMDG
Presumably if you have followed the SDK to the letter, this is something that Asobo has to fix rather than something that PMDG has to spend weeks of effort fixing?