How slicing works in PrintSol

A file has to be sliced for the printer model it prints on. PrintSol does that for you, either when you press Slice in File Manager or automatically when the queue needs a slice for a printer.

Where slicing runs

Slicing uses the Bambu Studio or OrcaSlicer command line where PrintSol runs. When no slicer is available there, the Slice panel says so. A bridge PC with OrcaSlicer installed can then slice instead, but with fewer options: the panel's settings are not used on that route.

The Slice panel

• Printer model (your own models first), Material, Nozzle and Quality: 0.20 mm standard, 0.12 mm fine, 0.28 mm draft, or 0.20 mm strength (more walls).
• Build plate, preset to the plate on that model's first printer.
• Copies on one bed.
• Supports: automatic (where needed), always (tree) or never.

PrintSol keeps one slice per combination of these settings. When you print, it picks the slice made for that printer's model and plate, and slices afresh when there is none.

Smart slicing

• A 3MF project keeps the designer's quality settings (layers, walls, infill, supports, brim, ironing, seams) on top of the printer preset.
• A bare mesh (STL, OBJ) is laid flat and oriented, and with supports on automatic it gets tree supports where it needs them.
• If the slicer warns about an overhang, PrintSol slices again with tree supports.
• A process profile chosen for the part goes on top; an explicit always or never in the panel wins over everything.

Checking the result

Each slice has a Preview with the slicer's own plate render, a top view, and a layer-by-layer view of the gcode with supports, brim and layer height. If slicing fails, the panel shows "Last attempt failed" with the reason, and the Activity log has it too.

The model guard

PrintSol never sends gcode made for one model to another. Every start is checked twice, against PrintSol's own record and inside the file itself, for model, nozzle and plate. A mismatch is refused with the reason (a P1P slice is accepted on a P1S).