Search Issue Tracker
Won't Fix
Votes
2
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-775
Regression
No
Input Action Bindings do not trigger Input Action Events when the Input Actions are reset
Reproduction steps:
1. Open the “ReproProject“ project
2. Select the “Player“ GameObject in the Hierarchy window
3. Change the “Actions“ property under the “PlayerInput“ Script to “Actions Asset“, and then back to “Project-Wide Actions“ in the Inspector window
4. Open the Project Settings window (Edit > Project Settings)
5. Reset the Input Actions in the Input System Package category by pressing the three dots on the top right and selecting the “Reset“ button
6. Delete the “WASD” Binding from the “Move“ Action in the “Player“ Action Map
7. Repeat step 5
8. Enter Play Mode
9. Press the “W” or “S“ keys to move the “Player“ GameObject
10. Observe the Game view
Expected result: The “Player“ GameObject moves according to the key presses
Actual result: The “Player“ GameObject doesn’t move
Reproducible with: 1.8.0-pre.2 (2022.3.19f1, 2023.2.8f1, 2023.3.0b5)
Couldn’t test with: 1.6.3, 1.7.0 (2021.3.34f1, 2022.3.19f1, 2023.2.8f1, 2023.3.0b5), 1.8.0-pre.2 (2021.3.34f1) (due to Input Actions not existing under Input System Package category in Project Settings)
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Note:
Changing the “Actions“ property under the “PlayerInput“ Script component on the “Player“ GameObject to “Actions Asset“ and then back to “Project-Wide Actions“ after step 10 fixes the issue, and the player moves according to the “W” and “S” key presses again
-
unity_lKq4EmT3x95kHA
Feb 02, 2024 21:00
This bug is devastating for users new to package or new to Unity. Please consider fixing this. Users rely on the "reset" button as a safety net in case if they may have accidentally removed an entry or changed the project configuration.
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:
This will no longer be reproducible in the final Input System 1.8.0 release as we've changed how ProjectWideActions assets work