Hello.
Firstly, a big thanks to all those members here who have spent much time experimenting and sharing their findings about settings for FS2020 and various devices since FS2020 was released.
Having used the Oculus Quest 2 with varying to reasonable success and quality, seemingly related to whatever update FS2020 and Nvidia are on, I acquired the Reverb G2.
However, when I activate VR mode with the G2 either FS2020 crashes to desktop and the cliff house in the G2 dissolves to black and back again or the VR view appears on the 2D display of FS2020 and the G2 cliff house dissolves to black. I do have sound in the G2 at this point and before. Toggling out of VR causes a CTD and the cliff house reappears.
My start up procedure is to reboot the PC, load WMR Portal (with the correct runtime in the registry) and see the cliff house in the G2, load the OpenXR Dev Tool, minimise both those apps and load FS2020. I then set a flight to start, say on the runway, and then toggle to VR using an assigned key on my Thrustmaster Airbus Flight Stick.
Am I missing a fundamental setting or procedure step or is it because Iâm using a laptop and an RTX2060?
I have played with other settings such as Game Mode and HAGS on or off, various Nvidia settings, low settings in FS2020 and changed settings on the WMR Portal and Dev Tool apps. I also tried different USB ports and a powered USB hub. The latter seems to make the CTDs worse and I canât get the 2D VR view often.
Any advice welcome or should I put the G2 away and wait for a higher spec system or FS update? I have tried to look for answers.
I can get VR to work in the G2 if I go via Steam and its runtime but am I right in thinking this should not be necessary? I have the store version of FS2020. The image on the G2 via Steam at present is nowhere as good as my Quest 2. I realise that the RTX 2060 will not be using the G2 to its full resolution though but expected better and to at least see an image using the non Steam route.
My setup is:
Store version of FS2020 (Deluxe)
Gigabyte Aorus 7KB gaming laptop
Intel i7-10750H (10th Gen)
16GB DDR4 2666 MHz
Nvidia GeForce RTX 2060
Nvidia driver 477.11 but have tried others.
Windows 10 Home (64bit)
Windows and Sim running on 512GB PCIeŽ NVMe⢠M.2 SSD
1 TB HDD present.
Apart from not needing to load the OpenXR Dev tool, which you only need to do if you are changing an OpenXR setting when the WMR portal is not running, your FS2020 VR start-up procedure echoes mine. I hit CTRL Tab just after I hit the Fly button and mine switches to VR while on the flight load up screen.
Other than these points, I canât really see why yours isnât working with WMR. At least you can get it working with SteamVR, so Iâd go with that and just make sure your render resolution settings for SteamVR are set high enough, which should look better than a Quest 2.
As above, my startup is much the same. I actually find WMR to be pretty robust and can start before or after MSFS and it still works just fine. It is interesting that you said using a powered hub causes more CTD ⌠I use a powered hub to run the G2 and it helps. Usually I found USB problems manifest as the â13-10 Error - Headset Failed to Startâ not a CTD - not sure what to make of that.
I use the default OXR settings so I donât use the OXR Dev Tools.
A couple of things to check:
I recently needed to do a clean reinstall of Windows and after that I did have some problems getting the headset to start in MSFS ⌠tracked this down to the default mode for input switching. Make sure that this setting in the WMR options is set to âmanually switchâ :
The other thing to try - I did find that after switching between 2D and VR would cause a period of extremely bad performance and sometimes CTD. It seems that this can be improved by setting the 2D graphics options to minimum. See my thread here. Itâs a pain if you plan to mix flying between VR and 2D ⌠but might be worth a try.
For reference - i7 9700, 64Gb RAM, RTX2080Ti (using 477.11)
Thanks ResetXPDR for that info. I have tried with the Dev tool not open thinking it wasnât active then but maybe it was then set with high settings. I will try again. I have tried different settings though.
Hi ClayishCoast19. Thanks. I have played with the input switching settings too and setting all sim resolutions to low. That did at least generally alleviate the CTD on switching to VR and produced the VR 2D view but a blank view in the headset. Power options are set to performance too on the Nvidia driver and the PC. I have also tried the default Nvidia settings and other settings in OXR.
No problem, hope you get it sorted. Let us know when you doâŚ
Your computer should be up to the task (16Gb is perhaps a bit light, but shouldnât be a show stopper). Also the fact that you can get it working through Steam suggests that it isnât a fundamental issue of hardware capability. But as you say - shouldnât need Steam VR to run.
Hi Samplissimo. Yes, with WMR Portal open I can see the cliff house environment in the G2. I have then been switching to VR from a button on my flightstick after loading a flight to the 2D screen from the PC keyboard to start on the runway but did also try from the menu in the VR environment I think and it crashed, although maybe that was trying to load FS2020 from the start. Maybe I didnât try switching from in the headset with all resolution setting options set low though and with the flight already loaded on the 2D screen. I will have another look. Thanks.
The G2 has some design flaws unfortunately. The headset draws too much power.
There are 2 things you can try.
First try to lower the volume of the headset all the way down and see if the screens are coming alive.
You can also buy a USB PCI card and try your luck with that one. Some motherboards USBs have problems.
Thanks SirKrassus. I tried the volume level and EQ fix for that issue and no change. Also the HP update for that issue. Appreciate what you say about the USB PCI card but Iâm using a gaming laptop. I can get it to work via Steam albeit with low res settings and often jerky or slightly jumpy tracking. I will have another go after todayâs MSFS update but feel it could be PC / OXR related?
@DullerCarp06 No, but havenât tried since various FS updates but then is it an FS issue? I donât know. I got HP to swap out the cable for the new revision with switch but it made no difference. I can get a display on the Reverb G2 using Steam VR but not using WMR. Even then the tracking is generally jerky on the lowest settings for everything. Did you have it working in the past though? Which GPU?
I will have another look soon but I am not expecting anything.
What Do you find for your Reverb G2 audio device listed in Windows âSettings/Devicesâ ? If it just identifies as a âUSB 2.0 audio deviceâ it indicates the problem. As others mentiioned it seems to be related to the power demands on the USB Bus. Did you try this: connect your Reverb directly to an USB port on your laptop, an USB 3.1 Gen2 port preferred as they allow for higher currents. Attach your powered USB hub to another port and all your other USB devices to that hub. Reboot and check what audio devices you are finding. The one of the Reverb should start with âWindows Mixed Reality Audio VâŚâ. If it does not, you are still in trouble.
I had the issues you report as well but got them fixed by setting up things as described above. The power demands are high on the USB Bus of my system as I use both Honeycomb controls and Flight Rudder Pedals, all of them drawing power from the bus. However, Iâve no experience with Reverb running on a mobile 3060. My rig is a PC and uses a 3090.
@tallinn19000 I donât know now or whether Iâd have looked. I will look as you say when I get time to try it again, thanks. I did try it in all my USB 3.2 gen 1 and 2 ports, USB A and C type, and with other controllers via a powered hub, plus the G2 via a powered hub as an option. I am aware of the power issue and certainly turned off the power saving function on the USB ports. The other fact is this is a gaming laptop rather than PC with separate GPU. Also an RTX 2060 so I wasnât expecting the highest quality but not this issue. Plus I can get at least a display via Steam VR. I do get the cliff house but it dissolves to black when FS VR switched using WMR. Other VR apps work, although on Titanic the controllers are iffy.
