Search Issue Tracker
Fixed in 1.1.0-preview.2
Votes
0
Found in [Package]
0.9.0-preview, 1.0.0-preview.5
Issue ID
1223436
Regression
No
Value equal to 1 is not returned by the Input System when reading a multi-bit control
How to reproduce:
1. Open the attached project
2. In the Test Runner, run all tests
3. Inspect the test results
Expected result: All tests succeded
Actual result: Tests for reading the input values failed
Reproducible with: , 2019.3.4f1, 2020.1.0a26, 2020.2.0a1 (0.9.0-preview, 1.0.0-preview.5)
Couldn't test with Unity: 2017.4.37f1 (Package Manager does not exist), 2018.4.18f1 (Internal Package errors)
Could not test with Packages: 0.1.2-preview, 0.2.10-preview (Internal errors)
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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Resolution Note (fix version 1.1.0-preview.2):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1219
Fixed package available in Unity 2019.4.0f1 and above