Extreme LAG, Blackouts in VR

Hello all,
I upgraded to RTX 4080, 13900K Processor.
Using HP Reverb G2

There is extreme lag suddenly and it blackouts ( freezes on and off in VR) This particularly happens in photogrammetry areas and when nearing those airports.
Settings are nominal, no issue in any other heavy end VR games. It’s an issue with MSFS VR. I am not sure how someone can think of developing new things when they cannot fix the present?

I tried every possible thing.
Please assist.

I have the same issue after update to version 1.33.8.0.
When i am in proximity of an airport my Hp reverb g2 goes in sleep mode (my settings in WMR are never sleep) and the simulator switch to 2d mode automatically. After that i try to wake up the headset but this does not respond…

Yesterday before update all work well and i never had this issue

SOLUTION FOR NOW:
Logging out of main ingame screen and logging back in fixed it!
It’s MS server related probably

I have the same problems with my HP Reverb G2. Every time I take off and always right after landing, the right display goes dark first, then both. The whole thing lasts for about 5-6 seconds, sometimes the glasses remains completely dark. Everything is still displayed on the monitor.
Very annoying and hard to fly. Please absolutely fix!

I’ve got a stable solution for this:
The HP Reverb G2 has problems with too high volumes on the integrated headphones. They then consume too much voltage and the displays are underpowered.
HP has released a firmware patch for this.
I have already implemented this FW update, but an additionally used buttkicker seems to influence the volume level as well, so I have these effects.
I was able to track stably though: If I reduce my volume on the headset from 100% to about 70%, the blackout problems are gone. Increasing it to 100% brings them back.

I’m still using an Oculus Rift S with an NVIDIA GeForce RTX 2070, which isn’t nearly as powerful as some of yours, and after the avionics update the sim has become unflyable. My FPS is currently around 10 with the PMDG 737 (and not much better with the stock Cessna 172). Before the update I was getting upper 20s into the 40s depending on which airport I was at. Not great compared with other flight sims out there but definitely flyable.

Nothing had changed on my system before updating and I always clear out my community folder so that isn’t the problem. I spent some time after the update going through everything, and even lowering them, to see if I could boost the FPS without any luck.

Apparently this new problem that’s been introduced isn’t affecting just HP products but Oculus and the rest as well. It seems like every update that Asobo has made, VR performance gets worse rather than better. I wish the developers would start taking VR seriously to improve it rather than giving us more eye candy (like 4th of July fireworks). These little “extras” are amusing but I think their time would be better spent ironing out the numerous performance issues they currently have.

There is no way I’m considering purchasing their 2024 version unless they can prove that they’re building a serious flight sim for VR users and not just another video game. I’m sure you’d all agree that once you fly in VR, going back to a flat screen experience is unthinkable. Until Asobo addresses this issue I’ll be concentrating on flight sims that actually work well in VR like Falcon BMS, DCS, or X-Plane 12 (that’s making an honest attempt to boost VR performance in their early version of this release unlike what I’m seeing in MSFS 2020).

1 Like

I wanted to follow up on my earlier post.
I found that Asobo had defaulted to DX12 (beta) instead of DX11 where I had it set before the update. I changed it back to DX11 and my FPS went back up into the 30s and 40s on the ground (which was great). The FMC buttons in the PMDG 737 were still difficult to read so I decided to try and improve that with OpenXR toolkit. I found by changing settings in OpenXR toolkit my FPS would tank again and any subsequent changes wouldn’t restore it. I think Asobo might have an integration problem currently with OpenXR which is creating more problems for everybody.