Search Issue Tracker
Fixed in 1.4.0
Votes
0
Found in [Package]
1.1.0-preview.2
Issue ID
1293728
Regression
No
[Input System] Normalized input returns incorrect value when the Input is below Deadzone minimum
Description:
The user wants to Normalize the controller's Left analog stick X-Axis input values in the range [0 .. 1], 0.50 being the new middle.
Reproduction steps:
1. Open the user's attached "BugInputSystemNormalize" project
2. Open Assets/TestScene
3. Enter Play Mode
4. Observe the "Normalized value" in the Game View window
Expected result: The Normalized value is 0.50 when the Left Analog Stick input in the X-Axis is below the Deadzone minimum
Actual result: The Normalized value is 0.00, snaps to somewhere around 0.50 when Left Analog Stick input in the X-Axis is above the Deadzone minimum
Reproduces on: 1.0.1 (2019.4.15f1), 1.1.0-preview.1 (2020.1.15f1), 1.1.0-preview.2 (2020.2.0b13, 2021.1.0a7)
Can't test: 2018.4 (can't successfully import the project)
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
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
Resolution Note (fix version 1.4.0):
Fixed in: 1.4.1