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

Fixed in 2022.1.X

Fixed in 2021.2.X

Votes

51

Found in

2021.2.0b17

2022.1.0a13

Issue ID

1375664

Regression

Yes

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

Input

Oct 25, 2021

To reproduce:

1. Download the attached project "New Unity Project.zip" 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

Notes:
- 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

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.
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 (43)

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.
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.
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?
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!
haiou1024

Nov 03, 2021 03:30

Did we have a temporary solution for this issue? It's really annoying.
yakandco

Nov 02, 2021 23:58

How does this happen? it's as though there's no QA testing for mac releases lately. v2021.1.22 became completely unusable on macs with extremely bad frame rate stuttering in the editor, and now basic typing in the editor doesn't work in macs. I'm sure the teams are working hard and QA is happening, but is obviously not thorough enough or under resourced. Something so fundamental as this is so confusing how it can make it into a production build, frankly it's pretty embarrassing.
Timmehh9

Nov 02, 2021 22:36

This is still an issue. The editor only updates with keystrokes and mouse movement. So if you type a letter or change a value using an arrow button, it won't show until you make another input via keyboard or mouse.
wreck709

Nov 02, 2021 03:05

Same issue here in MacOS Apple Silicon version of Unity Editor 2021.2.0f1.
ManjitSBedi

Oct 31, 2021 17:47

I am experiencing this issue with MacOS using Unity version 2021.2.0f1.
animaonline

Oct 31, 2021 13:51

Waiting for a fix