Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.1.X, 2021.2.X
Votes
0
Found in
2021.1.0a1
2021.1.6f1
2021.2
Issue ID
1336005
Regression
Yes
[WebGL][Input System] Vertical axis input is inverted when using a game controller
Reproduction steps:
1. Open the user's attached "hqf-maze.zip" project
2. Load the "SampleScene"
3. Enter the Play Mode
4. Move the Sphere around with the controller's Left Stick
5. Observe the movement on the vertical axis
6. Exit Play mode and make sure the WebGL platform is selected in the Build Settings
7. Build and Run the project
8. Move the Sphere around with the controller's Left Stick
9. Observe the movement on the vertical axis
Expected result: Sphere moves in the direction of the Left Stick input
Actual result: Left Stick input is inverted on the vertical axis
Reproducible with: 2021.1.0a1, 2021.1.11f1, 2021.2.0a21 (1.1.0-preview.3, 1.0.2)
Not reproducible with: 2020.3.12f1 (1.0.0-preview.1, 1.0.2)
Could not test with 2018.4 (Input System Package is not available), 2019.4 (the project uses C# 8.0 syntax that is only available in 2020.2 and above)
Tested with:
- Xbox One Controller
Comments (1)
-
Partycrow
Dec 06, 2023 16:04
I dont know what you fixed, but I run 2022.3 and its inverted, still...
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
- "GetPreferedValue" returns max value when using auto-sizing
- UI Builder doesn't update the style sheet when using "Extract inline style" right-click option
- “Assertion failed on expression” errors thrown when undoing Nodes creation with keyboard shortcut
- Crash on various stack traces when using Texture2D.CreateExternalTexture() while rendering
- Clicking on section text in Node Library > Context folder throws NullReferenceException errors
Resolution Note (fix version 2022.1):
The gamepad Y axis is now consistent with the editor and other players.
Resolution Note (fix version 2021.2):
Fixed WebGL gamepad stick Y axis being inverted. Fixed in: 2021.2.0b6
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.18f1