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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.1-pre.4):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1316