Search Issue Tracker
Fixed
Votes
3
Found in [Package]
1.1.0-pre.6
Issue ID
1359217
Regression
No
[Input System] PrtScn is triggered when pressing certain different keys with either NumLock on or off
How to reproduce:
1. Open the attached project ("InputSystem.zip") and open SampleScene
2. Press the "Play" Button and open the Console
3. Press on the Game Window
4. Press Insert, Home, Delete, End, Page Up, Page Down, Upward Arrow, Downward Arrow, Left Arrow, Right Arrow Keys one at a time
5. Press NumLock
6. Press Insert, Home, Delete, End, Page Up, Page Down, Upward Arrow, Downward Arrow, Left Arrow, Right Arrow Keys one at a time
Expected result: PrtScn Key was not logged in Console
Actual result: PrtScn Key was logged in Console
Reproducible with: 1.0.0 (2019.4.30f1), 1.0.1, 1.0.2 (2020.3.17f1), 1.1.0-pre.6 (2021.1.19f1, 2021.2.0b9, 2022.1.0a6)
Note: On some keyboards, this behavior is triggered with NumLock on, on others with NumLock off
-
Niclaskjellberg_TO
May 12, 2022 09:21
Is this going to get backported to other unity versions than 2022.1.0a16? We're currently on 2021.2. In the forum post regarding this, it was said that backporting was on its way. But no news since then.
https://forum.unity.com/threads/rebind-bug-arrows-print-screen.807060/
-
unitydreamer29
Sep 15, 2021 13:18
I see this as well in 1.1.0-pre.5
-
jukibom
Sep 10, 2021 13:13
Yep, I'm getting reports from users of this too.
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Fixed in: 2022.1.0a16
Resolution Note:
Fixed in: 2020.3.37f1