Unity Issue Tracker - Input.GetAxisRaw doesn't always return to 0 when key is released

Duplicate

Votes

1

Found in

2019.4

2020.2

2020.2.2f1

2021.1

2021.2

Issue ID

1310167

Regression

Yes

Input.GetAxisRaw doesn't always return to 0 when key is released

MacOS

Jan 28, 2021

How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Select the "Main Camera" GameObject
3. Enter the Play Mode
4. Spam or hold "Horizontal" and "Vertical" Input keys (A, W, S, D)
5. Release the Input keys
6. Inspect the "Main" Script X and Y values
7. Repeat from the 4th step several times (5-10)

Expected result: Input.GetAxisRaw always returns to 0 when the key is released
Actual result: Input.GetAxisRaw sometimes doesn't return to 0

Reproducible with: 2019.4.20f1, 2020.2.4f1, 2021.1.0b6, 2021.2.0a4
Not reproducible with: 2018.4.31f1 (Tested the Input for 5 minutes)

Notes:
- Input.GetAxisRaw returns to 0 when moving the Mouse (When Input is stuck and not holding a key)
- Hard to reproduce with Unity 2019.4.20f1
- Easier to reproduce with later releases of Unity

This is a duplicate of issue #1319883

[Mac] Input.GetAxis not resetting to 0 when no keys are pressed in the old Input Manager

Resolution Note (2021.2.X):

This is an issue that seems to be fixed in Big Sur. MacOS is not delivering the up event until much, much later in some circumstances.

Comments (3)

Stakk3r

Jun 15, 2021 06:10

The bug is back in version 2021.1.11f1. This is quite infuriating. Controlling the game is a pain in the editor. I don't understand how fixing this isn't a higher priority?
Stakk3r

May 17, 2021 12:27

This seems to have been fixed. Not sure in which version (it might have been 2021.1.5f1 or 2021.1.4f1 already), but at least in 2021.1.6f1 it looks like it's working fine again. Possibly could have something to do with upgrading to Big Sur also.

Search Issue Tracker

1