Ideal settings for RTX 2070 Super / Oculus Quest 2

Hi all,
I have seen some very valuable information in this forum on settings for best performance in VR. I love the information and have been using various settings to improve my experience. Frankly I am now just overloaded doing this time and time again and need to take a break and start again.

I was wondering if someone is using the RTS 2070 super with Quest 2 and if you can provide guidance on what worked best for you. My current setting gives me about 40fps, which I think is reasonably OK ?

Thanks in advance!

This is for my Reverb G2. It’s the first and only VR device I’ve ever owned, despite being overall an IT uber-nerd for more years than I care to admit.

My rig:
10600K OCed (using Asus AI OC tools) to all-core 4.9GHz, all other settings (except RAM) set to Auto.

64GB of CL16 RAM, 3200MHz, speed and settings set manually. My system does not like using XMP, even though it’s perfectly happy with the XMP settings being manually set.

2070 Super, OCed in MSI Afterburner to +100 Core Voltage, 111 Power Limit, 88 Temp Limit, +175 Core Clock, +1000 Memory Clock.

OXR Dev settings:
Use latest preview OpenXR runtime slider “On”, Custom Render Rate checked, set at 50%, Motion Reprojection Disabled, both “Advanced Settings” unchecked.

Workflow as follows:
Reboot system.

Mixed reality portal manually started, displayed on secondary display and minimized. Occasionally it starts itself, perhaps because I put my HMD on my head and triggered the sensor, but that’s untested speculation.

MSFS started from desktop shortcut to minimize background active tasks, but it does at least momentarily fire up Steam, perhaps to insure I’m a legit licensed user. FS window full screen on primary display in “non-VR mode” until after I hit “Fly Now”, after which it hit CTRL-TAB and switch to HMD.

While I’m still in test mode (which I most certainly still am) I don’t start any companion apps like Navigraph, Little Navmap, Pilot2ATC, etc.

FS VR settings as follows:
Under VR Graphics:

Render Scaling: 100. (I keep trying to raise that but it’s already over native for my G2s, so going beyond that seems not to help visual fidelity nor hurt performance, and does not save.) This is inversely related to the OXR setting from above, though I haven’t quite figured out precisely how.
Anti-Aliasing: TAA
Terrain Level of Detail: 150
Terrain Vector Data: High
Buildings: Medium
Trees: Medium
Grass and Bushes: Medium
Objects Level of Details: 150
Volumetric Clouds: High
Texture Resolution: High
Anisotropic Filtering: 16x
Texture Supersampling: 8x8
Texture Synthesis: High
Water Waves: High
Shadow Maps: 768
Terrain Shadows: 128
Contact Shadows: Off
Windshield Effects: Ultra (Only applies during rain/snow…)
Ambient Occlusion: Off
Reflections: Off (Mostly because I found them more annoying than enhancing.)
Light Shafts: Low
Bloom: Off (Was causing harsh reflections into my eyes.)
Glass Cockpit Refresh: High

Framerate: Uncertain. Afterburner is reporting low-mid 30s, but I’m not sure if that’s coming from within my VR session or elsewhere. I have not found any way to display VR framerates within VR, should anyone reading this know, please share with the class!

That said, I don’t chase specific framerate results, rather I go based on whether or not my eyes are telling me it’s smooth. Which it is. Overall smoothness is high, except for looking directly to the side on my TO roll where what appears to be a noticeable framerate is discernable, but you shouldn’t be looking there at that time, anyway.

Graphics are a bit blurry, except zoomed in on cockpit where it’s very sharp. As I haven’t had my eyes checked since having LASIK many, many years ago, I’m wondering if a new script, either in the form of contacts or lenses for use in my HMD might help, assuming such a thing even exists. Odd light streaking in VR nighttime that reminds me a bit of wearing slightly oily glasses.

Most used aircraft: Carenado PA44, day and night with modified GNS530. Next most used is default Baron with modified G1000 and Bonanza. WT CJ4, Cessna 172, Carenado 182, JL3 and a few others have been used once or twice, with no visual anomalies except as noted.

And I think that about covers literally EVERYTHING. Apologies if I got a bit disjointed from bit to bit, I was (am) absolutely exhausted when writing this. If you have questions or comments, please fire away. Now I can’t decide whether to go flying or to take a nap lol…

Thank you for your detailed response, I really appreciate it.

We are not running the same setup, so mixed reality portal does not apply to the Oculus Quest 2 I am guess. I will definitely look into some of your settings.

Where did you get the latest preview for OpenXR runtime? This is an Oculus thing?

Thanks for your thorough response, I have a very noob question: how do I set the OpenXR Dev settings? I can’t find where to set them. I did not install OpenXR, it was already installed with my VR headset software.

@LazerBeam983, across the top, there are 3 tabs, but they don’t look like prototypical tabs. But just click where it says “Developer Settings”. Also make sure you check the MS store for updates.

@vlrning2fly, either the page I very first read about it had a link, or I just got it from the MS Store. I think it was the latter, but can’t say so absolutely. I have ZERO clue whether or not it applies to an Oculus or not, aside from knowing that’s not what I have, I don’t know much lol…

I also kept installing and uninstalling it about 4-5 times before I decided to keep it once and for all. Right or wrong, my perception is that whatever it was doing, not only was it not helping, it was making things worse. I’m not certain who “they” is in this case, but “they” did a crappy job documenting the vary basics on how to get VR setup even for basic functionality.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.