Search Issue Tracker
Fixed in 0.0.13-preview
Votes
0
Found in [Package]
0.0.9-preview
Issue ID
1091936
Regression
No
[XR] Oculus SDK + Oculus Rift primary and secondary button touch states are inconsistent
Migrated bug from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/206
Touching Primary and Secondary buttons on Oculus remotes do not register touch in HUD but register in debugger.
Touch yellow appears to flicker at random times in HUD but is not consistent with touching the buttons
jackpr-unity commented 29 days ago
Still exists in 2018.3.0b2 and package version 0.0.7-preview
InputDebugger:
xtouched and ytouched, the inputs which shouldn't exist, are driven correctly. PrimaryTouched and SecondaryTouched are not driven
InputActions:
InputActions bound to primaryTouched and secondaryTouched do not fire.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment