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
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
- Crash on AMDUnityPlugin.DLL in specific built project when using FSR2 upscaler
- RenderObjects does not have any Depth texture bound when Event is set to AfterRenderingPostProcessing
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
Resolution Note (fix version 1.1-pre.4):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1316