Search Issue Tracker
Fixed in 1.2.0
Votes
19
Found in [Package]
1.1.1
Issue ID
1368559
Regression
Yes
Enter key is not registered when using WasPressedThisFrame with Input System 1.1.1
How to reproduce:
1. Open project "InputIssue.zip"
2. Enter the Play Mode
3. Focus the Game window
4. Press the "Enter" key
Expected result: "Enter" key registered and numbers are changing
Actual result: "Enter" key is not registered and numbers are not changing
Reproducible with: 1.1.1 (2019.4.30f1, 2020.3.19f1, 2021.1.23f1, 2021.2.0b13, 2022.1.0a11)
Not reproducible with: 1.1.0-pre.5, 1.1.0-pre.6 (2019.4.30f1, 2020.3.19f1, 2021.1.23f1, 2021.2.0b13, 2022.1.0a11)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.2.0):
The fix landed in https://github.com/Unity-Technologies/InputSystem/pull/1424