Search Issue Tracker
By Design
By Design in 1.14.X
Votes
1
Found in [Package]
1.14.1
Issue ID
ISXB-1643
Regression
No
Modifications to the InputActions asset in Play Mode persist when exiting Play Mode
How to reproduce:
1. Open the attached "IN-108286" project
2. Open the "SampleScene" and enter Play Mode
3. Modify the “BugRepro.cs” script by adding a comment
4. Save the changes to the script
5. Open “InputSystem_Actions” asset
6. Observe the Actions List
7. Exit Play Mode
8. Repeat steps 5-6
Expected result: Changes made during Play Mode to the InputActions asset do not persist outside it
Actual result: Changes persist after exiting Play Mode
Reproducible in: 1.8.1 (6000.0.0f1), 1.12.0(6000.0.37f1, 6000.2.0a3), 1.14.1(6000.0.55f1, 6000.2.0f1, 6000.3.0a4)
Reproducible on: macOS 15.5 (M1), Windows 10 (reporter), Windows 11
Not reproducible on: No other environments tested
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
InputActionAsset is a ScriptableObject and this is inline with expected behaviour for ScriptableObjects stored as assets.
It could however be seen as desirable to work against that and restore assets when exiting play mode but it would then break existing behavior and behave differently than ScriptableObject does by default. As such we've decided to not make any changes to this existing behaviour
Resolution Note (1.14.X):
InputActionAsset is a ScriptableObject and this is inline with expected behaviour for ScriptableObjects stored as assets.
It could however be seen as desirable to work against that and restore assets when exiting play mode but it would then break existing behavior and behave differently than ScriptableObject does by default. As such we've decided to not make any changes to this existing behaviour