Notifications
Clear all
PrusaSlicer 2.8.1 Fillament specific custom end G-code bug report
When using fillament specific custom end G-code on the prusa XL with two extruder there seems to be a bug generating the gcode.
On extruder 1 I have no custom gcode but on extruder 2 I do (or rather did)
When slicing a model set to extruder 1 the slicer adds the custom end gcode of both extruders in the generated gcode.
This ofcourse negates the effect of having fillament specific end gcode.
Napsal : 10/10/2024 4:26 pm
If it's filament specific, have you specified the same filament for both extruders?
Cheerio,
Napsal : 10/10/2024 6:56 pm
Topic starter
answered:
RE: PrusaSlicer 2.8.1 Fillament specific custom end G-code bug report
No I don't, one extruder is used for PLA and one is CF filled PETG
Napsal : 10/10/2024 7:07 pm