Search Issue Tracker
Fixed in 2022.2.3f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a25
Votes
0
Found in
2022.2.0a9
2023.1.0a3
Issue ID
UUM-11715
Regression
Yes
InputActionMap window is not opening from Inspector when using serialized Input Actions
How to reproduce:
1. Open the user’s attached project
2. Open the “SampleScene” Scene
3. In Hierarchy select “InputAction” GameObject
4. In Inspector double click on “Action” InputActionMap in Test Script Component to open it
Note: if you do not see these elements in the inspector check and error messages in the console and fix package-related errors by removing it
5. Observe the result
Note: To fix the bug you can check IMGUI in A new Project Setting added: Editor > Inspector > Use IMGUI Default Inspector to fallback to using IMGUI for default inspectors
Expected result: InputActionMap window is opened
Actual result: Nothing happens
Reproducible with: 1.4.1 (2022.2.0a9, 2022.2.0b1, 2023.1.0a3)
Not reproducible with: 1.4.1 (2020.3.37f1, 2021.3.6f1, 2022.1.11f1, 2022.2.0a8)
Reproduced on: macOS 12.4 Beta (M1 and Intel Core), Windows 10 Pro
Not reproduced on: macOS 12.4 (Intel)
Notes:
- Not reproducible if deleting the “Canvas Renderer” Component
- With some editor versions, actions have two headers
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
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
Resolution Note (fix version 2023.1):
Fixed in: 2023.1.0a25
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.3f1