Interl@ce님이 먼저 게시:

Index user here-- just to confirm that in '22 higher refresh rates lead to extreme jitter/tracking interpolation not present in other VR titles, which can cause severe nauseau to migraines.

Since other input-related issues are also still present I'm expecting this to still be an issue many people aren't aware of.

Web Browser님이 먼저 게시:

Thanks but unfortunately for me it didn't work. I'll keep testing and post any updates that may help others.

Is It?님이 먼저 게시:

So I've been doing a LOT of testing, convinced that they cannot have screwed it up so bad 2 years in a row. And after MUCH testing, I may have hit upon a few reasons why VR has been so bad - and potentially a 'fix'* for this.

* YMMV. I do not proclaim these settings to be THE BEST and GUARANTEED to work. They are working on MY rig, and are consistent, and may not work for yours.

Having said that... Let's begin.

My setup: RTX 3080ti, 5800x Ryzen (OC to 43.8GHz), 48Gb RAM, Quest 2 Headset. Windows 11 Pro.

ALL testing was done on the Singapore track, Heavy Rain, using the benchmark tool, as this is likely the worst case scenario.

My Steam Settings:
Video: Render Resolution - 124% (2296x2332)
ASF - On

Developer:
Current OpenXR Runtime: Oculus.

Oculus:
Refresh Rate: 72Hz (any more and it is just too unstable)
Rendering Resolution: 1.0x (4128 x 2096)

F1 23
Graphics Settings
Lighting - Medium
Post Process - Low
Shadows - Medium
Particles - Medium
Crowd - Medium
Mirrors - Low
Car and Helmet Reflections - Medium
Weather Effects - Ultra High (you could reduce this to as low as Medium)
Ground Cover - Medium
Trees - Medium
Skidmarks - Low
Skidmarks Blending - On
Ambient Occlusion - Off (Vital, this and SSR absolutely TANKS the FPS in VR :( )
SSR - Off
Asynchronous Compute - Low
Texture Streaming - Low (This is also VITAL, any higher also tanks FPS)
High Quality Hair - Off (Who cares about hair!)
NVIDIA Reflex - On + Boost (obviously not applicable to AMD)
NVIDIA SER - (I do not have a 4000 series - I would be VERY interested to know if this helps at all - leave comments below?)
Chronic Abhorration - Off (unless you like the LSD effect...)

Video Mode
Resolution - Doesn't matter, although lower might reduce a little GPU overhead perhaps)
Display Mode - Windowed (This appeared to make a difference, Fullscreen stole a few FPS)
Output Monitor - whatever
Anisotropic Filtering - Off (This REALLY seems to affect FPS. In VR, I don't think it really makes much difference, although you might want to try 2x as it does make close cars look a little better - if that matters.)
Anti-Aliasing - TAA Only (NONE of the other methods are any use. Other than DLSS/FSR look bad in VR (oddly FSR isn't quite as bad), they REALLY tank the FPS.)
Dynamic Resolution - Off (I never actually tried this, but I figured it would look awful in VR).

There you go. I have 72 FPS solid in Monaco and Singapore* in heavy rain, and there does not appear to be any head tracking issues.

* Singapore and also Qatar at least, seem to have some REALLY poorly optimised spots on the track that can cause significant FPS drops, regardless of your settings. I suspect an asset dump, or something similar. No setting I tried eliminated these entirely, but they didn't detract from the racing.

Again, YMMV, and if you have a 4070, 80 or 90, you can probably increase the Steam VR resolution a bit - this can be done in real time if you're careful (it can cause the compositor to give up if you mess about with it too much).

Other headsets I have no idea about - but if you keep the Steam VR resolution the same it probably won't matter.

Let others know if these did or didn't work in the comments - and if you have improved on them, also share!

Darkangle님이 먼저 게시:

World's fasted pc. 43.8GHz and this game STILL doesn't run properly?

All kidding aside. No effort has been put in VR. It has been tacked on to tick a buzzword checklist, but expect the same as the previous title = no fixes, no effort. Just shake and bake and repeat.

Is It?님이 먼저 게시:

Web Browser님이 먼저 게시:

Thanks but unfortunately for me it didn't work. I'll keep testing and post any updates that may help others.

Could you be more specific, as in what headset you have and your GPU? I'm thinking about compiling a list of hardware and headsets to see what appears to be the minimum viable requirements? And did it improve in any way at all?

Web Browser님이 먼저 게시:

Is It?님이 먼저 게시:

Could you be more specific, as in what headset you have and your GPU? I'm thinking about compiling a list of hardware and headsets to see what appears to be the minimum viable requirements? And did it improve in any way at all?

I have a 3080 and the headset I use is the Quest 2. For me running the settings on low actually somehow made it worse. Instead of lag whenever I got near lights or when looking around, I started getting frame tearing even sitting in the garage. This is for both night and day tracks. If any other info would be helpful let me know!

Dyskord님이 먼저 게시:

Do codies have anyone on these discussions? This post needs to be pinned my man, i worked with this guide for a couple hours last night making tweaks and have absolutely none of the jitter or delayed head tracking, and it looks fantastic.

For reference, im playing on quest 2, 5600X CPU and 4070 GPU. Oculus set to native resolution, Steam SS at 130%, VR High preset is absolutely pinned to 72hz (even with texture streaming on high!). SER does offer a small performance boost of maybe 5-7% or less it seems, with no cost that i can determine, so if you are using a 40 series, no reason not to turn it on for a few free frames.

Fantastic work here mate, well done.

Is It?님이 먼저 게시:

Web Browser님이 먼저 게시:

I have a 3080 and the headset I use is the Quest 2. For me running the settings on low actually somehow made it worse. Instead of lag whenever I got near lights or when looking around, I started getting frame tearing even sitting in the garage. This is for both night and day tracks. If any other info would be helpful let me know!

I presume you mean VR Low? I would definitely check your Steam VR settings, and make sure resolution is NOT set to AUTO, but to 75% as this makes a huge difference to the overall FPS. DON'T make the mistake of thinking you shouldn't need to reduce this - unfortunately, you will - and now I think about it, I remember a setting in the game, under VR settings, that allows you to override SteamVR scaling - I would ensure this is OFF. (I guess you could use this instead, however I have not tested it using this setting).

Also, check on SteamVR and see what Compositor is being used - it should be Oculus. If not, then it might be worth trying to change the compositor being used by going to the EA App, F1 23, Properties and see if -vrmode oculus works (I don't know). If it's using the Steam or OpenXR compositor, that might be why my settings are not as effective.