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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment