My VR Settings - Best Balance

[drhotwing1]

Greetings everyone. After a lot of trial and error I wanted to take the time to post what's working for my configuration in VR. Keep in mind that I set this to try to get the highest quality out of VR but still be smooth enough to enjoy; your results may differ so consider this subjective hoping to help get some of you going with a very good VR experience without pulling your hair out :)

Firstly, here is my PC specs that the settings are based off;

Intel Core i9-9900K CPU
RTX 2080TI GPU
32GB Memory
W10 64bit
Oculus Rift S

Here are my MSFS VR settings;

Render Scaling - 100
Anti-Aliasing - TAA
Terrain LOD - 150
Terrain Vector Data - Medium
Buildings - High
Trees - Medium
Grass and Bushes - Low
Objects LOD - 150
Volumetric Clouds - Medium
Terrain Resolution - High
Anisotropic Filtering - 4x
Texture Supersampling - 2x2
Texture synthesis - Medium
Water Waves - Medium
Shadow Maps - 768
Terrain Shadows - 256
Contact Shadows - Medium
Windshield Effects - High
Ambient Occulsion - Medium
Reflections - Medium
Light Shafts - Medium
Bloom - On
Glass Cockpit Refresh Rate - Medium

Under Traffic;
Airport Life group all at 50
Land and Sea Traffic all at 50

Also some must do's
1. Make sure that you have MSFS pointing to the Oculus API in the registry:

Right-click on your Start menu and select Run
Type in “regedit” (without quotations) and hit Enter.
This will launch the Registry Editor
Locate the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1
For ActiveRuntime change its value to the one that matches your platform (note: default path is shown below):
C:\Program Files\Oculus\Support\oculus-runtime\oculus_openxr_64.json
Close the Registry Editor

2. If you plan on using MSFS in VR mode most of the time, make sure that you change the following settings under the MSFS PC settings;

Display Mode - Windowed
Full Screen Resolution - 1024x768 (or lower) - This frees up resources to be used for VR, and it helps a lot.

I hope this gets you going somewhat, if you have a slower PC than my specs you will need to go backwards from here to get you a smooth experience.

[Trew Domko]

yikes. hope they optimize the game a lot more through time. cant see myself getting the game and playing in vr if its so unopimized

[drhotwing1]

Publicado originalmente por Trew Domko:

yikes. hope they optimize the game a lot more through time. cant see myself getting the game and playing in vr if its so unopimized

You would be surprised how good this looks in VR even with settings much lower than one would like.

[opjose]

Unoptimized? Hardly.

The sim is trying to display far more than any other VR sim, and streaming to boot.

For what it does it runs surprisingly well.

---

drhotwing1

Nice!

The Tip about display mode is something I completely forgot about doing too.

Thanks for bringing that up!

I am running the same hardware as you, excepting dual 2080Ti's in NVLink mode.

I haven't tried alternate frame rendering in VR mode yet, but it works brilliantly on my main screen to double frame rates.

[ImXL]

I have a 3080 and G2. Resolution at 80%, Buildings medium, Clouds high and Occlusion low.

It works great most of the time, but can't low-fly through Manhattan without stuttering.

I'll try lowering the PC settings. Never thought it would have an impact because as soon as you enter the VR mode the screen is replaced by a replica of what you see in the headset.

[★Macman★]

Publicado originalmente por ImXL:

I have a 3080 and G2. Resolution at 80%, Buildings medium, Clouds high and Occlusion low.

