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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
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.