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

I thought the same when I first tried 60Hz (MSFP/XPlane). I know every person is different but now there’s almost no difference for me between 60 and 90Hz. My eyes quickly adapted and 60Hz is my default mode for several months. The only time when I switch back to 90Hz is when I let my kids try VR otherwise they will immediately notice the flicker :slight_smile:

I tried 60Hz again today, but no dice, the flickering was awful. Yet here I am typing this on a 60Hz monitor. I wonder why the LCD panels on the G2 do this? Do they have very short persistence or what, anybody know?

newsflash: new Nvidia driver available!

Hi captain thanks so much for your hard work, I have just changed from quest 2 to reverb g2 are your settings at the start the same you have now

1 Like

Start here

2 Likes

Thanks so much Jonny :+1::blush:

1 Like

We’re all anxiously waiting for our feedback now! :slight_smile:

A quick note in the continuing series of experiments with the G2 and SU5.

Yesterday I’ve tried a different aircraft, in the category of the PA28, at and around Biarritz France (LFBZ), with the added photogrammetry cities for Biarritz and Bayonne from @thalixte (thanks for these, I know this place and this adds to it! They are maybe just a tad too bright though which shows vs the surroundings).

So I first went with my latest episode settings TAA70+OXR70+MR (I don’t know why they are calling it “reprojection” instead of “smoothing” in the OXR dev tools so let’s stick with MR there!)

And it was really not good in terms of MR at all because it couldn’t keep up enough fps for it either ?! This really puzzled me because a day earlier, I could fly the TBM in bad weather at New Orleans, and the KA350 over Los Angeles area without a hiccup?!

So for this aircraft I tried my next recommendation: analogue aircraft = OXR100, EFIS aircraft = TAA100. So I changed to OXR100 first.

Then I tried to find the TAAnn which would allow MR to kick in and stay stable. To cut a story short:

  • on ground TAA60 (otherwise ‘rubber banding’ - which is in fact WMR cycling between MR and no MR)
  • in the air TAA65 and this was smooth and working great flying around the area to the East, North-East.

Visuals were obviously good outside at OXR100 even with TAA65, cockpit visuals were good enough frankly at TAA65 (at least to me) but when using TAA60 there was a visible loss in legibility compared to 65 requiring me to lean forward just a little bit to restore some of it. Not a big deal when taxiing around the airport, but not what I’d like at least for the takeoff roll.

All this to say I still find that my base settings, when using my test system 9700K+2070S, are delivering on their promises for the VR experience for now:

  • TAA100 + OXR50 (with MR) still valid for EFIS centric like Airliners
    → with more powerful hardware you’d raise OXR.

  • OXR100 + TAAnn (with MR) still valid for analogue centric like GA aircraft
    → with more powerful hardware you’d raise TAA.
    → I had to go as low as TAA60 on the ground and TAA65 in the air for MR with a PA28 category aircraft.

  • TAA70+OXR70 (with MR) remains a good compromise when none of the other two are working for me.
    → eventually raising to OXR75 if outside is more important or TAA75 if EFIS is more important and if I can still keep MR enabled.

  • Otherwise you can use of course any TAAxx + OXRyy (with or without MR) but I find sticking with a few choices makes it simpler to quickly adapt the settings to the aircraft and/or the situation, while being sure at the same time of what the expectations are with each (TAA100: crisp EFIS, OXR100: detailed outside)

A question remains unanswered for now: how come I could run the TBM or KA350 at 70/70 the day before with MR, but I couldn’t run a simpler GA aircraft the next day without loosing MR at 70/70. I’m quite fine because for this type of aircraft OXR100+TAA65 in the air (TAA60 on ground) is more pleasant visually when looking outside and it is still correct when looking inside, but there is something which doesn’t add up to me somehow. Another FS2020 mistery :slight_smile:

3 Likes

So today i tried everything imaginable to fix the wing tilt/motion stutter issue im having in VR (3080+g2)… nothing worked.

Again, i’d never noticed it before with MR on and previous updates of FS.

Does anyone else when using MR (my case oxr 70-75 and 100 TAA), have the issue (also tried lower graphics and lower oxr). Try the B58, look out over left wing and bank up and down… the ground will occassionally stutter in view, even when solid “blue” locked in mr (say 22-30 fps even).

