Running WMR makes FS2024 super slow and unusable even when not flying in VR

[EarthFlight42]

I have …

• A vanilla FS2024 with SU 3, installed via Steam.
• a mobile GeForce 3070 in a gaming notebook
• a HP Reverb G2, set to 60fps in WMR settings
  (yes, it still works on my Windows 11, haven’t received 24H2 update yet)
• SteamVR 2.12.14
  • Render resolution is “Automatic” (aka 3156x3092) in SteamVR
  • OpenXR runtime is “Windows Mixed Reality” (also tried switching to “SteamVR”, no difference)
• up-to-date NVIDIA studio driver 580.97

The HP Reverb G2 work well with other VR games/software.

When running the simulator with VR completely off and no headset attached I get an acceptable 28fps, e.g. in Yosemite area. Have adapted the graphics settings (trees, fauna etc.) to my preferences.

The problem is: As soon as the headset is plugged in and WMR is running, the framerate drops to like 4fps … in 2D mode. Even worse, the simulator becomes almost unresponsive, that is, it takes multiple attempts to press buttons in the menu, takes several seconds to navigate through settings etc.
I’m not talking about flying in VR, the VR mode in FS2024 is still off. (Flying in VR also results in mediocre frame rates of like 4 FPS unless I lower the settings like rendering resolution. But this is not the main topic here.)

The task manager reveals that now 3/4 of the GPU time go to the desktop window manager:

Also, I noted that quite often Steam VR freezes completely and has to be re-started. Or the simulator does a CTD when switching to VR. I cannot remember having these particular issues when I first tested VR months ago (I think with SU1).

My questions are:

• Is it normal that a running WMR impacts the simulator that heavily just by being “on”?
• Can I do anything about this? (I don’t want to spend days or weeks tweaking some settings for a gain of 1FPS, but if there is one or two settings or recommendations that can improve FS2024 behaviour with WMR significantly then I am interested.)
• Does anyone have experience how the new OSASIS driver performs in relation to default WMR? Does it have the same issues? Or is this issue completely unrelated to the driver?

(I’ve already looked through the forums a bit but I am a bit overwhelmed by the number of different tips and tweaks and what not and I didn’t see my particular issue mentioned.)

Note sure this here is related to my issue:

Reverb G2, WMR, Steam VR and computer freezes in VR

Alienware I7 9700K, 32MB Ram, RTX 2080 Super, 2TB SSD and all this thing does is freeze once I connect to VR. Using WMR interconnected with Steam VR. First flight was magic, everything after that has been a disaster. Open XR installed with Dev Tools. Watched the YouTube vid with the guy in the Spitfire, almost all settings around medium in VR and PC. Flying in the PC is great, no problems. Flying in VR just about makes me want to throw my G2 against a wall. If anyone has an idea and can h…

[EarthFlight42]

OK, my sincere apologies. The fault was on my side.
The said notebook was in power saving mode since my last train ride and had not noticed this.

So I re-checked now and the described issue is neglegible now. I have 45fps with WMR off and 35fps with WMR on. So I simply don’t notice the difference if I have the fame rate capped to 30 fps for Vsync as I usually do.
Also, in the notebooks “normal” mode the desktop window manager only takes up like 7% GPU resources according to the Windows task manager when WMR is on, leaving enough for FS2024.

Longs story short: I declare the case closed.