Search Issue Tracker
By Design
Votes
0
Found in [Package]
0.2.0-preview
Issue ID
1134062
Regression
No
[Controller] Unwanted Deadzone when calling `gamepad.stick.x.ReadUnprocessedValue()`
Github Bug: https://github.com/Unity-Technologies/InputSystem/issues/299
Repro:
1. Download attached project: StickValue.zip
2. Download ISX package: https://github.com/Unity-Technologies/InputSystem if needed
3. Run the project in Editor or Player
4. Press Ctrl + i or click the Info menu on the right side
5. Observe the difference between ReadValue() and ReadUnprocessedValue() for stick movement (yellow text = unprocessed)
Actual: ReadUnprocessedValue has a build-in deadzone of 0.15
Expected: No deadzone for ReadUnprocessedValue.
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
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
Resolution Note:
This is by design. Devices by hardware usually don't exactly center on zero. Compensating for this is the purpose of deadzone processing.