Thanks for providing these insights. It’s strange because after a restart I was actually able to open the start menu without crash. However, after one deactivation/reactivation of VR-mode, I was back to regular crashes. Will try a few things. 2 questions that would be really helpful in pinpointing the bug: what Nvidia drivers are you on and did you turn of the preallocation key in regedit (the setting that turns off the rendering of seperate monitors for mixed reality)?
Edit: since there were task-switching related issues with it: Do you use windowed mode or fullscreen MSFS? Thanks for your help. Won’t bother you anymore after this. Just trying to pinpoint the error so I can update the bug I have filed.
It’s fine I don’t really feel bother at all. Having other stuff in the cockpit is really nice, so I am happy helping others on that.
About your questions, I use the driver 457.30, and I tried both preallocation settings. I didn’t set that registry before when I updated OpenXR and saw the issue resolved. Then yesterday I tried that registry when testing some further optimizations. Doesn’t seem to be related to the VR crash. And I usually use fullscreen.
1 Like
Thanks for your help. I tried all of your settings above and tested. I seem to be able to prevent the crash in cockpit by 1. setting motion reprojection to automatic and 2. going into the menu (esc) before the initial WMR menu start (not required for me after initial run of WMR start).
It definitely seems something resource related. Generally the lower the settings (less resources used) the less likely it is going to crash. This is why I think pressing esc before opening start menu helps when I have settings pushed up.
Will do some more trials. I never had any issues with it in Beta and was constantly using it which is why I have tried to get this to work reliably for weeks. Thankfully your success motivated me to revisit this. Perhaps others will be able to test this with their settings and rigs @CalmEspresso
Oh there is one thing I always do, maybe it is related. If I want to use VR, I always switch to VR while I am still in the menu and start the flight from VR to avoid the loading of all the high quality resources of 2D.
I think you’re right that the crashing has to do with resources. Before the UK update, I was able to open and close the WMR menu almost every time from the flight sim main menu. However, since the UK update has made the main menu laggy (especially after zooming in on the UK region on the World Map), I now crash out of VR most of the time when trying to open the WMR menu from the flight sim main menu. The workaround now is to either open VR and the WMR menu prior to setting up your 2D flight, or by opening the WMR menu inside the Cliff house, rather than inside flight sim.
I have a powerful rig so that’s probably not the limitation (10700k, 3080, 64gb ram)
If you want it to be truly smooth, get driver 457.30… The new one is trash in comparison. I’m not kidding!
I don’t think this applies to all. I have been running the latest Nvidia driver, since it came out, without any issues - things are silky smooth for me.
Interesting, what are your specs? For me it makes a huge difference.
Specs:
i7 8700k@4.9ghz
Z370 motherboard
32gb RAM @ 3200mhz
TUF RTX 3080
Reverb G2 (running through WMR, no steamVR)
Newest Windows Build, MS Store Version of FS
I9 9900 not K
64gb RAM @ 32mhz
Rtx 3090
Reverb G1
Newest Windows, MS store FS
You seem to be getting results unlike others with the same setup (including me). At higher settings, even with a 3090, the game is very unstable performance-wise without reprojection or upsampling.
Hi Gathan,
Are you using motion reprojection?
Thank you!
No I don’t, things seem to run better without it on.
1 Like
SteamVR or WMR?
I have just received my G2. Same 3090 suprim card and CPU as you, but not getting smooth experience. Do you have anything set in OpenXR dev tools? Trying to work out what I’m doing wrong. Thanks.
Are you using motion smoothing? If not be sure to lock your framerate to 30fps in the headset to avoid stutters (you can do this in the nvidia control panel per game).
If you have 30fps and 90hz then each frame will be displayed for 3 refreshes, while not ideal it will at least appear consistent. If you have eg 35fps then some frames will display for 3 refreshes, some will display for 2 refreshes and it leads to a much more juddery experience.
If you have motion smoothing enabled then it will lock itself to 30fps (or 45fps, but that’s much harder to achieve in MSFS) as long as you have sufficient headroom, but it does involve some overhead and requires headroom to properly function too so you may need to turn down the resolution and/or some in game settings to get it working properly.
For me personally in MSFS I prefer to turn off motion smoothing (disabled in the OXR app) and lock to 30fps as it frees up some precious resources and the artefacting from 30fps reprojection is too extreme for me.
Make sure you are using either 457.30 or 461.92 as those drivers have the best results for me on my 3090, anything else is notably more juddery on my system.
It’s also worth noting that the latest update has some performance issues, while mine runs great 90% of the time (well, not great - I don’t consider 30fps in VR great lol, but great by MSFS standards) I occasionally run into some serious stutters and performance problems since sim update III.
That’s really helpful thanks. Had not changed nvidia settings – will try that this weekend. Have a good one.
In my opinion, it is worth trying both these drivers, not just one or the other, as you could have wildly different results between the two, and hard to say which will be for the better or worse given the inconsistent results reported by many.
Just tried 461.92 and reprojection is totally borked compared with 457.30 on my g2 and 3090, horrible.
But it feels better with repro off…
So for me 457.30 is better by far with repro on.
461.92 is better with repro off.
■■■■.
Edit 60hz repro on works better for me, less wobbliness going on.
Can you elaborate a bit more on the improvement with repro off? I now can get around 40fps with my 2070S on 457.30, so I stopped using motion reprojection 
.
It feels less blurry at low altitudes, I think it’s called judder. This latest driver makes it more bearable for me, I don’t bother checking fps anymore I just go by what I see.
BTW I’m trying repro at 60hz now with the new driver and that feels better than 457.30. running oxr res disabled game res 100, less wobbliness.
The plot thickens…
1 Like