slic3r / Slic3r

Open Source toolpath generator for 3D printers
https://slic3r.org/
GNU Affero General Public License v3.0
3.28k stars 1.29k forks source link

The "modfied" detection doesn't always work. #5102

Open rewolff opened 2 years ago

rewolff commented 2 years ago

Do not report Prusa3D Slic3r bugs here without confirming it is a problem on a development release of Slic3r, or your issue will be closed. Development builds of Slic3r. Prusa3D Issue Tracker

Describe the bug

Some changes in the printer settings, like the number of perimeters (sometimes?) don't set the "config changed" flag. This results in no "(modified)" in the name of the configuration and more importantly no recalculate of the object being printed.

To Reproduce Not sure what exactly triggers this: When it happened to me this afternoon, I remember turning on "complete individual objects" and when printed.... that didn't happen. Then later I changed the number of perimeters and going back to the layers view... nothing had changed.

So then I decoded to write this bugreport and going back to reproduce... each time I clicked one of those buttons: immediately "(modified)" shows up and it looks as if the toolpath is re-evaluated. Good. So then I started thinking: Did I imagine that? If I can't reproduce at all, what's the use of finishing the bug report.

Then I went to my slicer, decided to lower "minimal layer time" and.... now that setting doesn't trigger a modified flag....

It seems that it starts tracking "modified" once you have manually hit "save" on that settings tab at least once.....

3D Model and Slic3r Configuration Export I don't think the model and config matter for this.

Expected behavior The change should most importantly be reflected in the generated/exported G-code.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context none