Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.2.18f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1130127
Regression
No
One Input axis does not work after using Input.ResetInputAxes() while both axes are held down
How to reproduce:
1. Open the attached "case_1130127-ResetInputAxesBug" project
2. Open scene "SampleScene" and enter Play mode
3. Hold down first the "W" and the "D" buttons on the keyboard (must be done in different frames)
4. Without letting go of the keyboard buttons, press the "Input.ResetInputAxes()" button in the Game window
Expected results: Both axes are set to 0 for one frame and rise back up to 1
Actual results: Only the horizontal axis rises back up to 1 even though the "W" button is still held
Reproducible with: 2017.4.21f1, 2018.3.7f1, 2019.1.0b4, 2019.2.0a6
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Unfortunately with the move to the new input system, we are deprecating the old input system and will not be developing the old input system code. The new input system package and documentation can be found in the package manager in the Unity editor or directly at https://github.com/Unity-Technologies/InputSystem. If this specific issue can also be reproduced using the new input system, bugs can be filed at https://github.com/Unity-Technologies/InputSystem/issues.