VR Settings - Try these. :: F1® 23 General Discussions

F1® 23

All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

F1® 23 > General Discussions > Topic Details

Is It? 13 Jun, 2023 @ 5:14pm

VR Settings - Try these.

*** I've removed my previous settings guide as, quite frankly, it is obsolete.***
*** Read my new notes below! ***

EDIT 3: So I've been trying more settings after someone else (I don't remember who it was, sorry) mentioned something about how the game ran better on one PC over another with identical hardware - except for one difference - the monitor.

It seems that the reason that the game in VR looks so blurry, is that it is linked to the GAME settings. So, for example, if you have the in-game resolution as low as possible, in order to reduce GPU overhead, like you would expect to be a Good Idea, it doesn't seem to run any better AND looks very blurry, as the game is rendering VR in THAT resolution, and then seems to upscale to match the SteamVR resolution.

The answer is to set the resolution IN-GAME as high as possible. In fact, you can edit the emgine.ini file to match the SteamVR settings, which in turn should match the Y resolution of your headset (for example, the Q3 headset has a resolution of 4,128 by 2,208, so you would normally set SteamVR to be as close to 2208 as possible. Afterwards, you'd set the file to read-only.

Then, in the Meta app settings, you set the resolution to match this, preferably at 90fps, although you can of course go as low as 72Hz to make life for your GPU easier - assuming you can handle the drop in refresh.

By doing this, it seems to allow the game to render at the right resolution with minimal blurriness. I found it to be a huge improvement and was actually playable. Depending on your GPU, you can push the settings to as high as your rig will allow - VR Medium is a good benchmark to aim for, but even VR Low looks good enough.

One can hope that Codemasters will fix this for 24... but I know.. you know...Everybody knows.... Not a chance.

Anyway, give this a go, you might be surprised how good it actually looks.

* 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.

Users are confirming DLSS and FSR are DECREASING performance - so be sure you are only using TAA - even for pancake mode. I presume Codies will fix this in a patch.

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!

Last edited by Is It?; 11 Mar, 2024 @ 11:18am

< >

Showing 1-15 of 40 comments

Interl@ce 13 Jun, 2023 @ 5:18pm

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 also still appear present I'm expecting this to be a lingering issue many people aren't aware of as well.

Last edited by Interl@ce; 13 Jun, 2023 @ 5:19pm

Is It? 13 Jun, 2023 @ 5:21pm

Originally posted by 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.

These issues seem to 'go away' once the GPU isn't hitting the render time limit, which is 13.9ms, and this does seem directly linked to the refresh/resolution. Which is logical of course, but F1 22/23 seem to be exceptionally sensitive to this.

90Hz would be ideal, but I have never found a usable render res that allows this to work properly.

mango

13 Jun, 2023 @ 10:08pm

thank you I will give this a try VR is boss..lol but the jitter is a pain

TheSlurpeeGuru has F1® 23

15 Jun, 2023 @ 4:14pm

Thank you!!

Web Browser has F1® 23

15 Jun, 2023 @ 7:34pm

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

Is It? 16 Jun, 2023 @ 2:20am

Originally posted by 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?

Adrián

16 Jun, 2023 @ 3:19am

I'm having an issue where every time I start a race, DLSS is turned back on, sort of. It is not showing as enabled, but once I put DLSS back on, it looks the same, then I turn it back off and then it's actually turned off. Not sure if there is any fix for this bug, it's annoying as hell.

Darkangle 16 Jun, 2023 @ 3:49am

Originally posted by 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!

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? 16 Jun, 2023 @ 6:34am

Originally posted by 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.

Ahaha I didn't notice that :D And yes.. apparently it didn't help!

Ripjaw-The Great. has F1® 23

16 Jun, 2023 @ 6:40am

shimmering sheeeite is what it is

#10

Web Browser has F1® 23

16 Jun, 2023 @ 9:31am

Originally posted by Is It?:
Originally posted by 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?

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!

#11

Is It? 16 Jun, 2023 @ 11:28am

Originally posted by Web Browser:
Originally posted by 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!

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.

#12

Dyskord

16 Jun, 2023 @ 11:47am

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.

Last edited by Dyskord; 16 Jun, 2023 @ 11:48am

#13

Is It? 16 Jun, 2023 @ 11:56am

Originally posted by 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.

Glad it helped. I'm also grateful for the feedback regarding SER - I suspected this would be helpful, so I'll edit the guide to mention that.

Clearly the higher the GPU the higher SteamVR Res can go - I am now suspecting this is a GPU video buffer issue. Stands to reason I guess. I'd be very interested to know how AMD GPU users are doing with VR. I also think 40 series cards can probably handle higher texture streaming, possibly due to RAM speeds.

Anyway, thanks for the feedback - have some points.

#14

Web Browser has F1® 23

16 Jun, 2023 @ 12:30pm

Originally posted by Is It?:
Originally posted by 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.

I'll try this when I have time and I'll get back to you. Thanks for the replies!

#15

< >

Showing 1-15 of 40 comments

Per page: 1530 50

F1® 23 > General Discussions > Topic Details

Date Posted: 13 Jun, 2023 @ 5:14pm

Posts: 40