I have Virtual Desktop but not tired it for F1 22. What I don’t get is why this would be better then using oculus Link which is hardwired to your PC. Virtual Desktop uses WiFi so surely the success of this solution is based on how good your home WIFi set up is?
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 (WORST performer)
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 (Still crashes but much better performance than the oculus runtime)
This is very interesting, the frame drops are rare and only to 87fps with much less 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 (Optimal)
Using the High "VR Graphics Quality" in the Virtual desktop settings produced an Ultra smooth experience (so how 10ms lower app latency than the link cable) 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 (CLOSE Second)
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
Thanks to everyone for all their hard work and hours of investigation - apologies but that's why my brain seems to go ouch when trying to carry out this depth of analysis. So as I'm typing F1 22 is downloading from Steam and I'll start with "Virtual Desktop plus Oculus Runtime" - as fulcon arrow says why on earth a wireless connection is better than a cable connection is beyond me - however I have always wondered if a USB 3 compressed -> uncompression was a good idea for Quest - why not use a Display Port 1.4? Is it possible to buy a RTX 3080 with a direct usb 3 output - doubt it!!
Thx again to everyone I'm most grateful
