To be Fair, I gave it a try this morning, but it was before i increased the bit rate in debugger, i found it extremly irritating. Because the cockpit looked so small. But i think i decreased it to 70% may this is to much? But again the single most game changing setting was the bitrate. I Will give this for setting a try later and will share my expirience
70 maybe is too much, honestly i'm at 85% and i noticed it only on the screen, not inside the visor.
Below 80% you start to notice it
I will definitly give this a try later. All by all it is sad that a global publisher, on of the biggest, serve the vr mode without ayny optimization. AMS devs still close to a indy studio with maybe 1% of dev Power of ea/cm. Nowadays I think QA Departement of such Companies is the paying costumer and one community Manager hidden in the HQs Basement
To be fair, i utilize this "trick" in ACC too to reach 120 fps.
And in flight simulator to just make it playable lol
You know i still have to try AMS? I red everywhere vr it's really good but i'm sticked to acc lately and i never tried ams
and remember to do it in steam vr settings.
Oculus debug tool settings did nothing to me in f1 2022
I am new to vr, i actually only ordered a quest 2 for f1 22, had a psvr years ago, did some dirt 1 on ps4 maybe 10 hours all by all, when i ordered f1 in june and saw the vr previews i knew i must gave it a try, only did ams2 and it right out the Box performed well. This morning it was alle for the first time to play it for more than 2 laps, i ordered the ce i have around 20 hours game time with roughly 1 hour off track time the 19 hours are switch settings, check in benchmark Mode....
Yeah i know the per application video settings on steam vr
i fell you, settings everything correct in first games i played in vr was a real mess.
At Vive time we had to do all this settings via text editor :X
Now it's easier, but don't worry, you will get used to it, and when you will play and everything will work, it will be worthed
Ok so here are my results after way too many hours of testing on a 3080/5800x Ahah. As many people in the forums have mentioned that subtle jittering sensation when moving your head/looking left and right (dirt 2.0 all over again) is present but not as horrible as day 1.
Settings that won't change
Oculus software
Debug tool settings
F1 22 graphics - Running Medium preset
As @Grocs_Blech has mentioned, ambient occlusion must be off and in Video settings, game AA on - TAA as this seems to always render the best performance regarding jitters.
In F1 22, VR settings steam render res is staying at 100% and the bottom 3 settings (god rays, motion blur, and stencil) are all off.
I will not be attempting to use SSW or ASW as I've personally gotten too used to 90hz native playing Iraicng and assetto Corsa.
Our target is 90hz smooth gameplay which is achievable on all other popular sim racing titles 🙂
Link cable oculus runtime results (Best performer **if it stops crashing**)
I experience no real frame drops with the odd drop to 85 fps, this seems to be the most "jittering experience however the one with the most graphical fidelity.
Most importantly using the link cable seems to promote steam VR crashes in random instances (can't really isolate the reason), hence the need to search for other solutions.
Link cable Steam VR runtime results (Similar performance to oculus)
This is very interesting, the frame drops are rare and only to 87fps with more jitter, However, link cable still seems to cause crashes particularly as you change from different sessions
In order to use the steam, VR run time head to stream VR settings -> developer tab -> current run time click change to steam VR. HOWEVER you must boot STEAM VR before booting the game up in order for it to use the steam VR runtime, otherwise, it will revert to the oculus run time (regardless of what steam says) this was shown in the Virtual desktop performance overlay.
Virtual desktop Oculus runtime results (worse than link cable but doesn't crash)
Using the High "VR Graphics Quality" in the Virtual desktop settings produced a smooth experience with the same rare drops to 88 fps.
the jittering its the same as the LINK + Steam VR combo and miles better than the Link + oculus run time. the visual fidelity wasn't as crisp as the link cable.
Ultra quality in VD settings induced frame drops to 83 which increased jittering.
Virtual desktop Steam VR runtime results (not as clear as oculus run time)
Almost Identical results to the Oculus runtime, ever so slightly more frame drops (2-3%) but a little less Jitters.
All in all, this was the most painful experience and EA defiantly needs to fix the jittering and optimization of VR as a whole. Specifically, the random crashes using the link cable :/, once this happens it's going to be a great experience
@Grocs_Blech id love you to try the SteamVR runtime vs oculus runtime on VD and let me know what you think
this are mine, honestly i don't understand why you put so high resolution, the quest 2 resolution is 1920 x 1832 x eye, so everything more it's like put a 4k image on a 1080p tv.
It's true, with supersampling you will get better result expecially when you move the head around, but you put the resolution really too much high, it's a lot better experince at 120 fps and highest settings in game IMHO.
for some reason to get native res in quest 2, you have to run max render res (it's very odd) as I race Iracing and AC on this setting it's hard to go down as I lose so much clarity, but lower Clarity with better HZ and in-game settings is a fine choice! each to their own, so long as everyone gets a smooth experience that's what counts!
it's strange, in acc i notice difference only until 1.3 multipy (in oculus app, at 120 hz, cause 1.3 it's the standard oculus ress)
from 1.3 to 1.7 i don't see difference at all in clarity, i also tried with friends and we reached the conclusion that the very little difference we forced ourself to see, were only in our head, but yeah, i think you right and it change from people to people.
The settings that gave max graphics to me was just the 500 on the oculus debug tool, that settings improved the graphics a lot
well.... this is a mess in VR, I bought this on origin to avoid steam VR yet its being rammed down me throat like its rated R.
ok, frame times are just slowly increasing throughout a race to the point after 3 or 4 laps that its unplayable. GPU, CPU, RAM usage does not increase, so something funky is going on. fps was rock steady at 72, but the frame times slowly going out of whack just makes the game a stutterfest.
AO is off, but im a noob when it comes to steam VR and all its settings.
quest 2, rtx3090, i9 11900k, 32gb ram.......
MM69
i'm sry to hear that, it's really strange, your pc is really similar to mine, it should fly like mine.
How much res have you put in oculus app and in steam apps?
To reach so slow fps i have to crank the resolution, i can't think to others things that can keep you at so low fps.
Leave the resolution you have now on oculus app, open "steam vr settings", activate "advanced settings", go on "video", then there is an option like "choose for single apps" (i'm not sure about english translation), then you select f1 2022, put the resolution to 2000 x 2000 (+-) and put the second string to 85%
Try again the game and check fps
