Pulled straight from the G-code
Modern slicers (PrusaSlicer, OrcaSlicer, BambuStudio & ElegooSlicer) annotate each object in the G-code. SimplyPrint reads those annotations and shows the objects in the print job UI with per-object status and a skip control.
Spot the failure, skip the object
Open the ongoing print job. The Objects on the bed card lists every part the slicer placed, with its position and a per-object status. Click the skip control on the failed object and the printer's firmware lifts to the next one - the rest of the plate finishes as planned.
Why this matters at print-farm scale
Print farms run multi-object plates to maximise throughput - one plate, twenty parts. If one fails halfway through, canceling means losing nineteen good prints with it. Skip Objects lets the firmware step over the failed part and finish the rest, recovering 95% of the bed time you'd otherwise burn. Across a fleet running dozens of multi-object plates a day, that's the difference between "we lose a plate every time something goes wrong" and "we lose a part every time something goes wrong".
Works across OctoPrint, Bambu Lab, Klipper and RepRapFirmware
SimplyPrint's skip-object control works wherever the underlying firmware or host supports per-object skipping:
- OctoPrint (Marlin 2.1+ and any printer that accepts
M486) - Bambu Lab printers via the SimplyPrint Bambu integration
- Klipper via the built-in
exclude_objectmodule - RepRapFirmware on Duet boards
Slicer support for per-object markers
Skip objects relies on per-object G-code labels that OrcaSlicer, PrusaSlicer, BambuStudio and SuperSlicer all output by default. If your slicer profile is older or has the option disabled, the card still shows the objects but the skip control is greyed out, and the print job tells you why.