Search Issue Tracker
In Progress
Fixed in 1.12.0
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (fix version 1.12.0):
Fixed an issue where action map action trigger hooks were erroneously set when notifications were set to UnityEvents.
These hooks are only now set when notifications are set to be: SendMessage, BroadcastMessage or CSharp events.
Resolution Note:
Fixed an issue where action map action trigger hooks were erroneously set when notifications were set to UnityEvents.
These hooks are only now set when notifications are set to be: SendMessage, BroadcastMessage or CSharp events.