My 2070 SUPER VR settings and suggestions (Index - SteamVR) 🟢

Yes, the way I told you how to do it will work regardless of where you bought it from and is how I tested it. I also have the windows store version.

I don’t believe which version you have is actually particularly relevant for most things though because the Microsoft store and steam store only contain the launchers which then install and launch the game separately from either platform. Whether you have the steam version or the windows store version should be largely irrelevant.

ah ok, thanks.yes i see now, when i restarted the WMR software now complains that OpenXR isnt set after I changed SteamVR to not use OpenXR.


Yesterday I said that in my case , switching from OpenXR to SteamVR environment gave me a better overall results with my G2.
Well as far as it’s true, I have to admit that when OpenXR is active and locks to that magic 30fps, it is actually really smooth and better than SteamVR environment at higher frame rates (35-45 fps).
This is clearly visible at dynamic turns…
Now my question is simple - if SteamVR is able to give me that constant 35-45fps almost everywhere, why my system is struggling to hit 30fps in OpenXR dev with the same resolution and settings…? I just need that steady 30fps in OpenXR and I’m set…

Eagerly awaiting your G2 results as I continue fiddling with mine. I think I’m nearly at a “set it and forget it” point with quality/performance tradeoff, looking forward to incorporating more of your findings.

Also, is there a place we can send you a beer or coffee or something for your efforts? Thanks.

@paulr70xbox I’ve just posted this information about OXR via Steam or WMR:

@Radeks40 Thank you for sharing this information. As a matter of fact I always have better results with WMR OXR instead of SteamVR OXR with the G2, but let’s keep this for “My VR Settings - G2” discussion later if you want. I’m interested in exploring these avenues.

@Trowels I thank you for your kind words! If you look at my profile, you’ll see my website…

Once the SDK is incorporating the minimum necessary, the best way to supporting these efforts will be flying with the Reality XP GNS and Reality XP GTN in FS2020 :wink:

1 Like

My best NVidia Driver recommendation for VR (and 2D):

NVidia Card Driver ver. Comments
20XX/30XX 457.30 Best for VR on 3090, 3080 and 20XX
3060 457.51 Best for VR on 3060
any 471.41 good enough to replace the venerable and trusted 457.30!

Tip: When installing NVidia driver, choose “Custom Installation” and select only “Core Driver files” and “NVidia Physics” (deselect all other options and never install GeForce Experience - see below).

NB: The NVidia driver bugs in VR is present with any driver release after 446.14. However I do have the best results with 457.30 which is close to 446.14 and compatible with SW Squadron with any 20XX card. Many other users are also reporting best results with 457.30.

:warning: 457.30 and 457.51 don’t include the latest security fixes unfortunately

More info: Security Bulletin: NVidia GPU Display Driver - January 2021

Here is some of the latest NVidia drivers history:

NVidia Card Driver ver. Comments
20XX 446.14 Last known WDDM 2.6 prior HAGS (recommended by SteamVR)
" 452.06 1st one with FS2020 optimizations (last one without FrameView SDK*)
3090 456.38 min ver required
3080 456.38 min ver required
3070 457.09 min ver required
3060 457.51 min ver required
any 471.41 good enough to replace the venerable and trusted 457.30!

*this is a new SDK shipping with the driver installation, most likely if you install GeForce Experience. Looking at the files it seems it is meant to capturing the VR views and measuring performance (the type you see in the form of graphs with fpsVr) and I believe it has some Vive IP in there. However it seems Nvidia VR problems started since they included this SDK

@Taleeah Thank you for your kind words!

Yes I do know about the Nvidia driver and I’ve already commented in this discussion about it here:

[update 27JAN2021] I’ve change the warning about the security fixes (thanks @AlexE75)
[update 10AUG2021] Added 471.41


Which settings specifically did you use? Did you change the resolution in SteamVR settings (specifically for MSFS 2020) to 78% resolution? I thought that we’re ignoring SteamVR due to changing the registry to point at the Oculus driver?

Did you do this in the Oculus Debug Tool?

What specifically did you change to get SS to 220%? Is it ‘Pixels Per Display Pixel Override’?

I also assume that’s a multiplier? What exactly do you set it to… 2.2? Or do you just put 220?

Also, where exactly is everyone changing their TAA - wouldn’t it always default to 100%?

And last question - do you have your Oculus settings under devices set as “Prioritize Performance” or “Prioritize Quality”? (the former will lower the resolution)


Look what I’ve just found!
In SteamVR environment (it does not happen in OpenXR), there is a huge jump in frames and smoothness when you actually point your mouse cursor over the toolbar toggle! 3D mouse is turning into 2D cursor and BAM, big jump in FPS! No jitters when looking around the cockpit!
It looks like during the flight, the 3D cursor is actually interacting somehow with head movements causing lots of stutters!
Is it only me or someone can confirm the same behaviour?



No change on my setup. Downtown Tokyo, fairly consistent frametime on both GPU and CPU sides.

Note how smooth my CPU frametime is, but this only happens with 120Hz refresh mode. If I set my Index refresh rate to anything else it would pretty much ■■■■ out.

1 Like

Thank you!
So there must be something wrong with my system…
Anyway in G2, with OpenXR and steady 30fps it looks like this:
Absolutely incredible!


Do you mind elaborating what is wrong? The videos are really smooth and apart a few scenery loading stuttering there seems nothing wrong, except I’d set the Gauge Refresh HIGH and you’re making me envious for a 3070/80… :joy:

Just to make sure: these are shot with the G2 using WMR OpenXR (not SteamVR) with Experimental OXR (v105) or current (v104)? With motion reprojection Auto or Always On?

Hi guys!
So, this is my result with HP Reverb G2.
30-36 FPS locked to 30 with RIVA Tuner (it removes most of jiggering in the cockpit) (( Sometimes don’t have constant 30 frames at Orbx Wiena or Dulles but with 90TAA that problem is also solved))
Driver: 446.14
100TAA OpenXR50
Terrain LOD 100, clouds high, 16Xaniso, textures ultra, windshiled ultra, rest on medium.

i9 9900 @5.2, 32Gb @3400Mhz, Nvme 512 Adata, MST 2080Super @1980 / 8900

1 Like

I was refering to my previous post. In SteamVR env. I discovered some weird issues with 3D mouse pointer.
Anyway, I’ve now stopped playing with SteamVR as I’m pretty sure the OpenXR is the right path to follow:)
Here are my current OpenXR settings:

Nvidia CPL settings acc. to your recomendations.

I’m pretty sure that in case of GA I can bump up that gauge refresh rate.
With FBW A320 it is definitelly harder to achieve steady 30fps. It deeps down to 26-27 on the ground depends on location and weather. Heavy clouds will have an obvious impact on that. Anyway it is still very playable.


Man, these are pretty amazing results with 2080S!
If I only could OC my 5600X up to 5.2Ghz…Even with that new architecture, I think that might be the botteneck as I can only get up to 4.7Ghz all cores.

I just tried this and can confirm a noticeable difference in frames.

I disabled “Enhance pointer precision” in Mouse Control Panel and it seemed to even out the framerates.

It may have even helped in Flat Screen mode


Thank you for the additional details. TAA80+SS60 is one of the 3 settings I’m retaining for my upcoming G2 recommendation topic. It is interesting my OXR “About” box is not displaying at the same location?! (mine is upper/right).

Looking at your settings, those you’ve set lower than my Index recommendation is wasted GPU possibility on the 2070S and you have more room with the 3070. I’ve spent countless hours validating up to what level and with which combinations to make sure my “non negotiable” ones are set to a minimum acceptable level while others have marginal impact whether low or high. In particular, you might want to change a few and compare (and let me know!): Aniso 8x (min req.) / Tex Synth. MED / Waves MED / Terr. Shadows 256 / Windshield HIGH. I believe you might even raise Shadow Maps to 1536 with the 3070 and don’t feel the difference.

It you have ample CPU avail you might really want to compare Glass Ref. Rate. to HIIGH as this eliminates stuttering induced by the EFIS (at additional CPU and GPU cost though) and if you do, you might want to lower clouds to MED or HIGH then. This could be the tradeoff in your overall settings you can balance whether flying GA or Airliner for example.

NB: Clouds impact depends only on the volumetric clouds level of detail, not if they are visible, in most cases. This is because their voxels are computed whether there is something visible or not in any case (unlike what you might be used to with FSX or XP11). It is possible when set to ULTRA there are additional computations only if they are visible but at MED and even HIGH I don’t see any difference in fps whether for example selecting clear sky or scattered clouds preset!

PS: I’ve forgotten to ask you: don’t you see any deformation when turning your head left to right? It does pincushion distortion with my system if using any OXR Reproj. settings and Scale between 50 and 60 included with OXR Preview (v105). Besides, if you disable OXR Reproj. you might immediately notice much sharper and more detailed image in the headset.


I’ve figured out where to super-sample (within the Oculus Debug Tool in my case).

Where are you setting your TA?

In the VR graphics settings in MSFS. He means “render scale” setting with TAA as the antialiasing option.

1 Like

Ah thank you - I was so confused. Now I just need to make sure putting “2.2” in as the oculus SS (Pixels Per Display Pixel Override) = 220% :sweat_smile:

May end up rewriting a guide just for the Rift and Rift S if so since this was a little confusing and I’m not absolutely incompetent when it comes to hardware/software.