Save Project button grayed out even though savable changes are present #1319

New Issue

MrUnknownDE · 2026-04-05T17:19:34+02:00

MrUnknownDE commented

2026-04-05 17:19:34 +02:00

Originally created by @shwadi on 12/19/2025

Is there an existing issue for this problem?

I have searched the existing issues

OrcaSlicer Version

2.3.1

Operating System (OS)

Linux

OS Version

Ubuntu jammy

Additional system information

No response

Printer

Not importent in this case

How to reproduce

tl;dr: when hitting the Save current filament or the Save current machine button, the false assumption is made that the project is saved as a side effect.
Or the assumption is right but the side effect got lost.

In the following example the filament_notes field within the Material Settings will be edited but the issue is reproducible with any field within the Material Settings or the Printer Settings.

start a new project
click on the button to edit the filament settings
switch to the notes tab
check your note; if no note is present yet, write "<my_notes_content>"
save the filament change
save the project under /your/3mf/path.3mf

[optional]: verify hat the filament note is part of the .3mf file by opening it in another instance or hitting

unzip -c /your/3mf/path.3mf Metadata/project_settings.config | sed -e 1d -e2d | jq -r .filament_notes
[
  "<my_notes_content>"
]

return to the filament note and change it but do not hit the Save current filament button yet
close the Material settings Window and click on File in the top left corner
verify that Save Project is not grayed out yet, indicating that there are changes which need to be saved
now once again return to the Material settings Window and hit the Save current filament button
close the Material settings Window and click on File in the top left corner
verify that Save Project is now grayed out, indicating that there are no unsaved changes

verify that this is not the case by opening the .3mf file in another instance or hitting

unzip -c /your/3mf/path.3mf Metadata/project_settings.config | sed -e 1d -e2d | jq -r .filament_notes
[
  "<my_notes_content>"
]

actually save the project by hitting the disc-button on top or overwriting the existing .3mf file by hitting File -> Save Project as...

verify that the changes are now saved by opening it in another instance or hitting

unzip -c /your/3mf/path.3mf Metadata/project_settings.config | sed -e 1d -e2d | jq -r .filament_notes
[
  "<my_notes_content> additional_change"
]

Actual results

The Save Project button does not actually indicate the presence of changes, which could be saved.

Expected results

The Save Project button does actually indicate the presence of changes, which could be saved.

Project file & Debug log uploads

not needed

Checklist of files to include

Log file
Project file

Anything else?

This issue is reproducible even though under Preference the Auto-Backup is checked with the Value of 10 Seconds.
Not sure if the Auto-Backup feature is broken as well or if this is the intended behavior.

*Originally created by @shwadi on 12/19/2025* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.1 ### Operating System (OS) Linux ### OS Version Ubuntu jammy ### Additional system information _No response_ ### Printer Not importent in this case ### How to reproduce tl;dr: when hitting the `Save current filament` or the `Save current machine` button, the false assumption is made that the project is saved as a side effect. Or the assumption is right but the side effect got lost. --- In the following example the `filament_notes` field within the `Material Settings` will be edited but the issue is reproducible with any field within the `Material Settings` or the `Printer Settings`. * start a new project * click on the button to edit the filament settings * switch to the notes tab * check your note; if no note is present yet, write "<my_notes_content>" * save the filament change * save the project under `/your/3mf/path.3mf` * [optional]: verify hat the filament note is part of the `.3mf` file by opening it in another instance or hitting ```bash unzip -c /your/3mf/path.3mf Metadata/project_settings.config | sed -e 1d -e2d | jq -r .filament_notes [ "<my_notes_content>" ] ``` * return to the filament note and change it but do not hit the `Save current filament` button yet * close the `Material settings` Window and click on `File` in the top left corner * verify that `Save Project` is not grayed out yet, indicating that there are changes which need to be saved * now once again return to the `Material settings` Window and hit the `Save current filament` button * close the `Material settings` Window and click on `File` in the top left corner * verify that `Save Project` is now grayed out, indicating that there are no unsaved changes * verify that this is not the case by opening the `.3mf` file in another instance or hitting ```bash unzip -c /your/3mf/path.3mf Metadata/project_settings.config | sed -e 1d -e2d | jq -r .filament_notes [ "<my_notes_content>" ] ``` * actually save the project by hitting the disc-button on top or overwriting the existing `.3mf` file by hitting `File` -> `Save Project as...` * verify that the changes are now saved by opening it in another instance or hitting ```bash unzip -c /your/3mf/path.3mf Metadata/project_settings.config | sed -e 1d -e2d | jq -r .filament_notes [ "<my_notes_content> additional_change" ] ``` ### Actual results The `Save Project` button does not actually indicate the presence of changes, which could be saved. ### Expected results The `Save Project` button does actually indicate the presence of changes, which could be saved. ### Project file & Debug log uploads not needed ### Checklist of files to include - [ ] Log file - [ ] Project file ### Anything else? This issue is reproducible even though under `Preference` the `Auto-Backup` is checked with the Value of `10` Seconds. Not sure if the `Auto-Backup` feature is broken as well or if this is the intended behavior.

Sign in to join this conversation.

No Label bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#1319