Search Issue Tracker
In Progress
Votes
0
Found in [Package]
1.7.0
Issue ID
ISXB-711
Regression
No
InputActionAsset is not being updated when it is already assigned to PlayerInput
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/Main” scene
3. Enter Play mode
4. Press the “K” button
5. In the Hierarchy window, observe the “Entrance Room” GameObject
Expected result: A new “Viewport“ GameObject was created as an “Entrance Room” GameObject child
Actual result: No new GameObject was created
Reproducible with: 1.6.1 (2022.3.5f1, 2023.2.0b1), 1.7.0, 1.8.0-pre.2 (2022.3.14f1, 2023.2.3f1, 2023.3.0a17)
Couldn't test with: 2021.3.33f1 (compilation errors while importing the project to this version)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- “Readme” Asset is unreadable in the Inspector window when switching Editor Theme to Light
- “NullReferenceException” error thrown when switching Editor Theme to Light if “Unity Version Control” tab is enabled
- A Warning is displayed in the Inspector when a Mesh with any Material is added as a Terrain Detail
- [Android][Vulkan] Memory leak when playing and stopping a video using the Video Player on some devices
- Caret moves by a character when typing "." and any number into 'Grid and Snap' toolbar's input field
Resolution Note:
Fixed an issue where action map delegates were not updated when the asset already assigned to the PlayerInput component were changed [ISXB-711](https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-711).
Resolution Note:
[Input System] Fixed an issue where action map delegates were not updated when the asset already assigned to the PlayerInput component were changed [ISXB-711](https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-711).