Search Issue Tracker
Not Reproducible
Votes
2
Found in [Package]
1.0
Issue ID
1249047
Regression
No
[Input System] Oculus Touch Controllers on Oculus Quest not handled
See https://github.com/Unity-Technologies/InputSystem/issues/730
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
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
rowanwaring
Jul 21, 2020 21:34
I think I've ran into something similar, using a Rift S setup with two Oculus Touch Controllers, in 2020.1.0b15. The devices are visible in the Input Debugger and inputs and values respond accordingly (in play mode, otherwise they are considered disconnected) - however, no binding or path for actions respond, and I've tried generic XR Controller bindings, to the OpenVR options for Oculus Touch Controllers, to the basic OculusTouchController ones.
The issue mainly seems to be that the device doesn't successfully pair with PlayerInput, but despite a bunch of digging doesn't seem to allude to why...
PatrickBaroudRobocom
May 26, 2020 12:04
Any news on this issue?
I can't seem to get the thumbstick input from an Oculus Touch controller regardless of which path I use. Is it properly implemented?
<OpenVROculusTouchController>{LeftHand}/thumbstick
<OpenVROculusTouchController>{RightHand}/thumbstick
<OpenVROculusTouchController>/thumbstick
<OculusTouchController>{LeftHand}/thumbstick
<OculusTouchController>{RightHand}/thumbstick
<OculusTouchController>/thumbstick
These are all the options available from within the UI, none of which are returning any input.