Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1305789
Regression
No
[XR][Input System] Left hand XR controller's primary2DAxis is ignored when using PlayerInput script
Reproduction steps:
1. Open the user's attached "InputSystemWithOpenXR.zip" project
2. Load the "SampleScene"
3. Enter Play mode
4. Use the right hand XR controller's thumbstick to control the player
5. Note that the player moves according to the thumbstick
6. Use the left hand XR controller's thumbstick to control the player
Expected result: the player is moving according to the left hand XR controller's thumbstick
Actual result: the player is not moving
Reproducible with: Input System 1.0.2, 1.1.0-preview.3 (2019.4.19f1, 2020.2.4f1, 2021.1.0b5, 2021.2.0a4)
Could not test with 2018.4 due to multiple compilation errors after downgrading the project
Note: reproduced with Oculus XR and OpenXR plug-ins
Tested with:
- Oculus Rift Touch controllers
Comments (1)
-
JDatUnity
Feb 26, 2024 09:18
Was able to reproduce this in 2021.3.15f1, just wasted 2 hours of my time because of it. I urge the Unity team to look at this sooner than later, as all other input works fine, except for the Primary2DAxis
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.