After SU4 - MSFS 2024 ends / CTDs whenever SteamVR is ended, regardless of VR injection or 2D
I’m reporting a regression in VR / OpenXR handling introduced with Sim Update 4.
For long-haul flights I have used the same workflow since MSFS 2020 (since ~2021):
-
Start MSFS 2024 and load the plane / flight
-
Start VR mode via Shortcut, SteamVR launches itself and begin preperation / flight in VR
-
On reaching cruise switching back to 2D. Due to stability issues best way for me was to simply stop SteamVR
-
Later re-enter VR for descent/approach through MSFS2024 as before via shortcut.
This workflow worked reliably throughout SU3, and in general already in the MSFS days since 2021.
Behavior before SU4 (SU3 and earlier):
-
After turning off SteamVR, MSFS2024 dropped out of VR projection.
-
MSFS 2024 continued running in 2D
-
SteamVR could later be restarted and VR re-entered
-
Not perfect, but functional and stable
Behavior since SU4:
-
As soon as SteamVR stops, crashes, or is restarted,
MSFS 2024 immediately terminates -
This happens even if VR was already disabled and the sim is in full 2D mode
-
The shutdown appears intentional (controlled exit), not a classic CTD
Critical issue:
SteamVR (Valve Index) can hang during the VR → 2D switch itself
(e.g. compositor freeze or headset tracking stall).
In that case:
-
SteamVR must be restarted
-
Restarting SteamVR always terminates MSFS 2024
-
The current flight cannot be recovered
This means that once VR has been used, any SteamVR runtime failure ends the flight, even if the user has already returned to 2D.
FREQUENCY OF ISSUE
Every single time SteamVR is restarted or stopped. Being in 2D or VR-mode does not change this behaviour.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
-
Start MSFS 2024
-
Load a flight
-
Enter VR (Valve Index via SteamVR / OpenXR) or MSFS 2024 shortcut
-
Exit VR back to 2D (Ctrl+Tab or in-sim menu)
-
Stop or restart SteamVR
-
MSFS 2024 exits immediately
-
Same happens when SteamVR is ended before dropping back to 2D (omitting step 4)
Expected behavior:
-
After VR is disabled, MSFS should:
-
fully release the OpenXR session, or
-
gracefully ignore later XR runtime termination
-
-
SteamVR stopping should not force MSFS to close while running in 2D or in VR
-
This was effectively the behavior in SU3 and earlier versions
Actual behavior:
-
OpenXR runtime loss is treated as fatal even when VR is no longer active
-
MSFS exits as soon as SteamVR stops or restarts
Hardware / Runtime:
-
Headset: Valve Index
-
Runtime: SteamVR (OpenXR)
-
GPU: NVIDIA GTX4080
-
OS: Windows 11
(Note: Issue is architecture-related and reproducible regardless of GPU load)
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What VR peripherals are you using: - Valve Index
[PC Only] Are you using Developer Mode or have you made any changes to it? - No
[PC Only] What GPU (Graphics Card) do you use? - GTX 4080
[PC Only] What other relevant PC specs can you share? - Ryzen 7950X, 64GB RAM