Open jalanjarosz opened 1 year ago
I worked around this by adding four fake toolheads in my macros.cfg file
[gcode_macro T0]
gcode:
ACTIVATE_EXTRUDER EXTRUDER=extruder
[gcode_macro T1]
gcode:
ACTIVATE_EXTRUDER EXTRUDER=extruder
[gcode_macro T2]
gcode:
ACTIVATE_EXTRUDER EXTRUDER=extruder
[gcode_macro T3]
gcode:
ACTIVATE_EXTRUDER EXTRUDER=extruder
[gcode_macro T4]
gcode:
ACTIVATE_EXTRUDER EXTRUDER=extruder
Description of the bug
T'#' tool change G-code is placed in output file when using G-code flavor of "Klipper"
Due to Klipper having multiple different ways to configure tools, using the default T'#' is not necessary, although the current alpha6 is placing tool change G-code into the output file.
Example sliced G-code from alpha6
PrusaSlicer is putting in the T1 call, and it's really not necessary as Klipper has other methods to change tool's (G-code macro's) that would be put in the Tool Change G-code section like:
Project file & How to reproduce
Setup a .stl with a tool change using multiple tools.
I'm using 2 extruders and the Single Extruder Multi Material checked.
Checklist of files included above
Version of PrusaSlicer
2.6.0-alpha6+win64
Operating system
Windows 10
Printer model
Piper2 -v2 coreXY