Search Issue Tracker
Fixed
Fixed in 1.9.0
Votes
0
Found in [Package]
1.8.0
Issue ID
ISXB-601
Regression
No
Input stops working after making a change in the Input Action window (in PlayMode) and pressing the “Save Asset” button when using New Input System
How to reproduce:
1. Open the user’s attached “FVL-Virtual-Targets.zip” project
2. Enter Play Mode and press the "W" or "S" key to move the Camera
3. Exit Play Mode and open “Virtual Targets.inputactions” add a new action, and press the “Save Asset” button
4. Repeat the 2nd step
5. Observe the result
Expected result: Camera movement is working
Actual result: Camera movement is not working
Reproducible with: 1.3.0 (2021.3.0f1), 1.6.3 (2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b3)
Reproduced on: macOS 13.4.1 (Intel)
Note: not reproducible after restarting the Editor
UPDATE:
Although Configurable PlayMode options aren't supported by InputSystem, this issue has been reconsidered for a fix due to new information and priorities.
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:
There are no fixes planned for this Bug