Search Issue Tracker
Fixed
Fixed in 1.9.0
Votes
1
Found in [Package]
1.6.3
1.7.0
1.8.1
Issue ID
ISXB-818
Regression
No
Control scheme changes to PlayerInput used action asset fail to update correctly if the component is part of a prefab
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/Scenes/MainMenu“ scene
3. Enter Play Mode
4. Observe the Console window
Expected result: No errors are thrown in the Console window
Actual result: “Cannot find default control scheme 'Mouse' in 'ControlCenter (UnityEngine.InputSystem.InputActionAsset)'“ error is thrown in the Console window
Reproducible with: 1.6.3(2021.3.29f1, 2022.3.8f1, 2023.2.0b6), 1.7.0(2021.3.36f1, 2022.3.21f1, 2023.2.16f1, 6000.0.0b12), 1.8.1(2022.3.21f1, 2023.2.16f1, 6000.0.0b13)
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Note: Disabling and re-enabling the “Player Input“ Component on the “EventSystem“ GameObject fixes the issue, the error is no longer thrown when entering Play Mode
-
Artykin
Aug 15, 2024 09:06
Hi!
Just found this same bug in 1.8.2.
Happy to hear it is already fixed in next version, and thanks for the quick fix to get rid of the error.
- Are
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.9.0):
Fixed in upcoming Input System version 1.8.3