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
- Value discrepancy between LateUpdate and OnAnimatorIK when state transition occurs
- Keyword space mismatch error is constantly appearing in the Editor Console window when shaders contain compilation errors
- Inspector Window Tag Search Bar is not populated with the copy-pasted text when using CTRL+V to paste a tag name
- CompilationPipeline.assemblyCompilationFinished is not invoked when using RequestScriptCompilationOptions.CleanBuildCache
- Error “A renderer material mask can't store more than 128 materials.“ is present when the GPU Resident Drawer is disabled
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.