Search Issue Tracker
Fixed in 1.1-pre.4
Votes
0
Found in [Package]
1.0.2
Issue ID
1319756
Regression
No
PlayerInput component loses its reference to an InputActionAsset
-e: see title, instantiated prefab has no reference to the asset
-repro:
--Start play mode on the "Scene_Main" Scene
--press Enter on the keyboard, this loads the "Scene_Lobby" Scene.
--leftclick into the scene to have player prefabs instantiated via the PlayerInputManager.
---in the first attempt you will notice that its PlayerInput component likely has the correct reference to the InputActionAsset. #
--stop play mode and repeat the same steps from the beggining - starting from the "Scene_Main".
--on the 2nd try whenever you instantiate a player prefab, you will notice that its PlayerInput component loses its reference to the InputActionAsset
-reproduces with 1.0.2 and 1.1.0-preview.3
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
- The Inspector does not shown SkinnedMeshRenderer Bounds when they are overriden by script
- Confusing validation message in Scoped Registries
- Compute shader is dispatched with unsupported workgroup size on multiple browsers when building the project for Web with WebGPU Graphics API
- Rotation Property collapses after changing Interpolation Type In Animation window
- It is possible to enter impossible Scope name in the Scope Registries of Package Manager Project settings
Resolution Note (fix version 1.1-pre.4):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1316