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
- 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:
There are no fixes planned for this Bug
Resolution Note:
There are no fixes planned for this Bug