Search Issue Tracker
By Design
Votes
1
Found in
2023.1.7f1
2023.2.0b3
2023.3.0a1
Issue ID
UUM-44707
Regression
No
Serialized Key Code type fields are changed to a different type than the set ones
How to reproduce:
1. Open the user’s attached “TestInputBug.zip” project
2. In the Hierarchy window, select “GameObject” GameObject
3. In the Inspector window, observe the Key Codes of the elements
Expected result: Key Codes are: “Mouse 0”, “Mouse 1”, “Print”
Actual result: Key Codes are: “Print”, “Sys Req” and “Left Windows”
Reproducible with: 2021.3.29f1, 2022.2.20f1, 2023.1.0a1, 2023.1.7f1, 2023.2.0b3
Not reproducible with: 2022.3.0f1, 2022.3.6f1
Fixed in: 2022.2.21f1
Reproduced on: macOS 13.4.1 (Intel)
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
- Errors in the Console when creating a new "2D Platformer Microgame" template project
- Prefab Override popup displays on wrong monitor when Inspector width is resized to minimum
- Scroll View is not moving by inertia after scrolling by click and dragging when Editor window is minimized and Canvas "Render Mode" is set to "World Space"
- "type mismatch error" occurs when the currentDirectionWS output of a Sample Water Surface node is connected to a float3 input
- URP Material Upgrade utility does not enable Alpha Clipping when material had Rendering Mode set to Cutout
Resolution Note:
The data in the repro project's scene seems to be wrong. For example, KeyCode.Mouse0=323, but in SampleScene.unity, the serialized value says "keyCode: 316".
The only explanation I can provide is that some older versions of Unity have a bug that will make them save a scene with the wrong values in it. All recent official releases of Unity will save their data correctly. Unfortunately, scenes saved with wrong data can't be fixed automatically by upgrading to a more recent version of Unity that doesn't have the bug.