Search Issue Tracker
Third Party Issue
Votes
0
Found in
2018.4
2019.4
2020.2.7f1
2020.3
2021.1
2021.2
Issue ID
1319883
Regression
No
[Mac] Input.GetAxis not resetting to 0 when no keys are pressed in the old Input Manager
The Unity Input "Horizontal" and "Vertical" Axes seem to get hung up or stuck when playing in editor in Unity 2020.2.6 and 2020.2.7.
Input Manager settings look completely normal to me, and this doesn't seem to affect WebGL builds; it just happens in Editor.
In Project Settings > Player, Active Input Handling is set to Input Manager (Old).
I do have several applications set up in the OS to allow Input Monitoring (pics included). Not sure if that affects it at all.
When I say this happens "Sometimes", it *never* happened before 2020.2.6, and now it happens several times per day.
2. How can we reproduce it using the example you attached
a. Open __Scene_0.
b. Press Play.
c. Use arrow keys to move the ship and hold space bar to shoot.
It only happens sometimes, and seems to only happen on macOS Catalina (10.15)
-
Martin-Kraus
Apr 22, 2022 05:46
I see the issue with Unity 2020.3.24f1 on macOS Monterey 12.3.1.
-
Stakk3r
Jun 21, 2021 08:26
This now happens to me on Big Sur 11.4 and Unity 2021.1.11f1.
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Resolution Note (2021.2.X):
This appears to be an issue most visible on macOS Catalina where macOS does not deliver the keyup event in a timely manner in cases where the message loop is delayed. The issue appears to be fixed in Big Sur. Though if anyone sees it in Big Sur, please let us know.