I cant eliminate this, minor issue but it wasnt an issue before.

Secondly for those without MR on, how do you eliminate the ground blur issue, i tried everything with MR off to make that work for me, but its just not as clear as MR on, MR on feels more real?

1 Like

I use a 3080/G2 combo and recently played around with MR using a high roll rate plane to see the wings flashing on and off. That what you’re talking about? Very disconcerting, to say the least. Getting non MR ground detail up is by raising OXR and LOD settings.

You wont eliminate that judder until you get 90fps to match the native frame rate of the headset. If you want to enjoy the houses and trees rolling by in a smooth way you need MR. Once in the air or not looking down at close fast moving objects some people wont notice the lack of 90fps as much.

@CptLucky8 I find a sure fire way to make the sim CTD is to Alt+Tab in and out of VR while changing MR options and scaling. If i leave OXR, TAA, and MR settings alone i can usually Alt+Tab in and out of VR without issue.

What’s more, the idea of taking off with one set of settings, then getting out of VR to change settings once airborne is too annoying for the relatively minor resolution boost, not to mention the increased risk of CTD.

I noticed more frequent drops out of MR last night without changing from OXR50/TAA100. Im wondering if it would be beneficial to document when we are seeing the sim perform less optimally than a particular day. To see if our experiences line up. Of course the sheer myriad of factors determining performance make this nothing but conjecture but there has to be some commonality going on right, RIGHT?

1 Like

SU5 made a big improvement with the micro stuttering that drove folks to MR. Now I don’t see much difference with ground visual smoothness between having MR on or not.

I meant I use Mr but can’t get smooth ground even locked in when tilting the wings and looking at the ground there is a fraction of second stutter on the ground movement from moment to moment, this is not present in 2d

Flip side I’d use wo Mr buts far too blurry

Do you have Ambient Occlusion OFF, Light shafts OFF, and TLOD and OLOD 100? Try drop down to those settings and see if you notice a change. It sounds like you’re right on the edge of MR.

1 Like

Def 100 n 100, occlusion off, pretty sure I tried light shafts off… Mr stays solid blue on indicator whole time
Edit: tested light rays off, no change

Also getting ctd just launching the sim alot, same deal switching vr on and off (randomly)
ucrtbase.dll error (no addons, even turned off overclock)

@Jonny5Alive6618
I’m fine usually when changing OXR res, but sometimes it CTD. Here is what I do: active pause the game, open OXR dev tools, change res, validate res is changed in the status page then close. Activate the game window back, CTRL+TAB and wait at least 10 to 15 sec, then CTRL+TAB again to switch back to VR. 9 out of 10 tries it is working fine.

This is also why I prefer using settings which you can quickly change in-game instead of in-OXR Dev tool, and why OXR100+TAAnn is a good option for GA or light aircraft.

NB: with the Index it is super easy to change the SS res. because you can do it directly with the headset mounted button. You still have to CTRL+TAB twice but you don’t have to remove the headset to do it.

So many compromises with VR!

Do you mean it is solid blue yet it looks like stuttering/juddering and not smooth?

Yeah MR on the indicator is solid blue but with motion of the wing up and down, the landscape will stutter here or there as its tilted (not constant but its there). No degree of changes has cured.

I’m not certain to fully understand what you’re describing here?! I’d suggest you lower drastically the in-game render res. (even if this is too blurry) just to check whether you can see motion smoothing or not. If this works, this means you were pushing too hard on your system somehow (despite the indicator). At least testing like this might reveal a bug/problem somewhere (drivers?) or that everything is working as it should.

Yep tried that, set render scale to ridic low values and other settings, despite this, no help.

I’d say i’d just live with it, but the thing is, it wasnt like this before su5, pretty sure.

So i load up the b58, fly along at say 1800 feet (anywhere, even barren land)… look out to the left, keep your head looking that direction, now just rock the wing (left up and down, so basically left / right yoke), in doing so it starts out smooth, but every so many seconds/rockings, it will create judder/stutter if you watch the surface. Its actually there too, judder if you look left and right and no rocking, the screen view shudders for a half second every now and then.

this could be something broken on my windows install (i did just do 21H1 upgrade in place to rule things out), i have another test install i could try a fresh install of fs on it (forget, i think has to go on its own partition, cant point to the existing one i think).