Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.36f1
2022.3.22f1
2023.2.16f1
6000.0.0b13
Issue ID
UUM-67720
Regression
No
Input.GetKeyUp() is not called when the Right Shift key is pressed and released while the Left Shift key is held down
How to reproduce:
1. Open the attached “shift_getkeyup_issue” project
2. Open the “SampleScene” and enter Play mode
3. Press and hold the Left Shift key, and then the Right Shift key
4. Release the Right Shift key
5. Observe that no message is printed in the Console window when the key is released
6. Release the Left Shift key
7. Observe the Console Window
Expected result: The Console prints a message when the Right Shift key is released
Actual result: The Console message showing that the Right Shift key is released only appears after both the Right Shift and Left Shift keys are released
Reproducible in: 2021.3.36f1, 2022.3.22f1, 2023.2.16f1, 6000.0.0b13
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Notes:
* Reproducible in Player
* Not reproducible when using the Input System package
* The issue also reproduces for the Left Shift key while the Right Shift key is held (press Right Shift → press Left Shift → release Left Shift)
* Alternating the pattern (press Left Shift → press Right Shift → release Left Shift → release Right Shift) does not reproduce the issue
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
- [VFX] Missing Expand Option with Output Slot
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.