Start with the Default VR, notice it does not use Occlusion, make it 100% else you get smaller Cockpits, make up the difference gained by using WMR Developer Tool from MS Store, in that Set Latest OpenXR=ON, set SS=50% (it's lowest) then keep TAA but rid other Aliasing, with a 3080 you will be ok with most on Medium and some on High. Terrain Shadows are the Killers. You may just like Clouds Medium too. It can then play better on a fresh start rather than after tweaks. Oddly, any changes to the ingame SS only changes the Scaling Sizes after a Game restart.

[Crazy_Juergsi]

i can read the displays in the A320, which is really annyoing :(
speed and altidude...

[opjose]

Same hardware as the OP, I made the following changes.

Render Scaling - 110
Anti-Aliasing - TAA
Terrain LOD - 200
Terrain Vector Data - HIGH
Buildings - High
Trees - Medium
Grass and Bushes - Low
Objects LOD - 150
Volumetric Clouds - Medium
Terrain Resolution - High
Anisotropic Filtering - 4x
Texture Supersampling - 2x2
Texture synthesis - HIGH
Water Waves - Medium
Shadow Maps - 768
Terrain Shadows - 256
Contact Shadows - Medium
Windshield Effects - High
Ambient Occulsion - Medium
Reflections - Medium
Light Shafts - Medium
Bloom - OFF
Glass Cockpit Refresh Rate - LOW

I made the above changes and also...

Offset MipMap bias -0.7
Force Mipmap Generation on all layers ON
Use FOV Stencil OFF
ASW Force 45fps ASW Enabled
Encode Resolution Width 2784
Supersampling 1.2 - 1.3

And things look SOOOOO much better

Building pop-ups have disappeared, the flicker and graininess is gone!

The cockpit scaling looks great now and you really feal like you are in a cramped Cessna or huge 787.

[drhotwing1]

Publicado originalmente por opjose:

Same hardware as the OP, I made the following changes.



And things look SOOOOO much better

Building pop-ups have disappeared, the flicker and graininess is gone!

The cockpit scaling looks great now and you really feal like you are in a cramped Cessna or huge 787.

How is the performance with the changes that you made?

[opjose]

Re: Performance

Much better than I had thought they would be. I do see a slight update lag when moving my head side to side, but when not performing big view shifts the screen update rate is very good.

The biggest problem I see is with data streaming.

I get pauses as larger amounts of data are pulled down from the server, but usually these are when large texture fetches take place. I've seen the hourglass appear in VR going into cities.

Pre-fetching the area or revisiting an already traveled area from the rolling cache solves that.

I tried flying into Miami at night using the Miami night time mod, and the results are awesome, though at times it was if someone below started to flip on the highway lights in series.... though that looked pretty realistic.

The lights did not all come on at once, it was as if the "turn on" signal was travelling down the highway a half second or more between lights.

[drhotwing1]

Publicado originalmente por opjose:

Re: Performance

Much better than I had thought they would be. I do see a slight update lag when moving my head side to side, but when not performing big view shifts the screen update rate is very good.

The biggest problem I see is with data streaming.

I get pauses as larger amounts of data are pulled down from the server, but usually these are when large texture fetches take place. I've seen the hourglass appear in VR going into cities.

Pre-fetching the area or revisiting an already traveled area from the rolling cache solves that.

I tried flying into Miami at night using the Miami night time mod, and the results are awesome, though at times it was if someone below started to flip on the highway lights in series.... though that looked pretty realistic.

The lights did not all come on at once, it was as if the "turn on" signal was travelling down the highway a half second or more between lights.

There are a couple of things that may help the loading a bit;
1. you can increase your memory from 16gb to 32gb so that you don't have to many loads from the system page file. If you do this, make sure that the speed of the memory is as fast or faster than what you have currently.
2. You can increase the casche in data settings if you have some hard drive space that you can afford.
3) mainly off of 2, you can identify custom areas that you tend to fly over a lot and add it to the manual casche.

I don't know if 2-3 will work for your situation as it may just be a slower internet? but using the casche feature will pre-load photogramtry buildings and trees into memory.

Good luck!
- Jeff

[jons]

Youre from aerofly aren't you?

[opjose]

Publicado originalmente por drhotwing1:

There are a couple of things that may help the loading a bit;

1. you can increase your memory from 16gb to 32gb so that you don't have to many loads from the system page file. If you do this, make sure that the speed of the memory is as fast or faster than what you have currently.

2. You can increase the casche in data settings if you have some hard drive space that you can afford.

3) mainly off of 2, you can identify custom areas that you tend to fly over a lot and add it to the manual casche.

I don't know if 2-3 will work for your situation as it may just be a slower internet? but using the casche feature will pre-load photogramtry buildings and trees into memory.

Good luck!
- Jeff

Yup I already have 32GB of RAM and a 32GB rolling cache.

Item "3" produces the biggest benefit.... though it at high settings it eats hard drive space fast!

That makes me wonder though.

If you've cached an area on low or medium, and have data streaming turned on, then fly low, does streaming photogrametry override your cached data to give you better building details?

BTW: Your 100% render scaling suggestion is on point.

You can even flip to say 80 while in cockpit view, and the difference is dramatic in terms of gauge fuzziness.

[drhotwing1]

Publicado originalmente por jons:

Youre from aerofly aren't you?

Yes I am. I worked for IPACS until around three weeks ago.