Still same issue with this second su5 beta from yesterday…
CTD after passing from VR mode to screen mode if i am in full screen mode( in Windows mode no crash) and CTD if i use pop ups screens active .
So going back to the su4 official until next Su5 update because my nerves arena made of Steel….
So do I but it makes no difference.
A couple of seconds of black screen followed by CTD. It obviously tries to go back but fails.
Interesting. I have no problems with my Valve Index.
From reading the comments above, it sounds like the insta-CTD when exiting from VR to 2D is not fixed in SU5 Beta 2 
Does anyone know if the other annoying issue in Beta 1 (VR graphics settings resetting to defaults each time) is fixed in Beta 2?
thanks
Danny
With this beta I leave the sim in windowed and no issues. Still, it needs to be fixed
This issue here is not fixed, but can be worked around by leaving 2D in windowed mode.
The other issue you ask about, with the settings reverting, is solved.
Add me to the list of casualties with this issue. I will try the windowed mode for 2D until this is fixed.
Here’s some related fault data for the last two of them, if that helps:
Faulting application name: FlightSimulator2024.exe, version: 1.7.7.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.7.7.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000003b78a9d
Faulting process id: 0xE514
Faulting application start time: 0x1DCA4849FD9D514
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MSFS2024\FlightSimulator2024.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MSFS2024\FlightSimulator2024.exe
Report Id: 75c196cf-75c3-4199-b2a0-525c17e6d9bc
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 2033731734285408230, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator2024.exe
P2: 1.7.7.0
P3: 00000000
P4: FlightSimulator2024.exe
P5: 1.7.7.0
P6: 00000000
P7: c0000005
P8: 0000000003b78a9d
P9:
P10:
Faulting application name: FlightSimulator2024.exe, version: 1.7.7.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.7.7.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000003b78a9d
Faulting process id: 0xCAAC
Faulting application start time: 0x1DCA483593DAA82
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MSFS2024\FlightSimulator2024.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MSFS2024\FlightSimulator2024.exe
Report Id: 438f4c7b-a0ec-4f63-9daf-edb99a77a900
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 2033731734285408230, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator2024.exe
P2: 1.7.7.0
P3: 00000000
P4: FlightSimulator2024.exe
P5: 1.7.7.0
P6: 00000000
P7: c0000005
P8: 0000000003b78a9d
P9:
P10:
CTD every time when leaving VR
Sony Playstation VR2. Just started on 3/1/26 after I updated to windows 11 version 25H2.
Windows 11 Pro
12th Gen Intel(R) Core™ i9-12900K (3.20 GHz)
128 GB (128 GB usable)
5090 Nvidia FE
Same, pimax crystal light every time.
Reverb G2 - todays new beta 1.7.9… still CTD after leave VR….
The same here. Last today beta and keeps pn CTD after leaving VR to screen mode … not fixed it yet
So ,again ..return to Su4 official by now
Disappointing that it wasn’t fixed this build, but the previous workaround of being in windowed mode in 2D should still work.
Yup same here
Same here ,…….
Still happening here in 1.7.9.0.
My guess is it is something to do with the screen creation as the RTSS display won’t appear until after the game begins to load, whereas up to 1.7.6 you could start it first and it would work immediately.
Of course, i am only going by my system.
I have never seen those CTDs cause I have my 2D always on windowed mode. However, in 1.7.9.0 I have about 2 second freezes when switching from 2D to VR or from VR to 2D. There were no such freezes in 1.7.6.0 or 1.7.7.0…
I did see the freeze in the previous betas. It is like that it is trying to go back to the original screen but can’t for some reason and then crashes.
Obviously with you it is the same but it is eventually able to go back to a windowed screen.