Product: F1 22Platform:PCSummarize your bug There is a delay in the image / camera when moving your head in VR. Image is not updated correctly in relation to the headset position.What is your 16 digit Report Code? VCBJ-HJMT-RCBB-DEKEWhich area is the bug/glitch in? Driver CareerHow often does the bug occur? Every time (100%)Did you have cross-play enabled? NoSteps: How can we find the bug ourselves? Drive any car on any track using a VR headset / Valve Index. Move your head and witness the delay in the image / camera.What happens when the bug occurs? A delay in the image when moving your head in VR.What do you expect to see? A 1:1 updated image based on the position of the head.When moving your head in-game, the expected image related to the positon of the head is delayed. Any drop in frame rate exacerbates the latency experienced, but overall the delay is not improved even when consistently hitting the headsets refresh rate. This comes across quite like an artificial smoothing technique, like 'mouse smoothing' for instance. Creates a lot of nausea even for someone like me who's very used to VR after many years of using it. Without question, any new players are certainly going to be put off using VR.

@dertysin No, we're not talking about jittering. This bug report is specifically about head-tracking delay. Jittering is a separate problem and there are other threads out there talking about that. The word 'lag' is getting misused a lot and the head tracking delay issue is getting clouded over by those who are confusing lag and latency for frame time related issues. Although I do feel for you and others who are getting jittering, this is not the issue I'm trying to bring to light.

I didn't spend much time with the Rift CV1 and F1 22. I plugged it in to see if it was my headset (HP G2), workstation/GPU, or a software issue.The CV1 headset worked much better that the G2, but still had a minor delay. It was nearly unnoticeable but I was specifically looking for it. I might have been able to tune it out.I have used the CV1 for many hours with other driving SIMs without any issue other than minor tweaks. The same for my HP G2, no major issues other than minor tweaks until F1 22.I have spend many many hours trying to get the HP G2 to work "reasonably" with F1 22, but have failed so far. The best I can get is around 55fps with minor head movement delay (around 0.8 SS @custom VR Rez). Totally unusable for any length of time.I can't image the frustration of having a headset capable of 144Hz and trying to get it to work on F1 22 (without having a RTX3090Ti @medium Rez)

@rockman834 That's very interesting, although I'm not sure what you mean when you say you could 'tune it out'. Are we both talking about the same thing here (head tracking delay) or are you referring to poor FPS? Because a lot of people are confusing the two things. I could be wrong here, but I felt that running my Index at 120hz seemed to improve the perceived latency for me. Almost like the latency is tied to the refresh rate which cetainly isn't beyong the realms of possibility. I could also be a placebo effect, obviously.

I have a monster computer. The problem is the head tracking, not jerkiness or jittering, or stuttering. I have 90 hz easily, 5 gig cpu, 3080ti oc, etc with valve index. The head tracking is broken. That is the problem. It’s also the blurriest vr racing game on the market, that’s another problem. And many objects in game are not rendered properly in 3d. That’s another problem. But the main problem of out of sync head tracking makes the game unplayable, so the other stuff doesn’t even matter.

This has been an issue since release and still not acknowledged yet.

VR Head Tracking not 1:1 - Delay / Latency when moving head

34 Replies

furfoots
3 years ago
This has been an issue since release and still not acknowledged yet.
SW0RDF15H
3 years ago
Do we know if it's the same on all VR headsets? A few weeks ago, I had a 5 minute blast on my nephew's Oculus CV1 on F1 22 and didn't notice any delay in head tracking. I guess there's a small chance that I didn't notice because I wasn't looking for it, but frankly, it was the first thing I noticed when I booted up my Valve Index. It was so obvious and actually took me a while to work out what I was experiencing that was making me want to throw up so badly.
Anyone with an Oculus or other non-SteamVR headset can attest to this being the case?
dertysin
3 years ago
It's jittering a lot for me as well.
Can't play the game properly if it feels like you're racing in an earthquake!
This needs to be top priority for the devs to fix, because it's ridiculous that this is even an issue.
SEXY-L0U
3 years ago
@dertysin No, we're not talking about jittering. This bug report is specifically about head-tracking delay. Jittering is a separate problem and there are other threads out there talking about that. The word 'lag' is getting misused a lot and the head tracking delay issue is getting clouded over by those who are confusing lag and latency for frame time related issues. Although I do feel for you and others who are getting jittering, this is not the issue I'm trying to bring to light.
furfoots
3 years ago
This issue is irrelevant of your setup it the same on all PCs. I have it on my RX5700 with Intel I5 on CV1 and on my RTX 3070 with Intel I7 on my Quest 2. Whether you're annoyed by it is a separate discussion 🙂
SW0RDF15H
3 years ago
Anybody tried any other headsets with the game and noticed this issue?
rockman834
3 years ago
I have the same issue with a HP Reverb G2 running on a RTX3060ti
On my Oculus CV1 is a lot less noticeable, but the resolution is about 1/4 of the Reverb
SW0RDF15H
3 years ago
@rockman834 Would you say that there is a delay in head movement on the CV1 then? I only tried the CV1 briefly while I had access to it but didn't notice any delay. If there was, I'm surprised I didn't notice it as it's extremely obvious on my Index
rockman834
3 years ago
I didn't spend much time with the Rift CV1 and F1 22. I plugged it in to see if it was my headset (HP G2), workstation/GPU, or a software issue.
The CV1 headset worked much better that the G2, but still had a minor delay. It was nearly unnoticeable but I was specifically looking for it. I might have been able to tune it out.
I have used the CV1 for many hours with other driving SIMs without any issue other than minor tweaks. The same for my HP G2, no major issues other than minor tweaks until F1 22.
I have spend many many hours trying to get the HP G2 to work "reasonably" with F1 22, but have failed so far. The best I can get is around 55fps with minor head movement delay (around 0.8 SS @custom VR Rez). Totally unusable for any length of time.
I can't image the frustration of having a headset capable of 144Hz and trying to get it to work on F1 22 (without having a RTX3090Ti @medium Rez)
SW0RDF15H
3 years ago
@rockman834 That's very interesting, although I'm not sure what you mean when you say you could 'tune it out'. Are we both talking about the same thing here (head tracking delay) or are you referring to poor FPS? Because a lot of people are confusing the two things. I could be wrong here, but I felt that running my Index at 120hz seemed to improve the perceived latency for me. Almost like the latency is tied to the refresh rate which cetainly isn't beyong the realms of possibility. I could also be a placebo effect, obviously.