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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
Add comment