Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.0
1.11.2
7000.0.0
Issue ID
ISXB-1325
Regression
Yes
Default Input Action Asset creates unsaved changes when clicking on Button actions
Steps to reproduce:
- Open a Unity Project
- Ensure that the Input System package is installed
- Create a new Empty GameObject via GameObject > Create Empty
- Select the new GameObject
- Add a 'Player Input' component to the GameObject
- On the Player Input component, click 'Create Actions' and create a default Input Actions Asset
- Double click on the new Input Actions Asset to open it
- Ensure 'Auto-Save' is not enabled
- Click on any Action in either the Player or UI Action map that has an 'Action Type' of Button
Actual results: The Input Asset gets unsaved changes.
By saving and then checking GitHub, it looks like the changes are from converting Button to an empty string for each Button Action you click on from the default asset:
!image-2025-01-13-15-44-04-242.png|width=585,height=662!
Expected results: The Input Asset does not get unsaved changes
Reproducible with versions: 1.11.2, 1.8.0
Not reproducible with versions: 1.8.0-pre.2
Can't test with versions: 7000
Tested on (OS): Windows 11
Notes:
- This occurs both on a default input action asset created with some project templates, or with creating a default input action asset via a Player Input component.
- This doesn't affect Input Action Assets that the user creates from scratch, or if they add their own Button Action Type to an Input Action Asset.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.