Are you using Developer Mode or made changes in it?
NO
Brief description of the issue:
CTD anytime Ctrl-TAB into VR. Never happened before the beta. Happens in normal and safe mode in DX11 or 12.
Provide Screenshot(s)/video(s) of the issue encountered:
Just CTD
Detailed steps to reproduce the issue encountered:
Ctrl-Tab
PC specs and/or peripheral set up if relevant:
G2 Headset, 64 GB Ram, 3090 RTX, 12th Gen Intel(R) Core™ i9-12900KF 3.20 GHz
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
Fault bucket 1731406398137839368, type 5
Are you using DX12?
Yes and No (happens w/ both)
Are you using DLSS?
Yes
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
I have the same. I was running the VR toolbox previously, but I uninstalled it when I read it is not compatible with SU 10 beta.
Still getting CTD as soon as I CTRL + Tab
What sequence are you following for Starting up the headset and sim?when does it CTD: when you switch to VR whilst still on the menu? on the world map and ready to hit fly? or once you’ve loaded a flight into the simulated environment? Or of course all of the above?
You name it. In the main menu. In the world map. In game.
Even prior to SU10 beta, I’ve pretty much always had to start WMR before I start MSFS otherwise I get a CTD. Have you tried starting WMR, or whatever is your OpenXR client, first?
Yeah thx for suggesting. I never had to start it before but now it crashes whether I do or not.
1 Like
Do you have the same issue if you follow the OP’s steps to reproduce it?
yes
Provide extra information to complete the original description of the issue:
11900K RTX 3090 64G ram Vive Pro 2 I had no issues before updating to SU10
If relevant, provide additional screenshots/video:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
Fault bucket 1641575062440367561, type 5
Same here. But only using Dirx12 .
Last beta
win 10 pro
Just a quick reminder for those who might be using OpenXR Toolkit (and if not - then ignore my message).
Hey all,
Just putting it out there so there is no surprise:
OpenXR Toolkit is currently NOT expected to work with SU10 while in beta.
SU10 comes with some engine changes that are expected to break certain features of OpenXR Toolkit, like DX12, Foveated Rendering, and perhaps more.
To be clear, this is not Asobo’s fault nor their responsibility: this situation is inherent to hooking into the game engine from outside the game. It could have very well happened at SU8 or SU9, we just got lucky b…
Same thing.
I uninstalled OpenXR toolkit, tried different drivers, reverted Bios to default, and reinstalled OpenXrR and MR portal.
i9 9900, 3080, 32gb, win11, Reverb G2
Reliability report:
roblem Event Name:
MoAppCrash
Package Full Name:
Microsoft.FlightSimulator_1.27.11.0_x64__8wekyb3d8bbwe
Application Name:
praid:App
Application Version:
1.27.11.0
Application Timestamp:
00000000
Fault Module Name:
nvwgf2umx_cfg.dll
Fault Module Version:
31.0.15.1659
Fault Module Timestamp:
62b4eac6
Exception Code:
c0000005
Exception Offset:
0000000000203101
OS Version:
10.0.22621.2.0.0.768.101
Locale ID:
1050
Additional Information 1:
0807
Additional Information 2:
080784da1826d1e72b555a3cd9009a00
Additional Information 3:
2992
Additional Information 4:
2992c92c360adc20d6590c183c36d0d3
Description
Problem signature
Extra information about the problem
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template: