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

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.

After a few hours testing this “index” settings on a 3070, I can say that in my G2 the result is pretty nice and sharp (much more than with my own tweaks). So big thanks for that.

My only concern is that I get horrendous framerate drop (like going from 30 to 5) every 30-40 seconds, constantly breaking all the immersion.

This issue looks more like an Nvidia driver issue tho. I’ll now investigate this.

1 Like

@CD8TLympho1818 Thank you for your kind words!

The G2 article is in preparation (I’m doing a few more tests)

but in the meantime I’ve just posted this which might further guide you for the G2 and the NVidia driver (just ignore 446.16 because you have a 30XX) [edited: old link removed]

[update] the full settings and suggestion article for the Reverb G2 is now available here:

My 2070 SUPER VR settings and suggestion (Reverb G2 - WMR)

1 Like


There is definitelly something wrong with this 3D mouse cursor.
Even in OpenXR it eats my resources…As soon as I hover over the toolbar toggle, the fps jumps up.
Just look at this:

It is directly connected to GPU utilization which is only 65% with 3D cursor and 95% when hovering over the toolbar!

I tested this earlier… did not see any improvement unfortunately :pensive:

Would love to see exactly what you followed… I’ve got the same PC except I’m running a 3080 with a Rift S and am having pretty low FPS. Copied his VR graphics settings 1:1 in MSFS, and am running 2.2 (220%) in the Oculus Debug Tool with the ingame at TAA 60 (his preferred option).

Is that what you’re running? My overlay shows only 20 to 30FPS with that depending…

@Radeks40 Are you using any mod? One which is “altering” the toolbar? I can’t see any such difference on my test system (I’ll retry right away to make sure with a different aircraft). However I can see when you’re hovering there is a change between CoherantGT and Manipulators. The former is responsible for drawing the UI (and maybe the EFIS) whereas the later is the thread I believe handling the interactions with the cockpit. If you’re hovering the toolbar it is possible the simulator is no longer checking whether the mouse is potentially over a cockpit manipulator and therefore it is saving checking collisions every frame.

@CD8TLympho1818 are you also trying with the A320?

UPDATE: I confirm I can see this with the B787 but not with the A320 (I’ve to redo a test with this one to confirm), and the most likely explanation to me is the one I’ve given (well this is self-delusion also :upside_down_face: )

Nope, never tried any liner in the game yet.

No mods here and I cannot even move my mouse up to see the toolbar at all - is there a new keybinding to display it while in VR I’m missing?

I feel like I am misunderstanding what you are talking about here, especially based on the screenshots provided in this section:

In short for the Index this is:

FS2020 SteamVR Comments
TAA 100% SS 78% Better for EFIS clarity
TAA 70% SS 100% Adequate for analogue gauges
TAA 60% SS 220% Breathtaking visuals and crisp enough EFIS (my fav overall)

Tip: Thanks to using 78% resolution in SteamVR I can use 100% TAA with adequate fps. This makes EFIS screens readable without the need to lean over. You might also want comparing the two other variations which are giving similar fps but different legibility. The Index will never reach the clarity and details you can get with the G2 but I find TAA60+SS220 giving the best looking inside or outside the cockpit given the 1400x1600 panels.

You’re showing the overall and per-game settings but don’t these sliders do the same thing? Why are you referring to one as “TAA” and the other as “SS?”

I’m explaining this terminology a few post above:

My 2070 SUPER VR settings and suggestions (Valve Index)

It is also explained in the discussion. Try the search feature with “CAS Shader” or “Timothy Lottes”

Unplayable for me with Index and 1080ti run by 10700k. I know the gpu is old but I am waiting for the 3080ti no matter what, but I expected at least a fluid experience in low settings. Taa 60 and ss220 runs bad. So does taa 60 and ss150. Taa100 and ss100 also bad. I even reverted to may2020 drivers with zero impact. Back to DCS until Asobo fixes that mess

Is the default

I have a Oculus Quest 2…does anyone know how to set the SS? I open the oculus debug tool but I dont see anything in there that mentions SS… Thanks!!

I must have messed with it - doesn’t work. Do you know the name of that binding?

In the Oculus Debug Tool, it’s called “Pixels Per Display Pixel Override”. It’s a multiplier, so 2.0 is 200%, and 2.2 is 220% (as per one of his 3 options).

My dude - I’ve got an 8700k running well and a 3080 and I’m so CPU bound at 220% (Oculus Oversample) / 60% (MSFS) - It looks absolutely fantastic but man I’m at about 25fps. My assumption is my CPU is getting killed right now… unless I’m missing something. For you, not sure - you have a faster CPU, but not by a ■■■■-ton… I think we need the next generation or two to come out or we need some serious optimization by Asobo.