Crashing in vr after su5?

I am experiencing CTD in VR after update SU5 . This is troubling as many others have reported . Is there a work around or a fix ?? Never had this happen before now . Whats up?

What are your specs, equipment and settings. In what scenario does it crash?
It must be something specific, because I can use VR on Su 5 without crashing. (Latest TestFlight around Melbourne PG area.

My MSFS VR settings are set to high, TAA and DLSS (quality) tested, on following rig: 9800x3d, 96GB 6000MT/s, NVIDIA 5090 factory overclocked. SW: Windows 11 latest, msfs2024 su 5.1 beta, Steam version
VR: headset: pico 4 ultra, virtual desktop, Steam VR. Streaming via wifi7 @ 4.2 to 4.8 gigabit/s

It’s NOT my setup it is happening now after SU5. I tried the Beta 5.1 same issiue. There too many people experiencing the same problem.
Running on DLSS preset “M” with good performance,however now CTD all the time. ( same config. before SU5 no crashes)

Latest driver Nvidia : build 596.49
|Processor|13th Gen Intel(R) Core™ i9-13900K (3.00 GHz)|
|Installed RAM|64.0 GB (63.8 GB usable)|
GPU= RTX 4090
VR: Pimax crystal

And why do you not join one of their threads, if it is a known issue?

BTW, I am also having no problems. It’s the opposite: VR has become much better in SU5, much smoother.

Good for you Frank, However do you think I’m making this up??
Since the update in VR my Sim crashes. I don’t need your criticism I am only looking for recommendations and help…

I also think VR is much better in SU5, similar specifications to you. But it appears that updates can mess about with settings, not always the same for everyone so it may be worth turning everything down to low, emptying your Community folder then trying again with just a basic setup. You can then add things back, one at a time, to see if there is anything obvious. VRFlightsimGuy did an excellent video on SU5 settings which I used and my VR experience is the best it’s ever been.

One last thought, maybe one of your addons, and I assume you’ll have a few, may well be reacting badly to SU5. Reintroduce them one at a time to maybe find a culprit.

I had a very similar issue after changing VR/display settings in MSFS VR. Suddenly I started getting CTDs, huge latency spikes in Virtual Desktop (400ms+), input freezes, low GPU usage and even performance problems in other games.

What fixed it for me was clearing the DirectX Shader Cache.

Steps:

  1. Open Windows Start Menu

  2. Type: Disk Cleanup

  3. Select drive C:

  4. Check only: “DirectX Shader Cache”

  5. Click OK and delete files

  6. Restart the PC

After reboot, MSFS and even other games returned to normal.

What probably happens is that after crashes, VR runtime changes, DLSS/OpenXR/display changes etc., the shader cache can become corrupted. DirectX Shader Cache stores precompiled GPU shaders to improve performance and reduce stutter, but if it gets corrupted, it can cause low GPU usage, stuttering, crashes and strange FPS behavior.

Maybe this helps someone else too.

Shader cache doesn’t do anything for me . Turning off the photogrammetry made a difference . No crashes yet, the sim looks like FSX, that can’t be right. It must be a memory allocation issue in the sim for some people . This must have changed in recent never had this problem??

BTW I use “AddonLinker” which allows me to run an empty community folder in a vanilla state or use only what I am flying. This makes it easy to identify any 3rd party addons that don’t get along with the sim.

But it does not disable marketplace content and external tools connected via SimConnect. In particular SimConnect can be critical.

No, I’m just wondering if there are so many people have reported it, why do you not join them?

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report.

Using the template and/or providing all the requested information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

I can now confirm the Sim crashes CTD on final approach every time .This is only since SU5 update . This is troubling…

You should analyse the Windows logs then, in order to identify the root cause.

It seems to me - actually, I’m pretty convinced - that there are no fortune tellers on this forum and Frank certainly isn’t one either. So maybe at least say where exactly you’re getting this CTD? On approach to which airport? Which aircraft?

Be more specific if you expect people to help you.

I can confirm that after SU5 the PMDG mostly 737-7 737-8 crashes in VR MSFSS2024. (B777-2 -300 do not) Other default aircraft do as well , not all. Fenix does not crash the sim. I have run the sim in vanilla state and also use “Addon Linker” to only allow what I am using in the community folder to better Isolate any 3rd party discrepancy. The 737-7 737-800 crash consistently, usually on final approach. Most airports cause this. This never happened before and never in MSFS2020.

I can confirm, that this is not the case. No plane crashes the sim for me.

There must be an individual issue on your side. So I agree with @TenPatrol : You have to provide more diagnostic data, or we can’t help you.

BTW, you are still the only one reporting this problem, although you claimed, there are many other users suffering from this problem.

We need to start eliminating things step by step.

@Starseed55
Do you get CTDs only in VR, or also in 2D? Try disconnecting the headset and check.

Important: to test this properly, you need to uninstall absolutely everything related to VR so that third-party tools like OpenXR Toolkit or other software from different vendors don’t interfere with MSFS.

So again: remove everything connected to VR, unplug the headset from the PC, and then run MSFS 2024 completely clean - with no add-ons at all. Then test it in that state.

Also rename the exe.xml file to exe_copy.xml - you’ll find it in:
c:\Users\Username\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache

And delete the content.xml file:
c:\Users\Username\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Your_Gamertag

There is no need to uninstall OpenXR Toolkit as it can be disabled by a simple click in the menu and per application also if required. Saying that is very unlikely that is the root of the problem. I would however DDU in safe mode anything Nvidia and then re-install the drivers. That should fix it.

In the way I described, we’re eliminating potential VR-related issues step by step. Simply disabling something is not always reliable - sometimes it can still hook into the system or leave background components active.

Only a full uninstall gives real certainty that nothing related to VR tools is interfering with MSFS.

And as for the Nvidia driver - that’s a separate matter and we’ll get to that later.

I have been working with Pimax tech’s trying to resolve if itis their product, however the Sim crashes in 2D and with VR off usually nearing the airport and I believe when the Sim renders the scenery. I have tried clean installs of multiple drivers, I always use DDU in safe mode for clean installs. Again this is new to SU5 never had this issue before now. This is why they have a stability fix SU5.1 in Beta now.
And there are plenty of posts with others having the same problem you should do a quick check.

TenPatrol;
I have changed the recommended settings as shown .

I know you said it also crashes in 2D.

I have a Pimax Crystal light, and fly for an hour or two almost everyday, and I have had no crashes at all.