Search Issue Tracker
Fixed
Votes
0
Found in
2021.3.28f1
2022.3.4f1
2023.1.3f1
2023.2.0a22
Issue ID
UUM-41466
Regression
Yes
Mouse and JoystickButton KeyCodes are different in runtime when selected in Inspector
Reproduction steps:
1. Open the “KeyCodeStripped” project
2. Open the “SampleScene” scene
3. Select the "Checker" GameObject
4. In Inspector ensure the selected KeyCode is "Mouse 0"
5. Enter Play Mode and observe the Console
Expected result: The selected KeyCode (i.e. “Mouse0”) is logged
Actual result: An unexpected KeyCode (i.e. “Print” in 2022.3, "Break" in 2023.1) is logged
Reproduced in: 2022.2.21f1, 2022.3.5f1, 2023.1.0b18, 2023.1.3f1, 2023.2.0a16, 2023.2.0a19
Not reproduced in: 2021.3.28f1, 2022.2.20f1, 2023.1.0b17, 2023.1.4f1, 2023.2.0a15, 2023.2.0a20, 2023.2.0b1
Regressed in: 2022.2.21f1, 2023.1.0b18, 2023.2.0a16
Already fixed in: 2023.1.4f1, 2023.2.0a20
Reproduced using: Windows 10 (by reporter), macOS 13.4.1 (Intel)
Notes:
1. Reproducible KeyCodes start from “Left Meta” till the end
2. KeyCodes between "Left Meta" and "Alt Gr" can instantly change the selection to their unexpected KeyCodes (e.g. select "Mouse 0", then select "Left Meta", and the selected KeyCode will set to "Right Meta")
3. Also reproduced in Player
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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-36836