Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2021.2.X



Found in



Issue ID




The first Keyboard Input is Ignored and stored for later when renaming Assets causing all Keyboard Inputs to become mixed



To reproduce:

1. Download the attached project "New Unity" and open it in Unity
2. In Project view create a Folder or another Asset
3. Try to change its name

Expected Results: You can easily change Asset name and Unity Editor correctly detects Keyboard Input
Actual Results: First Keyboard Input is Ignored and Stored for later causing Asset renaming to become mixed

- This issue only happens on macOS systems
- For example, if you press the "L" key on Keyboard, it becomes ignored, then if you press another Key like the "Delete", in Unity Editor you can see that the "L" symbol is printed, then you can press for example the "A" key and observe that the "L" symbol is deleted and if you press then Key like the "T" or another key, you can see that the "A" symbol is printed.
- Its sounds like the first Input is ignored and stored for later causing all Keyboard Inputs to become mixed

Reproducible on Unity 2021.2.0b17 and 2022.1.0a13
Not reproducible on Unity 2021.1.27f1, 2021.2.0b16 and 2022.1.0a12
Regression on Unity 2021.2.0b17 and 2022.1.0a13

  1. Resolution Note (fix version 2022.1):

    Fixed in: 2022.1.0a14

    Recent Mac Metal editor change delayed frame updates by 1, affecting keyboard input lag - this is now fixed.

  2. Resolution Note (fix version 2021.2):

    Fixed in: 2021.2.2f1

    Recent Mac Metal editor change delayed frame updates by 1, affecting keyboard input lag - this is now fixed.

Comments (39)

  1. FrailQuail

    Nov 06, 2021 17:15

    I'll use the inspector to input variables and will have a 1 letter not appear until I select somewhere else on the screen. Using 2021.2.1f1

  2. bab202

    Nov 06, 2021 05:52

    We both know that this issue is so critical but may be there are reason for Unity team did not fix this soon, may be it relate to many other components in the Editor. Hope this issue can be fix as soon as possible. Cheers!

  3. MoreFoam

    Nov 06, 2021 04:55

    Neither this release, nor the LTS release is working properly on the new MBP's.... I will continuously scream into my pillow until this is fixed. The life of my beautiful, luscious voice is in your hands

  4. laffan

    Nov 06, 2021 03:14

    This is still not fixed in 2021.2.1f1. ( MBP, Mid 2015, i7)

  5. MartinParadis1970

    Nov 06, 2021 00:36

    No this is not fixed for 2021.2.1f !!!! Do you understand this is a crucial bugs for people here ? When I used to work there, everyone had MacBook Pro. Why this bug did not receive more attention, this is unbelievable.

  6. rooksoto

    Nov 05, 2021 13:57

    This is still an issue in 2021.2.1f1, released today.

  7. TV4Fun

    Nov 04, 2021 22:25

    Regarding this being an issue with the Metal editor, I tried switching my project API to OpenGL and am still having the same issue.

  8. TV4Fun

    Nov 04, 2021 21:50

    I think we may have differing definitions of "fixed." For me, fixed means that I can download a new version of the editor that does not have this issue. I'm very happy for you if this is fixed in your internal codebase, but that doesn't really do me a lot of good when I'm trying to develop a game using the public (final, not beta) release.

  9. Timmehh9

    Nov 04, 2021 03:31

    Do Unity employees ever comment on these threads? This is an editing but nightmare that makes native silicon use worthless. How soon could we expect an update to 2021.2 that has the fixes mentioned above included?

  10. mrstruijk

    Nov 03, 2021 09:39

    Had this issue too on 2021.2.0. Caused some interesting bug-hunting, since the delay is also visible in the Console :).

    Downgraded to 2021.1.27, which works just fine for me!

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.