Forums » Bugs
VR Calibration starts clipping repeatedly
Using HD Daydream version on Pixel 2 XL, Android 8.1
I find that, the last 3 playthroughs in VR, the display will constantly shift back and forth after about 8 minutes, as if the program can't tell where the calibrated viewing center for each eye is. I have medium details on, and can usually get another 8 minutes in after a reboot.
Let me just say also that this game is phenomenal, and I really hope that your effort to bring PC/mobile, and VR together will pay off big for you guys. I've gladly ponied up a premium year's sub, hope there is more content I could maybe buy to help along. Keep up the groundbreaking work!
I find that, the last 3 playthroughs in VR, the display will constantly shift back and forth after about 8 minutes, as if the program can't tell where the calibrated viewing center for each eye is. I have medium details on, and can usually get another 8 minutes in after a reboot.
Let me just say also that this game is phenomenal, and I really hope that your effort to bring PC/mobile, and VR together will pay off big for you guys. I've gladly ponied up a premium year's sub, hope there is more content I could maybe buy to help along. Keep up the groundbreaking work!
Glad you like it!
We have seen some challenges on some VR devices, particularly on Daydream. Of the two mobile-VR versions (Daydream and GearVR), I'd have to say Daydream is a bit more prone to weird problems. It used to have the most terrible drift, although that's been improved a bit.
Most of the issues we've seen have been on the "API" side, basically aspects of Google's code, or the device hardware, not working quite as intended. But we'll definitely take a look as soon as we can.
We have seen some challenges on some VR devices, particularly on Daydream. Of the two mobile-VR versions (Daydream and GearVR), I'd have to say Daydream is a bit more prone to weird problems. It used to have the most terrible drift, although that's been improved a bit.
Most of the issues we've seen have been on the "API" side, basically aspects of Google's code, or the device hardware, not working quite as intended. But we'll definitely take a look as soon as we can.