Bug with filament save settings
 
Notifications
Clear all

Bug with filament save settings  

  RSS
Eiffel31
(@eiffel31)
Active Member
Bug with filament save settings

This is a very severe bug where gcode is generated with different values from the values displayed in the settings.

How to reproduce the problem:

- open PrusaSlicer 2.7.4

- import some random STL

- go to filament settings

- select some template. Ex: Prusament ASA

- modify some setting: bed_temperature to 95°C

- save as a new filament preset named "test"

- select a new filament profile. Ex: Prusament PLA

- modify some setting: first_layer_temperature to 212°C

- save the filament preset with the name "test" (same name as first time)

At this point, everything is broken. The displayed values are not the values used to generate gcode. The simplest way to check this is to export configuration (^E).

All the values are in green color on the interface, but the first_layer_temperature is not 212 in the file.

- Now change extrusion_multiplier to 1.01

- Export the configuration again

The extrusion_multiplier is correct (same value as displayed), but the first_layer_temperature is different from the displayed one.

 

As the effect of most parameters (such as extrusion_multiplier or temperature) is not really visible on the slicing result, gcode is produced with values that does not reflect the displayed configuration and this may result to major printing failure.

 

Note: Probablly not relevant, but observed on the Linux version

 

Posted : 10/04/2024 9:55 am
Neophyl
(@neophyl)
Illustrious Member
RE: Bug with filament save settings

This is a user to user forum.  If you want to report a bug you need to open one at the appropriate github.  For Prusa Slicer that is located here https://github.com/prusa3d/PrusaSlicer/issues

 

Posted : 10/04/2024 9:58 am
Eiffel31
(@eiffel31)
Active Member
Topic starter answered:
RE: Bug with filament save settings

OK, I filled a bug repport.

This message in the forum may help users with unexpected behaviour as gcode can be generated with values different from those displayed in the interface.

I had the problem this morning. I am not sure about the exact sequence I made to get into this situation, but the first layer failed due to a completely wrong temperature. The temperature used by the printer (same as in gcode) was very different from the temperature displayed in the interface.

 

 

Posted : 10/04/2024 12:19 pm
Share: