Search Issue Tracker
Fixed
Votes
12
Found in [Package]
1.4.1
Issue ID
ISXB-244
Regression
Yes
Upgrading to 1.4.1 throws errors for keyboard use
-see title
-repro:
# get [https://github.com/UnityTechnologies/InputSystem_Warriors]
# move it 1.3.0 package version
# start scene
# notice the warrior moves using the keyboard
# upgrade to 1.4.1 package version
# start the scene
NOTICE the warrior doesn't move using the keyboard and extra errors are thrown
Redoing this with a clean checkout and upgrade the keyboard works but new errors are thrown:
Type of instance in array does not match expected type
UnityEngine.InputSystem.PlayerInput:OnDisable () (at Library/PackageCache/com.unity.inputsystem@1.4.1/InputSystem/Plugins/PlayerInput/PlayerInput.cs:1735)
Interaction count in old and new state must be the same
UnityEngine.InputSystem.PlayerInput:OnDisable () (at Library/PackageCache/com.unity.inputsystem@1.4.1/InputSystem/Plugins/PlayerInput/PlayerInput.cs:1735)
-
unity_4tsblackcat
Sep 16, 2022 12:55
This is actually quite 'game-breaking' in our XR project. 2022.1.15f1 with 1.4.2 Saying won't fix in 1.4.x leaves us sitting waiting on some future version of the 1.5.x alpha/beta software to finally reach non alpha/beta status.
-
Schubkraft
Sep 10, 2022 08:44
You might be running into this change https://forum.unity.com/threads/input-system-1-4-1-released.1306062/#post-8368569 too.
-
john79
Sep 09, 2022 08:39
i have the same issue with 1.4.2 the issue is kind of urgent cause i cannot use the keyboard and there is no precise error or suggestion on how to solve it. please fix
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:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-282