Hello all, I've recently just got back into sim flying a few days ago due to hardware upgrades (and the Oasis driver) and I'm struggling setting up my Reverb G2 in VR. I'm pretty sure I have the hardware to handle at least medium setting, but I think I need to do more adjusting between SteamVR and the in-game graphics settings.

I've searched all over YouTube and Google but can't find anything for using the G2 with the new Oasis driver and SteamVR (without the OpenXR Tool Kit which is what I used in the past). I've found videos with people using the Oasis driver and how great it is, but no mention of settings.

I'm running with motion smoothing off (as the prop effects are terrible) and locked frames at 45 through the NVidia app (so that I'm running at half the 90hz of the G2). I seem to be holding at 45 frames with minimal frame drops, but not getting the clarity I had in the past. I feel like I'm getting the same performance(or worse especially at airports) before the CPU and GPU upgrade.

Any advice would be greatly appreciated. Below are my hardware specs.

Windows 11

GPU: RTX 5080

CPU: AMD Ryzen 7800X3D

RAM: 64G (32G x 2) DDR5 6000hz

 

 

You can still still use the OpenXR toolkit to change some settings. Here is the full answer found on GeminiL

 

You can and should still use the OpenXR Toolkit to change settings in Microsoft Flight Simulator (MSFS).

The OpenXR Toolkit works by being an API layer that sits between the application (MSFS) and the active OpenXR Runtime (which you will set to SteamVR, now utilizing the Oasis driver).

Here’s a breakdown:

• **OpenXR Toolkit is Runtime Agnostic: The Toolkit is designed to work with any compliant OpenXR runtime you have set as the default on your system. It doesn't care if that runtime is the old Windows Mixed Reality one, Oculus, or the SteamVR OpenXR Runtime (which the Oasis driver enables your Reverb G2 to use). 

• The Chain of Command: When you launch MSFS into VR, the process will be:

1. MSFS (OpenXR Application)

2. \rightarrow OpenXR Toolkit (API Layer for FFR, Sharpening, etc.)

3. \rightarrow SteamVR OpenXR Runtime (The default you set)

4. \rightarrow Oasis Driver (Which communicates with the Reverb G2)

The OpenXR Toolkit remains essential for MSFS VR users because it provides features like:

• Foveated Rendering (FFR): Renders the edges of your vision at a lower resolution to save GPU performance. 

• Upscaling/Sharpening: Tools like FSR (FidelityFX Super Resolution) and CAS (Contrast Adaptive Sharpening) to improve clarity. 

• Manual Resolution Control: Independent resolution control, often leading to better results than the built-in SteamVR or MSFS sliders alone.

You will manage the overall headset resolution within SteamVR settings, and then fine-tune the rendering and performance enhancements using the OpenXR Toolkit overlay inside the sim.

MauBen, thank you for this response, I was under the impression that OpenXR Toolkit was going to decrease performance now with the Oasis driver.

I went ahead and setup OpenXR toolkit. Enabling FFR and FSR has already made a pretty significant improvement which allowed me to increase the headset resolution through SteamVR and bring back some clarity, and at the same time increase performance. It's not perfect yet, but I think I just need some fine tuning. Thank you again for your assistance! 

@Mcfly81 Even you can reduce FOV in the SteamVR options when Oasis is installed, and gain more fps without noting nothing, people speak reducing around 85%. I have to make a new installation of W11 and test because I am still in 23H2, some people say that Oasis is better and other a bit worse than WMR and W10-W11/23H2 in performance.

I have noticed significant improvement with driving sims and other titles with Oasis over WMR. However, my experience so far on flight sims (at least for me) with Oasis has been mediocre at best. However the implementation of OpenXR Toolkit has drastically helped with MSFS2020.

One major plus with Oasis is, at least I no longer have to use my Reverb G2 as a door stop 😆.

On 12/3/2025 at 11:36 AM, Mcfly81 said:

but not getting the clarity I had in the past.

I recently migrated from WMR to SteamVR via the Oasis driver for my G2.  It also seemed to me that clarity was lacking with SteamVR, and it turned out that SteamVR was using the G2's pixel resolution for its "Resolution Per Eye" setting.  Though it seems counter intuitive, it should be 3152x3088 (or thereabouts) to compensate for lens distortion. WMR did this resolution boosting internally for the G2, and IIRC SteamVR in the past defaulted to the distortion corrected resolution for this setting.  Thus, I was surprised to see this "incorrect" res setting in SteamVR, and when corrected, the clarity returned.  The distortion corrected res per eye setting is marked with a tick on the setting's slider scale, which is found in SteamVR "hamburger">Settings>General when Custom is selected.  Here's more on this distortion situation, plus unfortunately this bumped res does cost FPS (but worth it IMO).  Enjoy that upgraded computer!

Edited December 5, 2025Dec 5 by TheFamilyMan

A follow up to my post above.  Turns out, according to mbucchia, that the default (as in not custom) res per eye for the G2 is always set as I gave above for the proper G2 res.  The custom slider, when enabled, initially lowers the res down to the G2's pixel res...ugh.

By empiric habit, I don’t trust a "dynamic default quality setting" (paraphrasing SteamVR's help bubble for the default res setting), and in this case I should have, especially since that mbucchia took special effort with his Oasis driver that SteamVR's default res value is always correct for the G2, regardless of the user's gpu capabilities.  Thanks for bearing with me here...all for naught 🥵

Thanks for the update. I was wondering if I was subject to the placebo effect 😃