Absoultely awful performance on lowest settings using 3070

This looks like Motion Smoothing interfering and wobbling (typical). This is why I prefer disabling it: I can stand juddering but not wobbling.

Juddering is usually unnoticeable when looking the outside front view, it is only noticeable when looking side ways at low altitude, and when moving your heard around in the cockpit.

Wobbling on the other hand is visible everywhere, behind rotating prop, behind and around the wings deforming it along the way, etc…

1 Like

Do we have any BETA testers that had the Index… Because its bullcrap if they skipped the Index owners in the BETA test… Because Index is having issues. Lots.

Are you reading the posts above prior posting?

Thanks for the hint, I will give that a try then

1 Like

Hi, I have the following specs and settings, I get great FPS, around 25-30FPS in London. Having been a beta tester for a month or so I have literally tried all settings, these are the best I can come up with alongside some compromises vs. what I value most:

PC Spec

  • Intel® Core™ i7-6800K running at 4.2ghz (OC)
  • 32Gb 2666mhz DDR4 Ram
  • GTX 1080ti running at 1950mhz (OC)
  • SSD HD
  • HP Reverb G1 v2
    3dMark Fire Strike result : 22147

MSFS VR Settings:-

Rendering Scaling: 50
Anti Aliasing: TAA
Terrain Level of Detail: 95
Terrain Vector data: High
Buildings: High
Trees: High
Grass and Bushes: High
Objects Level Detail: 95
Volumetric Clouds: High
Texture Resolution: Ultra
Anisotropic Filtering: 16x
Texture Supersampling: Off
Texture synthesis: Ultra
Water Waves: Medium
Shadow Maps: 768
Terrain Shadows: High
Contact Shadows: High
Windshield Effects: Ultra
Ambient Occlusion: Low
Reflections: Low
Light Shafts: Ultra
Bloom: On
Glass Cockpit Refresh Rate: High

Hope this helps, remember, the HP Reverb runs at 2160x2160 so the Rendering Scale needed to be 50 to make this more smooth, if I had that at 100, it would tank my FPS. 60 offers better visuals but reduces the FPS by 3-5FPS so wasn’t worth the extra scale for not much gain. In order to run at 100 render scale, I would seriously have to reduce the visuals on other things, which for me is too big of a compromise. I used to have a Vive so 50 render scale is still better but with all the visual pleasures.




You can really get much more without loosing much in terms of “external visuals” if you’re balancing differently.

As a matter of fact, albeit on a 2070S, I can push the G2 to 110% TAA with super crisp EFIS and very good external visuals 30 miles away at 30fps and smooth / stutter free flights.

I’d suggest you review some of your settings which are taxing performance for not much better visual experience:

Terrain 100%, Objects 100%
Buildings, Trees, Grass: MEDIUM
Clouds HIGH if you can afford, MEDIUM otherwise*
Texture Res: HIGH (no need for ULTRA in VR, not enough panel res anyhow unless Pimax 2x 4K)
Aniso + Tex SS: 8x + 2x (better visually and runs better too)
Tex Synth: MEDIUM (you won’t see any diff)
Terrain Shadows: 256 (you really want some in mountainous regions)
Contact Shadows: OFF (you won’t see any diff)
Windshield: HIGH (you won’t get EFIS reflections inside but you’ll save some fps)

Further rationale and explanations behind this:
My 2070 SUPER VR settings and suggestions (Valve Index)

*I didn’t check how the clouds are rendering with latest update, it was supposed to be same as before update 5, but I did find them better in general at MEDIUM visually in VR during the beta.


if you’re running an oculus rift, update the oculus software to the beta software

Thanks CptLucky8, I’ll try those and see how it looks. There’s so many options and different choices, all a balance of scales. I’ll let you know how I get on.


1 Like

Great tip, thanks again. Disabling motion smoothing does indeed improve things considerably!

1 Like

It’s working just fine for me - although I had to play around with settings. Mine is a i7 7700 / 2070 Super / 32 GB ram.

Performance is a juddery mess on my RTX3080 + 10700k with a good overclock and 32gb ram on both my index and (even worse) via link and a Quest 2. I’ve flown hundreds of hours in xplane VR which is by no means smooth but this is surprisingly rough. It seems like every 2-3 seconds there is a mega-stutter.

It’s just functional enough to make me really want to fly exclusively in VR, but unless they can really optimize it it’s going to be 5 years before it’s ideal. I hope the reports of it being great with a G2 are true, but I’m skeptical having heard that song so many times with VR releases.

I have been trying all day to get a reasonable performance…I can just about get 30 frames, but a lot of judder and stutter. Its also unpleasant on the eyes, everything look out of focus with low or medium settings. So I have given up for now. Going back to standard beautiful screen flight. Have to say little disappointing, but hopefully over time it will improve.


64 gb

Definitely give the link CptLucky8 posted a read. I had the same experience as you on a 3080 and 10900k until I implemented his settings. Now it’s largely smooth.

1 Like

Wrong, i can maintain 60fps in 4k with a 3080 and High settings.
I can not maintain 45FPS in VR (smoothing forced on) in Index Medium settings.

Now the pixels per second for the Index at 90hz native res both screens combined (let alone 45fps) is less than required to push 4k @ 60hz, also with lower settings i should be able to easily pump out the required GPU bandwidth.

This smells of extremely poor VR implementation

1 Like

I am on Oculus Quest2 using link. Same results, although I have a lower spec PC - but it runs in desktop mode surprisingly well at quite high settings. I get about 4fps in VR - I know because it it so slow I can count them. Flying at 4fps is actually surprisingly possible and it shows the potential if only it would go up to 20-20fps.

@sthackrey It should have been shorter and faster for everyone just to tell the video, 9min long, is only recommending:

Use the OXR Dev Tools and adjust the OXR Resolution Scale down in order to lower the load and raise the fps.

Much shorter isn’t it?

Now the problem with this approach is that you’re not getting the max you can get in terms of G2 resolution nor you’re getting the max pixels you can get with your hardware.

PS: I’m creating a new post to explain all this.

1 Like

Quick question, do you update the original post to your latest recommendations or de we have to go through each update one by one, or just the first post and the last update? Thanks for all your hard work!

I’m just trying to help people mate.

@sthackrey I’m sorry if this sounded offending, it was not the goal. Instead, I was just trying to point sometimes it is better to just post the main (in this case only) content of a 9min video if this is so short telling: people won’t loose 9mins for 1 sentence read, you’ll lower the carbon footprint of the internet.

On a personal note, maybe I’m too old to understand how spending time watching a 9 min video delivering 1 key message only is better than reading it (well I know why it is 9 min long and not 1…) It is the same when I don’t get it why my kids are spending 10 mins chatting to get 1 info from a friend, while a phone call would give it in 1min only. This is even more surprising when the tool they are using is an actual phone! :upside_down_face:

Nevertheless, here is my point of view about the main subject of the video:

WMR Scaling and Dev Tools - Some Explanations