ZSLICEDOCS

Internals

zslice and other slicers

zslice is a new slicer, written from scratch. Cura, PrusaSlicer, OrcaSlicer, and Bambu Studio are mature slicers with many years of work and large teams. This page says what zslice does that they do not, what they have that zslice does not have yet, and how the main features compare.

The other slicers change with each release. If a line here is out of date, open an issue.

What makes zslice different

What zslice does not have yet

See the roadmap for the plan.

The main features

"Yes" means that the slicer has the feature in its main release. "Some" means a part of it, or a plugin.

FeaturezsliceCuraPrusaSlicerOrcaSlicerBambu Studio
Explains each line of the preview (real speed, why)YesNoNoNoNo
Slices again while a slider movesYesNoNoNoNo
Runs in a web browser, files stay localYesNoNoNoNo
Gaps view with settings that close each gapYesNoNoNoNo
History of changes with a timelineYesNoNoNoNo
Embeddable library with a C APIYesSome (CuraEngine program)NoNoNo
Variable line width walls (Arachne)YesYesYesYesYes
Tree supportYesYesYesYesYes
Support blockers and enforcersYes (marks)YesYes (painted)Yes (painted)Yes (painted)
Bridges detected and printed as bridgesYesYesYesYesYes
IroningYesYesYesYesYes
Settings for each part, modifier volumesYesYesYesYesYes
Settings for some layersYesSomeYesYesYes
Automatic orientation and arrangementYesSomeYesYesYes
Printer library with bed modelsYesYesYesYesBambu printers
Send to printer (OctoPrint, Moonraker, own)YesSomeYesYesBambu printers
Measure toolOn the sliced linesNoOn the modelOn the modelOn the model
Multi-material and colorNoYesYesYesYes
Variable layer heightNoYes (adaptive)YesYesYes
Arc fittingNoSomeYesYesYes
Calibration printsNoSomeSomeYesYes
Resin printersNoNoYesNoNo
LicenseAGPL-3.0LGPL-3.0AGPL-3.0AGPL-3.0AGPL-3.0

Testing against CuraEngine

tools/compare_cura.py slices a folder of STL files with zslice and with CuraEngine, with the same main settings, and compares the results: failures, time, memory, and the print time and the plastic of each part. CuraEngine is a test oracle; no Cura code is in zslice (see REFERENCES.md).

zig build -Doptimize=ReleaseFast
python3 -I tools/compare_cura.py run zig-out/bin/zslice <out folder> --root <folder of STL files>
python3 -I tools/compare_cura.py summary <out folder>
python3 -I tools/compare_cura.py check model.stl
python3 -I tools/compare_cura.py walls zig-out/bin/zslice model.stl <out folder>

walls compares the walls of one model: the wall paths and volume of each slicer, and the line widths of the Arachne walls. The script needs CuraEngine (the Cura AppImage, extracted) and a Cura printer definition; see the header of the script. Use it to find the parts where zslice fails, is slow, uses much memory, or gives a print far from the Cura print.

Testing support

tools/support_check.py checks the support of a sliced part, and compares the support of zslice, CuraEngine, and OrcaSlicer on the same parts.

python3 -I tools/support_check.py parts zig-out/scratch/parts
python3 -I tools/support_check.py check model.stl model.gcode --png model.png
python3 -I tools/support_check.py review zig-out/support-review zig-out/scratch/parts --zslice new=zig-out/bin/zslice --cura --orca

The check cuts the mesh at each layer and draws the support lines of the G-code into a grid of 0.1 mm cells. An overhang cell is a cell under a face of the mesh that looks down and leans more than 50 degrees from vertical. The check reports the overhang area with no support line within 1.5 mm in the 3 layers under it (unsupported), the support lines with nothing under them (floating), and the support volume. review slices each part with grid and tree support, and writes a picture of each slice (front, side, and top view) and an index.html with a table. OrcaSlicer needs the profiles machine.json, process.json, and filament.json in <out folder>/orca; see the header of the script.