Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
0.2.1-preview
Issue ID
1139056
Regression
No
[XR] Oculus Go controller device is missing
moved from https://github.com/Unity-Technologies/InputSystem/issues/211
Steps to reproduce
- Editor 2019.1.0b8
- Project: https://github.com/Unity-Technologies/InputSystem
- Scene: Assets/QA/Tests/XRDeviceActions/GearVR/GearVRActions.unity
- look at a public action on one of the ButtonControlActionStatus (such as on the gameobject Canvas->HeadsetTracking->ControlStatus->Button(isTracked))
- Create an action, double click on it, explore path->specific devices
Expected
GearVR HMD, GearVRController, Oculus Go HMD, and Oculus Go Controller all exist
Observed
There is no Oculus Go Controller. Although we know that GearVR and Oculus Go are interchangeable, a user probably doesn't.
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
- Crash on memcpy when opening a project that loads TSS files
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
Resolution Note:
Oculus Go is deprecated. We will not be fixing this issue.