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

@AlexejGeldt
There is no such throttling and prediction settings with WMR/OXR. These are only in SteamVR and only if you’re using the StreamVR compositor (exit Vive for example).

As for NVidia VR Frames, since day 1 the overall consensus has been to using 1 to get the best performance and stable fps (less spikes). Some are reporting sometimes they have better results with 2,3,4 but most that I can read feedback from are finding it is better for them with 1, which I recommend too (both for Index and G2). It is possible it is video card dependant as well, or VRAM dependant?!

The most important setting for reducing “wobbles” and for stabilizing fps that I’ve identified is Multithreaded Optim. OFF (SteamVR and/or WMR).

NB: prior SU5 finely choosing VSync related settings where positively impacting the experience too in VR (see my older recommendations) but since SU5 they don’t seem to be having the same influence anymore (which is good and expected), and therefore I don’t recommend to change them anymore either.

The TAA scaling dance trick with WMR is a workaround to kick MR in, working for me, and now at least also working for @Jonny5Alive6618 (and I hope this helps many more people too!)

1 Like

I noticed this too, I didn’t understand really why but sometimes it would be very choppy in vr, and just adjusting TAA slightly has helped for me. It’s like everything gets re-drawn correctly after a small change and then settles in.

I really hope the devs can fix this temperamental VR, it shouldn’t be like this.

2 Likes

@CptLucky8 OXR 100 / TAA 65 is my number. I’ve always noted my res has been 5 to 10 below yours since the beginning. But everything else seems to scale well. The only difference is my i5 9600 at 5gh to your i7 9700. And my desire for high clouds.

Photogrammetry seems to account for about a 5 or 10 hit on the render scale, if you will.

Explain it like I’m 5;

Why is 100/50 - 75/75 - 50/100 a more efficient combination than any other combo?

1 Like

Please explain what everyone is referring to with, e.g., “TAA at 80”?
Don’t you all mean Terrain Detail? Am I not correct that TAA is not adjustable, other than selecting an antialiasing mode such as TAA, FXAA etc.?

They are talking render scale value, though frankly im not sure where the TAA part comes from :slight_smile: I just accept it

1 Like

I’d suggest you start with the 1st post for all the details. It is just a convenient way to “tag” each resolutions we’re talking about (there are several different to adjust).

I believe the i5 9600 vs I7 9700 might perfectly explain the difference. In this case you might want to try reducing every CPU related and see whether you can raise back your TAA res. to same levels?

Namely: buildings, trees and traffic first

A quick update for tonight (my time):

I’ve done another flight with FBW A320 in South America this time, once again:

  • TAA65+OXR100+Clouds Med on the ground to get MR
  • TAA70+OXR100+Clouds High in flight, touchdown with MR
  • TAA70+OXR100+Clouds Med again when taxiing

So this seems to be pretty good and I believe I’m getting a good overall feeling I’m closing in on final recommendations.

NB: at the beginning I had once again the MR/rubber banding problem but this time I tried something else to cure and I’m posting it for other to try and confirm: instead of playing the TAA dance back and forth, I’ve done this:

  1. press the WIN key on the keyboard to open the Windows start menu (while wearing the HMD, this witll also cut the sound).
  2. Move the head side ways until I notice MR kicks in.
  3. press the WIN key again to restore focus on the FS2020 main window.

It was much more convenient than opening the settings and trying to grab the smal slider dot, and I’ve had to do it twice and it worked reliably too!

This new trick in the sleeve is starting to making me wonder about changing the Win10 perf options for “background process”…

Other than that I’ve also tried to see whether I could get rid of the shimmering in trying something at the NVidia CPL level. I’ve already reported a problem about the anisotropic setting not reseting back, I thought maybe I could use NVidia sharpen set to 0.01 in case the shimmering was due to the sharpening setting not reseting as well. Unfortunately this didn’t change anything.

2 Likes

I’ve always found running the sim in window mode was a performance hit.

Temporary Anti-Aliasing. LOL, another acronym for your collection.

1 Like

Fbw 320 oxr 100 taa 60 clouds med.

I had to do the render slider. Pressing Windows key has no impact on my headset. Just the start menu opens in the sim. Are you pressing Windows key on your g2 remote?

It was smooth the whole way, outside looked great, efis good. No CTD. Your taxi mods worked great. Thanks for those!!

Fbw320 experimental build flying well.

1 Like

@Jonny5Alive6618
The keyboard WIN key, the one opening the main Windows menu (the same when you click the Windows logo to the left of the Windows task bar). I have had good success with it but sometime you have to do it twice, or give it more time:

  • press WIN key on the keyboard, the sound in the headset stops but the game continues rendering
  • eventually turn your head toward something “light” 3D wise like the overhead panel of the A320 or the location where your feet are supposed to be
  • move the head sideways a few times until you notice there is no hiccups (but not necessarily MR yet)
  • press the WIN key again to close the Windows menu and restore sound in the headset.
  • from then on there is a great chance MR kicks in, but not always.

