GregValiant

All this depends on your settings. If you disable z-hop on retraction the gcode is one way. With it enabled it's another way. Adding all the if-come-whens and what-ifs is...

I changed this a bit. There should be some improvement. The script doesn't change any lines, it just reorders them. The speeds seem to be fine so I'm not sure...

Within a "virgin" gcode the travel speed is 250mm/sec (which you have set in Cura). Re-ordering the lines (as the script does) doesn't change that. M135 T0 G92 E0 M104...

Within the Cura Machine Settings, there is no "XY Offset" between the nozzles of your printer but there obviously is an offset. That shuffle move that brings the next nozzle...

Will the firmware accept a simple "T" line for the tool change (instead of M135), or are you stuck with the M135 line?

This version moves the cut lines to below the Z-hop down line. G92 E0 ;MESH:NONMESH G0 F15000 X10.32 Y-51.817 Z5.45 G0 X9.008 Y-51.269 ;TYPE:PRIME-TOWER G1 F900 Z0.45 **M135 T0** G92...

I have absolutely no idea why that line would make a difference. It's gotta be something in the M135 macro in the firmware. ;TYPE:PRIME-TOWER G1 F900 Z1.5 G92 E0 G1...

The definition files come from the community or from the manufacturer. When someone submits a Pull Request for the printer it will show up on the Pull Request page here...

This line in the StartUp won't work: M109 S[material_print_temperature_layer_0] because Cura uses curly brackets to denote replacement patterns. It should be: M109 S{material_print_temperature_layer_0} Other than that it looks like the...

I'll see your "Start In" folder and raise you a "Save To" folder. Right now it seems like Cura always starts in the last folder "saved to" or "opened from"...