Search Issue Tracker
Fixed in 0.10.0
Votes
0
Found in [Package]
2019.3
2020.1
2020.1.0a17
Issue ID
1208341
Regression
No
[XR Interaction Toolkit][Oculus Go] ControllerManager errors on only one controller being active
Repro steps:
1. Open attached project
2. Build and Run on Oculus Go
3. Observe the logcat and the game view
Actual: One controller is floating between the eyes and errors thrown in the logcat
Reproducible with: 2019.3.2f1, 2020.1.0a23
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on MeshRenderer::DispatchUpdate when disabling the second Mesh Renderer on a GameObject
- Inaccurate collisions when resizing Game view
- Animator Controller Layer name stays unchanged in Layers tab when renamed from Inspector
- [RenderingDebugger]Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
Resolution Note (fix version 0.10.0):
This is fixed in an upcoming version of the xr interaction toolkit. It will be a new input system only fix and we'll be deprecating the original controller manager.