Search Issue Tracker
Fixed in 0.0.13-preview
Votes
0
Found in [Package]
0.0.9-preview
Issue ID
1093787
Regression
No
[XR] OpenVR 2D axis issues
Migrated bug from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/249
Editor 2018.3.0b2
Package 0.0.7-preview
Steps to reproduce:
Git the InputSystem test project https://gitlab.internal.unity3d.com/xr/manualtests/input-system. Specifically grab the 2018.3 branch
Set the OpenVR SDK, and hook up a Vive or Oculus.
Run the scene ViveWandActions
Expected:
All actions are triggered correctly
Observed:
The touchpad InputActions are not triggered.
In the InputDebugger, primary2DAxis and secondary2DAxis now appear as well as the trackpad 2DAxis. The trackpad seems to drive primary2DAxis
jackpr-unity commented on Sep 18
Oculus has a similar issue. I am changing the name to reflect that.
For Oculus, the joystick control shows up in the InputDebugger, but again it is primary2DAxis that is changed.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Text is unreadable when DLSS is applied to the Canvas with Render Mode set to World Space
- NullReferenceException errors appear in the Console when changing the values of Visual Effect Control Clip Events' Attributes
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
Add comment