@dwuk Splitting the gcode file?
I never thought of this as an option when I built the hashPrinter in 2021.
In my mind it was always the slicer who had to split the object, but that approach had it's own issues.
Your approach looks very promising, although I see lots of retracts/unretracts where the tracks were chopped apart. That can end up ugly, like tons of blobs everywhere.
And of course you'll run into tool collision situations and waiting for the other tool to finish the current layer while the waiting nozzle drools dry. (just as I did)
My idea to the latter problem was, to synchronize both tool speeds, so they finish work at the same time.
Maybe you want to add that in your splitting post processor?
BTW, my hashPrinter only required 4 steppers for the whole motion system ( plus 3 for Z and 4 for extruders) and all the belts where short and straight. Not such idle roller nightmare...
But lets not start a pi$$ing contest. There are pros & cons in both designs