PrusaSlicer 2.8.1 Fillament specific custom end G-code bug report
 
Notifications
Clear all

PrusaSlicer 2.8.1 Fillament specific custom end G-code bug report  

  RSS
Wilco van der Veen
(@wilco-van-der-veen)
Member
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.

Posted : 10/10/2024 4:26 pm
Diem
 Diem
(@diem)
Illustrious Member

If it's filament specific, have you specified the same filament for both extruders?

Cheerio,

Posted : 10/10/2024 6:56 pm
Wilco van der Veen
(@wilco-van-der-veen)
Member
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

Posted : 10/10/2024 7:07 pm
Neophyl
(@neophyl)
Illustrious Member
RE: PrusaSlicer 2.8.1 Fillament specific custom end G-code bug report

If you want to report an issue it needs to be done here https://github.com/prusa3d/PrusaSlicer/issues   

The forum is user to user and anything brought up up is likely to not be seen by devs and certainly isn't tracked like it is over on the PS github.  

If you do want to report an issue please make sure to check first if one already exists that covers the problem.

 

Posted : 11/10/2024 8:15 am
Share: