Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
1.1.0-pre.5
Issue ID
1336240
Regression
No
InputTestFixture tests return inverted values when pressing Gamepad's left or down joystick buttons
Reproduction steps:
1. Open the attached project ("case_1336240.zip")
2. Open the Test Runner: Window > General > Test Runner
3. In the Test Runner window select "PlayMode"
4. Click the "Run All" button to run all tests
Expected result: When pressing GamePad's "leftStick.left" button, the test returns "Left Stick/Left pressed"
Actual result: When pressing GamePad's "leftStick.left" button, the test returns inverted value: "Left Stick/Right pressed"
Reproducible with: 1.0.2, 1.1.0-preview.3, 1.1.0-pre.5 (2019.4.28f1, 2020.3.11f1), 1.1.0-pre.5 (2021.1.10f1, 2021.2.0a19)
Couldn't test with: 2018.4 (Input System is not available)
Note:
-Issue is reproducible when pressing "leftStick.down", "rightStick.left", "rightStick.down" buttons as well.
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
- No data received in Profiler when connecting to WebGL Player without "Autoconnect Profiler" option enabled
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
- Crash on AMDUnityPlugin.DLL in specific built project when using FSR2 upscaler
- RenderObjects does not have any Depth texture bound when Event is set to AfterRenderingPostProcessing
Resolution Note (fix version 1.3.0):
Fixed in Input System 1.3.0 available in 2019.4 and above