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
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
- Graphics Compositor breaks Unity rendering when the "Output Camera" is changed to a scene Camera and one Camera SubLayer is active
- The Editor freezes on RenderGraphViewer.Repaint when entering too many characters in search fields without character limits
- Adding a new SubLayer in Graphics Compositor renders BaseLayer darker and makes it flicker
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.