Only Custom Start G-code Prevents Filament Specific GCode

[randellhodges]

If I check the box on the Printer Settings->Custom G-Code for Only custom Start G-code, the value in Filament Settings->Custom G-code->Start G-code is not emitted.

Superslicer version: 2.3.56.5

[randellhodges]

This might be a case of, "be careful what you ask for", but I tried the nightly and it seems to be working but...

Sorry, my picture is backwards. The one on the right does not have "only custom start g-code" selected, the one of the left has that option selected.

The lines in yellow are the ones I wanted gone, and the ones in red should probably be down where the yellow lines are currently.

I guess I could include the G21, G90, and M83 in my PRINT_START macro, but if I ever wanted to toggle relative/absolute extrusion in the slicer, I'd have to update the klipper macro. I am checking now to see if there is a way I can pass that choice to my macro.

Edit: Changing my print start macro like this will allow me to choose between M83 and M82 in my macro. So no action is needed.

PRINT_START EXTRUDER=[first_layer_temperature] BED=[first_layer_bed_temperature] RELATIVE_E=[use_relative_e_distances]

[supermerill]

write {if use_relative_e_distances}M83{else}M82{endif}

edit: too late, so the issue can be closed?

[randellhodges]

Yup, I'll close it. I just wanted to "document" it so maybe it'll help someone else out in the future. Thanks!