Nothing very scientific here, and maybe coincidence as well, but this has been working more often than not with my test system so far and eventually what you could do is use the WIN key approach first, twice at most, and if this still doesn’t work then use the “TAA dance” trick.

Hitting that key has no effect on the sims audio for me. Right now I’m flying the first leg of the Iceland bush trip at OXR100/ TAA 75 TLOD 200 Clouds high.

Earlier I was whipping the fbw around Chicago landing at meigs (addon) at TAA 60 clouds med TLOD 200

This is all of course with MR with practically no drops.

Lots of mods loaded up too, meigs, gaistv2, we love vfr 1&2, fbw, several aircraft, dnbof weather, your taxi markers.

Great stuff!

1 Like

Any updates on how things are performing after the update? (I havent had a chance to get back to things yet, or update).

I see no major perf change, but it seems to me there is a slightly better sharpness with TAA70+OXR100. I haven’t tried the “pre-caching” setting either and left it at its default for now.

1 Like

Thanks for the update, well at least no decrease haha

I tried the update, i cant get past the second (42mb) update file, just sticks (admin or non admin launch mode the same). Blah (turned out i had to sign out of xbox, relaunch, this time there was a much bigger 50gb plus update and it worked, test vr later)

Im flying with MR off these last few days, & these settings hold up incredibly well without MR too. (Now that I think about it I also dropped clouds down to med from ultra/high) MR has been a little inconsistent and annoying recently.

I may try remove my overclock and see if there’s any correlation.

Maybe it’s because I used MR for so long my brain is automatically ignoring the wobbles and artifacts. Either way. I’m liking it.

2 Likes

I used @CptLucky8 settings and latest Studio drivers, OXR70 TAA100 and it’s smooth with smooth MR, but I have tiny but very annoying regular stuttering - the image freezes every 1 or 1.5 seconds for a very short time. So it’s like tiny hiccups. They are very regular, and otherwise FPS feels smooth and MR is working buttery smooth. Almost no MR artifacts (with prop mod), which usually means there’s enough overhead.

What could be causing the regular hiccups and how to cure that? Any ideas? I heard about putting cache onto the RAM drive - anyone tried that? I have 64Gb of fast RAM, so maybe it’s worth exploring. But I have 60Gb cache configured, and putting it to RAM would mean reducing it to 16Gb maybe. Not sure the risk/benefit here…

BTW I also tried SteamVR OpenXR to check if it got better, with SteamVR resolution of 70% (TAA100) - and it’s horrible. I don’t think motion reprojection works for me in SteamVR at all. It’s like my G2 had a nervous tick - it’s jerking few degrees back where it was a second ago, all the time, every half a second of so, like time-travel hiccups. WMR OXR is at least playable, if only I could get rid of the tiny regular stutter.

1 Like

I’m experiencing the same with the latest 1.19.9, not as much with the prior version. The latest WMR/OXR Dev Preview seems a little better as well than the prior dev preview regarding this.

Usually when these are happening it is most likely the motion smoothing is taking just too much enough, in addition to the frame render time, to overflow the threshold (44ms / 22.5fps) and cause a hiccup. The next frame, motion smoothing will be disabled and there will be enough render time but it will show without motion smoothing. The next frame, motion smoothing will kick in again and overflow etc… until both render time + motion smoothing time stabilize under 44ms again.

There doesn’t seem to be any setting you can tune for adjusting the threshold detection logic, except a few registry values whose names are telling they might be related but I’ve not experimented with:

  • Is this one allowing to motion smooth more than 4:1 in WMR (like up to 6:1 with SteamVR)?
    .
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Spectrum\HeadPredictionAmountFrames

  • Otherwise these are most likely for 2D full screen WDM compositor:
    .
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm\ExtendedComposition\ExclusiveModeFramerateAveragingPeriodMs
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm\ExtendedComposition\ExclusiveModeFramerateThresholdPercent

PS: I concur SteamVR OXR → WMR for SteamVR is not better than WMR OXR directly now (but it used to be!)

PS: the most impactful setting when you’re at the motion smoothing threshold is Clouds. Just going from HIGH->MED or MED->LOW changes a lot the experience (both in terms of motion smoothing but unfortunately visually as well). This is usually the first one I change and with my settings on my test system, nearly the only one I have to change on ground, which I can revert back once airborne.

1 Like

Anyone here getting “rubberbanding”? With mr on the scenery moves nice and smooth then speeds up for half a second then back to normal. It’s not stutter or judder, it’s a new phenomenom to me that started about six months ago.
Sometimes increasing render scale stops it, but then the risk of stutter increases, it even happens if I reduce render scale to minimum (about 840x840!), this is on a 3090 and 5800x.
Changed every setting I can think of, uninstalled openxr numerous times and it’s still there.
Definitely openxr or sim related as all other vr stuff is butter.
It’s come to the point that I don’t want to load it anymore, and this is by far the most played game I have.
Any advice out there?