Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.26f1
Issue ID
UUM-39906
Regression
No
The Editor does not recognize button release when first releasing the "LShift" button and then "Numpad2"
Reproduction steps:
1. Open the attached “Repro.zip” project
2. Open the “Scenes/SampleScene” Scene
3. Enter the Play Mode
4. Hold the “NUMPAD2” button on the keyboard while holding the “LSHIFT” button
5. Let go of the “LSHIFT” button first and then “NUMPAD2”
5. Observe the Game View
Expected result: After releasing “NUMPAD2” the Editor recognizes that the button has been released
Actual result: After releasing “NUMPAD2” the Editor still recognizes that the button is being held down
Reproducible with: 2021.3.26f1, 2022.1.0a14
Not reproducible with: 2022.2.21f1, 2022.3.0f1, 2023.1.0b19, 2023.2.0a17
Fixed in: 2022.1.0a15
Reproducible on: Windows 10
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Bug already fixed in 2022.1.0a15