Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.4.3
Issue ID
ISXB-312
Regression
Yes
Input doesn't get registered when pressing WASD or Arrow keys
Reproduction steps:
1. Open the user’s attached project
2. Enter the Play Mode
3. Try pressing WASD keys and then Space key
Expected result: All keys' input gets outputted to Console
Actual result: Only the Space key gets outputted to Console
Reproducible with: 1.4.1 (2021.3.10f1, 2023.1.0a9), 1.4.3 (2021.3.12f1, 2022.1.20f1, 2022.2.0b11, 2023.1.0a14)
Not reproducible with: 1.3.0 (2021.3.7f1, 2023.1.0a3)
Could not test with: 2020.3.40f1 (Assets\Scripts\Environment\Treasures\Chest.cs(3,19): error CS0234: The type or namespace name 'CompilerServices' does not exist in the namespace 'Unity.Burst' (are you missing an assembly reference?)
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-254