Hi @HamVR thanks for your comment. The performance as measured by FPS is fine, the problem is with regards to jittering as widely reported in this thread. As mentioned it does seem to be better when keeping FPS above headset refresh rate, but I have never seen any other VR game that goes haywire like this when you drop below the refresh rate - In Microsoft Flight Simulator I actually cap my FPS well below the refresh rate.
With regards to the FOV/motion problem I mentioned, I spent several hours messing with steam settings including FOV to try to cure it without success. I have been able to get all my other steam VR games (including MSFS, Automobilista 2, Half Life Alyx, VTOL) working brilliantly. But if you are saying you find the VR tracking/motion in F1 to the same as in other PC VR games then that gives me some confidence and will try again... (I was wary about trying again until an official fix was announced, as I've already used up 5 hours of my 10 hour trial just trying to fix it!)
@Hairy_Bones2Hi yes I've played this on two different PC setups and 3 different headsets. I've also played online with 4 other friends, all in VR (all on Windows 10 FWIW), so it definitely does work in VR, but clearly for some people they are experiencing problems, but that's the nature of PC gaming with so many different hardware/software setups.
Regarding Epic launcher, my friend running 3080Ti and 12900k could run all VR games no problem but F1 22 in VR ran badly until he turned off Epic launcher. So some software (potentially ones that scan memory) can cause issues so look out for apps/services that could be doing that.
Regarding FOV stick to using Oculus Debug's FOV-Tangent Multiplier and avoid altering the SteamVR FOV scale. That said, on a 3090 and Quest 2 you shouldn't need to alter the FOV at all and run the Quest 2 at max resolution at the right graphics preset (VR Medium with streaming on ultra low) at 72Hz
In regards to your other SteamVR game that work, are they all running in SteamVR mode or Oculus Mode from the launcher? Would be good to double check SteamVR games in SteamVR mode run OK via Quest 2
Many of the jitters were related the performance issues in the pit garage and starting grid but that seems to been cleared up since the v1.06 release on Monday.
It’s also worth checking the hardware_settings_config_vr.xml (found in Documents\My Games\F1 22\Hardwaresettings) I’ve got vsync=”false” and framerate limit value set to the headset refresh. I run the game in windowed mode with 2D screen companion resolution turned down low. You can always delete this file, the game will auto generate a new one if you forget the settings.
If there are still jitters after trying the above in v1.06 I would look at clearing the Oculus Guardian and redrawing it fresh. Look out for reflective objects in your play area, clean the tracking cameras and potentially re-install SteamVR again (not the games though).
Thanks, interesting to hear that you have no issues with 3 different headsets.
Re launcher I have tried from the .exe directly or from the Origin app. Yes, I confirm all my other games use the SteamVR runtime.
There is definitely no issue with objects in my play area or cameras, as I swap straight from Automobilista or MSFS into F1 and consistently have no problems in the other games and the same problems in F1.
I think FOV was a bad choice of term from me - to clarify I am not talking about changing the Oculus Debug FOV (indeed I run at 100% in Link or via Virtual Desktop which is my preference), it was more my attempt to describe the strange camera movement I perceive on head turn. It gives me an almost small Dolly Zoom effect (eg https://www.youtube.com/watch?v=_OO3pqJVLAc&ab_channel=MKArtStudio) which led me to question whether there was an incorrect IPD, FOV or Zoom setting in the game. This evening I will again reset my Steam settings and confirm no change to Steam FOV.
In my testing I did also play with the xml including the 2 lines you mentioned, but will try again this evening and report back. Thanks for trying to assist !
