Forum Discussion
shoveltools
9 years agoHonored Guest
Potential 1.12 Double Render Tracking Errors for Rift
I got a "required update" from the Oculus app just now.
I was testing our experience off the alpha channel. The update notification popped up and I clicked update. Oculus app rebooted and I saw the version being used in the screenshot below.
It felt when I "teleported", ( moved position in 3D space ) there was a frame overlaying in a stuck state mixed with a frame that was being tracked. So double rendering with a dirty frame. I am the most sensitive to VR and this was insta nauseous for me, Especially when I took off the headset.
The above never happens before the 1.12 update. I hope this info helps.
We are using Multi-pass rendering and Unity 5.5.0p3 for our settings. Same alpha build was tested before and after this update with the same hardware. Two sensors, two Touches. Rift.
Thanks,
Matthew
I was testing our experience off the alpha channel. The update notification popped up and I clicked update. Oculus app rebooted and I saw the version being used in the screenshot below.
It felt when I "teleported", ( moved position in 3D space ) there was a frame overlaying in a stuck state mixed with a frame that was being tracked. So double rendering with a dirty frame. I am the most sensitive to VR and this was insta nauseous for me, Especially when I took off the headset.
The above never happens before the 1.12 update. I hope this info helps.
We are using Multi-pass rendering and Unity 5.5.0p3 for our settings. Same alpha build was tested before and after this update with the same hardware. Two sensors, two Touches. Rift.
Thanks,
Matthew
2 Replies
Replies have been turned off for this discussion
- george_papagianHonored Guestwe also have the same problem which is particularly evident in VR-ready laptops, it seems that no-one is testing on these @oculus. Please do provide us with an update as soon as possible.
- AnonymousDescription
Today's Oculus Runtime Update has now totally ruined the game. It now stutters every second even when using hotkeys to DISABLE ASW which worked 100% smooth previously in v1.11 and previously we even heard a Sound Confirmation when we switched these Modes but there is none now. I know it still switches as I can see a difference from CTRL&Numpad1 when compared with auto CTRL&Numpad4. I do know for a fact this is NOT reverting back to the original game mode.
This is SEVERE AND SORRY FD - I CAN NOT PLAY ELITE:DANGEROUS ANYMORE until fixed as before. It isn't even you problem but is that of OCULUS for altering this. I also read other users have issues with other games.
Steps to Reproduce
Rebooted - all I will try next is to swap over the USB sockets to rebalance them. This has worked for 1 user.
Oculus - We need a definite way to remove ASW and ASAP!!!
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 12 days ago
- 2 years ago
- 6 days ago