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)
Community ManagerHey everyone,
Thanks for sharing your details on this.
I'd like to gather some additional info so we can pass this on to the team. Please reply with the following info when you have the chance:
- With which headset(s) have you experienced the movement delay?
- What is your current game version (you can see this at the bottom left of the Start screen)?
If possible, can you also attach a DxDiag to this thread? For more info on how to pull one up check out the EA Help website. Please attach the full text file here.
Thank you!
EA_Kent, my guess is your going to find the issues are with the Quest2 or even older headsets. I have tried both Reverb2 and Quest2. The Quest2 was unplayable but Reverb 2 was awesome fun. Quest2 just isnt made for this stuff. People want a buttery smooth experience using the quest2 which is meant as a self contained device meant to play beatoffsaber or whatever low graphics, low quality game they play.
Yea, I am little perturbed, I held off on this because of the complaining here and I almost missed out and its as good if not better then PC2 in VR This is such a big issue when making VR games, so many variables, so many people with garbage hardware want to complain. I am having a good time in VR.
If I were EA I would say Quest2 or any other junk facebook headset need not apply.
Possibly an issue with Oculus CV1, could be a setting, but hardly noticeable. Much better/stable framerate and framtetime, but a much lower quality display.
Primary issue with the headset HP Reverb G2 v1 (I haven't had any cable issues, so I found replacing the it with a v2 cable a lower priority)
Currently Using F1 22 Game Version 01.11.918016
Using the HP Reverb G2 with the recommended 2240x2188 @90 (although I have tried hundreds of different combinations in the attempt to make this work with F1 22)
Getting Average 61fps with Average frametime of 16.39 using lowest VR setting of Ultra-low (the frametime number has gotten worse with each F1 22 update)
If I hold my head still it looks great, but when I move it side to side or up/down, there's a Delay/Latency (for lack of better term) in the headset visuals.
My best way to describe it would be if the headset display went on pause and then un-paused for a split second repeatably as you move the headset in any direction.
F1 22 is impossible to play with my vr headset, and can only be experienced in very small doses while testing without getting ill.
dxdiag.txt attachment included.
I also have issues on the rift S regarding the "jittering" or "delay".
I've tested it on my Oculus CV1, Reverb G2 and Quest 2. All headsets have a delay in head movement but the amount of delay varies per headset and also which runtime you use, I have tried the following combinations:
CV1 with SteamVR
CV1 with OpenComposite
G2 with SteamVR
G2 with OpenComposite
Q2 with Virtual Desktop
Q2 with SteamVR
Q2 with OpenComposite
All of the above show some form of head movement delay compared to every other VR game in existence. Frametimes are fine, there is only tiny dips in frametime when moving your head.
Specs:
12700K
RTX 3070
WIN 10
Not sure about EA, but, of course, everyone at Codemasters knows the head tracking is broken. It is broken on every headset. For whatever reason, the 3rd party that did the VR implementation will not or cannot fix it. That's where we are at.
I just wish EA Kent would do the one thing I need him to do, which is to tell me how to get a refund, so I'm not held hostage by this game anymore. Steam won't give me a refund because I spent 7 hours the first couple of days trying every conceivable setting change to fix the head tracking and the horrific AA options they decided to use.
I opened a case here at EA and they said they would let the team know. Yay.....worthless. Just give me a refund.
I have spent hours after hours testing and I have it now "cross fingers" a nice fun time in VR. Between no mouse support, having to get use to using buttons to get around the menu, figuring out steam VR resolution and all the darn settings in game, this is not plug in play. EA did do some nice things in VR, gave some good settings, gave personal options its a shame there is a fatal flaw. The most important thing I found, hope it helps some.
1- The framerate can not dip below the hz you have set on your VR headset. If it dips 6 or 7 frames much less 15 or more below your hz setting you get that jerky movement even if your running at 72 fps if your hz is set say on 90hz.
2- So what does that mean, your probably going to have to set your headset at 60hz or 72hz and run on mostly low settings. If your a high fps person or have to have better clarity you are out of luck in VR on f122 the way it is implemented now.
Conclusion: Something in the way EA has implemented VR does not allow it to handle drops in frames compared to the hz settings in the headset. Its always been somewhat important but in F122 you just get the over the top jerkyness compared to other games. The issue is most of us just dont have hardware that allow a constant 90 fps or more in a racing game that would allow us to set our headsets to use the 90hz or higher.
EA if you care this is where you need to start investigating why you have such an issue here where PC2 or MFS does not.
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.
Community ManagerThank you everyone! I appreciate the info.
@nangu22 Bingo. Codemasters already know about it because it would be impossible to not know about it. They developed the game. Now, maybe they are waiting for the 3rd party to fix it, or maybe it can't be fixed, which they would never tell us...but maybe we are getting the answer by the radio silence itself. Which is fine--just give me a refund since the VR feature is un-functional and that is a promised feature.
Luckily I was able to use the 10 hour free trial with Xbox Game Pass. I used 7 hours of that to test all the patches up till 1.10 and none of them really changed the head tracking.
Again to chime in with the earlier posters this issue has nothing to do with performance or not hitting the required frame rates as I am locked at the refresh rate of my HMD it's just the head tracking does not behave like basically every other VR game in existence, it lags behind the actual head movement.
For me the best combination so far has been using OpenComposite on my CV1 but that does not FIX the issue as it is still lagging behind.
@57c8f68321dc240fI meant to say that my framerate is locked at the refresh rate of my HMD. So my FPS is not fluctuating below the refresh rate of the HMD.
CV1 is at 90hz
Q2 is at 80hz
G2 is at 90hz
3090ti and 12900K
I was hoping that this VR issue would be resolved over the summer break. Unfortunately, it has gotten even worse. Before you had the opportunity to lower the details. Since it was halfway, that you could drive something. Now that doesn't work either.
Did 1.12 do anything for this issue?
Ofcourse not ☹️
EA, please fix this! It's so bad and why are you not doing anything to fix this problem? So frustrating that EA does not give a single F about it's customers. Just bring in the money and screw everybody...
1.15 any better? so glad I didn't buy this game and only used the trial from game pass.
