November 21, 20223 yr Reverb G2 / 3060 Ti Driver 31.0.15.2698 (latest Game Ready 526.98) / Win 10 21H2 19044.2251 / Steam I had been using the G2 a lot prior to the latest MSFS update but today is first try with VR since SU 10. VR works fine in Assetto Corsa. VR works fine in MSFS as long as I run in VR desktop mode (I start the sim from the VR desktop) - I can do anything I want with no problems. When I start Mixed Reality then MSFS from the 2D desktop and then use the MSFS Options / VR / switch to VR I get an immediate CTD. Empty Community folder and also happens in SAFE mode. I've used both MS Mixed Reality and Steam VR with same result. Only odd thing is that when I start Steam VR and then start MSFS from the Steam Library - I get a Steam message that MSFS does not support VR. What have I overlooked / forgotten about starting VR? Two months ago it was so easy and worked perfectly! AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
November 22, 20223 yr Hi, any chance you are running the OpenXR Toolkit? If so, is the in-game msfs2020 render resolution set to 100? I think used to crash if set otherwise though this may no longer be the case. Otherwise, it may be worth uninstalling and reinstalling OpenXR and Open XR tools (different to Open XR Toolkit incase you are unaware) and you could try checking for updates from the MS Store library Edited November 22, 20223 yr by dogmanbird
November 23, 20223 yr Author If I set MSFS to use DX11 - VR works perfectly and I get a surprisingly good FPS using DLSS/Quality/Ultra If I tell MSFS to use DX12 - CTD as soon as I hit CTRL+Tab or use the VR option to turn on VR AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
November 23, 20223 yr Easy, just keep it on DX11 and don't bother with DX12, DX12 isn't ready, too many (small) issues. Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base & hegykc MFG Crosswind modded pedals, TrackIR4, Rift-S for VR
November 23, 20223 yr As @dogmanbirdsays above, earlier versions of OXRTK cause these CTDs switching to VR in DX12. Either turn OXRTK off or update it to the latest version. Edited November 23, 20223 yr by Reset XPDR 9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit MSFS @ 4K Ultra DLSS Performance FG 80 FPS | VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11 Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11
December 14, 20232 yr OXRTK = OpenXR Toolkit It is different software to OpenXR Tools (required for WMR headsets like Reverb G2. This one is part of windows apps library) I've been unable to use OXRTK since the latest MSFS update and the game now gives an error when entering VR unless I use OXRTK safe mode or disable it. I haven't had much time to figure out why. Edited December 14, 20232 yr by dogmanbird
December 15, 20232 yr OK, thanks. I figured out the problem. I simply undid the DLSS version upgrade that I performed a week or two ago and all is well again. That mod was hailed as the secret to all our problems. I should have known better. LouP
Archived
This topic is now archived and is closed to further replies.