Missing Save As and Auto-Save buttons in Project Settings -> Input Actions

Input
, ,
1

When trying to alter the Input Actions via Project Settings | Input System Package | Input Actions, I am missing the Save As and Auto-Save buttons, so I can’t save my changes.

Tried it with Unity 6.0 and Unity 6.3, so it looks like it is a Input System 1.18.0 issue.

2

I dont remember a save as.. but
image
If auto-save is selected they tend to go grey’d out.

3

As I mentioned, the buttons aren’t there.

Screenshot 2026-02-22 at 20.16.14
Screenshot 2026-02-22 at 20.16.141165×699 33.7 KB

4

They’ve never been there for the project wide settings I’m pretty sure.

They show up when editing a standalone input actions asset.

It will still be saved when you CTRL-S so no need to worry.

5

Editin the global does in fact NOT save. I havent foudn a clear repo why it happens yet. @antenomspa you can “fix” it for now by:

image
image512×144 6.78 KB

clicking on the InputSystem_Actions asset in the global settings again.
This will open a sbut menu for actionsEditor:
image
image961×783 40.9 KB

in this one you will now see the save asset / auto save. And editing it should save the changes :slight_smile:

6

No need for the thumbs down. It should save when editing it but I guess the editor has a bug in that it doesn’t dirty the asset on any change.

Mind you the project wide input actions makes for terrible code architecture and I suggest not using it.

8

Thanks for raising the issue, a ticket has been submitted earlier this month. Feel free to upvote.

10

A PR has been merged to develop branch containing a fix for this issue.
Next release will include this fix.

See more here: FIX: Input System actions not auto-saving in Project Settings when both related windows were open by josepmariapujol-unity · Pull Request #2362 · Unity-Technologies/InputSystem · GitHub

Thank you for your feedback!

11

Regarding the missing Save As or Auto-Save buttons in Project Settings → Input Actions: they are not actually missing. They were intentionally omitted to follow the Project Settings convention of saving changes automatically.

12

Still don’t have any save buttons in v1.19.0, 6000.3.9f1 and none of my changes are auto saving.

image
image2308×1225 176 KB

For anyone else as a work around I hit a breakpoint in jetbrains rider and entered the following command to turn on auto saving.

InputEditorUserSettings.autoSaveInputActionAssets = true

image
image1314×879 56.7 KB

For the Unity team i inspected the autoSaveToggle toggle when the GUI is being created and the width/height of the auto savetoggle are NaN.

13

I think we established there is if you edit it one way, and the team have said you dont need it if you edit it the other.. So if you edit the SO version in your folder structure you will get buttons, aka

image
image161×134 5.19 KB

if you edit it through the project settings you do not and this is by design.. aka

image
image512×144 6.78 KB

14

Still the issue is there (Unity ver. 6000.3.19)
Look at this flow:

  1. I select InputSystem_Actions asset.
    изображение
  2. In the Inspector it says “Edit in project settings”.
    изображение
    изображение546×401 15.5 KB
  3. So I press this and open the project settings. Adding new action there.
    изображение
    изображение1078×651 65.5 KB
  4. Saving the project and closing it.
  5. Opening the project, all my changes are gone.
    изображение
    изображение1073×649 61.5 KB

    It’s very frustrating when all your work is gone
15

then log a bug, as the unity guys said the way you’re doing it it auto saves

16

I am also running into this, it does not in fact auto save when doing it through project settings. Any changed actions are also not appearing in the inspector when you have a public InputActionReference

17

OK, so if you dont think it saves, edit it from the SO file in your project files.

18

Opening and editing in the file also does not work. The only method that does work is to double click the asset in the “Project-wide Actions” field while in the Poject Settings window and open a seperate window to edit. This is certainly a bug otherwise why would they allow editing in the project settings window?

19

well its working for a lot of us, so there must be some other actions blocking it, if editing it from the SO in your project files, which comes with a save button, then log it as a bug. but it sounds like its being blocked somehow by the project