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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment