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
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
Resolution Note (fix version 1.4.0):
Fixed in: 1.4.1