Slicing: how geometry becomes machine behavior

01

Geometry must become regions

A slicer first needs a valid representation of the object and build coordinate system. It intersects the model with layer planes or otherwise evaluates the volume to determine what belongs in each manufacturing layer. For mesh-based workflows, holes, self-intersections, flipped triangles, overlapping shells, or ambiguous zero-thickness features can cause missing regions or unwanted repairs. The safest fix is usually to correct the authoritative model, not repeatedly patch exported meshes.

Model orientation changes the cross-sections the slicer sees. It determines the footprint, height, overhangs, support access, stair-stepping direction, and—on many processes—the direction of interfaces between layers. Units and transforms also matter. The 3MF core specification explicitly defines units, coordinate systems, meshes, components, and transforms so that a package can carry more manufacturing context than a bare triangulated surface ².

• Confirm scale and units.
• Inspect whether every intended wall has printable thickness.
• Resolve intersecting or disconnected bodies intentionally.
• Orient for function, support access, surface priority, and process stability.

02

Regions become paths and process states

For material extrusion, the slicer commonly creates outer perimeters, inner walls, top and bottom surfaces, sparse or solid infill, support structures, skirts or brims, and travel moves. It assigns extrusion widths, layer heights, temperatures, cooling, acceleration, retraction, and speeds. A resin build processor creates images or scan vectors, exposure schedules, lift and peel motions, supports, and transition layers. Industrial systems may also schedule recoating, hatching, contour passes, energy settings, gas-flow considerations, and multi-material operations.

These settings are not independent knobs. Increasing layer height changes bead geometry and the number of interfaces. Speed, acceleration, available melt or cure energy, material delivery, cooling, and path curvature constrain one another. A nominal volumetric flow that exceeds the hot end’s capability can under-extrude even when the commanded line width looks reasonable. Conversely, slowing every move can increase heat accumulation or change cooling behavior. A process profile is a coupled recipe.

03

Motion planning changes commanded motion

Generated instructions describe desired actions, but firmware must turn them into physically achievable motion. Marlin documents a chain from G-code to segmented moves, a planner queue, and timed stepper interrupts. The planner considers acceleration and direction changes because a machine cannot instantaneously reach commanded speed or reverse momentum ¹. Kinematics, bed-level compensation, and curve approximation can split one high-level command into many smaller moves.

This distinction explains why two machines executing similar-looking paths can behave differently. Frame stiffness, moving mass, belt or screw mechanics, drive current, control-loop timing, resonance compensation, pressure advance, and firmware limits influence the actual bead placement. The slicer and machine controller share responsibility: the slicer proposes a trajectory and process state; the controller schedules that request within configured physical limits.

• Travel speed is not the same as achieved speed on a short move.
• Acceleration and cornering rules affect ringing, time, and pressure changes.
• Very small segments can burden planning and create uneven motion.
• Firmware limits may override or constrain slicer commands.

04

Preview is a manufacturing review

Never treat successful slicing as proof of a good job. Inspect the preview layer by layer. Look for missing walls, isolated islands, unsupported starts, unstable support towers, abrupt changes in cross-section, trapped powder or resin, long bridges, excessive tiny segments, seams on critical faces, unintended material assignments, and collisions or out-of-bounds moves. Prusa’s troubleshooting guidance specifically recommends reviewing generated G-code and model warnings when diagnosing failed prints ³.

Estimates also deserve skepticism. Time prediction depends on whether the slicer models acceleration, heating, tool changes, recoating, curing, cooling, and machine-specific pauses. Material estimates may omit purge, support, failed setup, or downstream waste. Use them for planning and comparison, then calibrate estimates against actual recorded builds.

• First layer and adhesion footprint
• Each new island and overhang
• Support contact and removal route
• Top surfaces and closure over sparse infill
• Tool changes, purges, pauses, and temperature transitions
• Final machine envelope and clearance

05

Release the job, not just the file

Before execution, bind the instructions to the intended machine, material, setup, and model revision. A G-code file may include temperatures and movements tailored to one printer; executing it elsewhere can be unsafe. Preserve the prepared project so another person can inspect the orientation, modifiers, supports, and profile choices that produced the output. Record slicer version because algorithms and defaults change.

For production, the release package should define who approved the build, the required setup verification, allowable substitutions, inspection plan, and response to interruption or deviation. NIST’s systems-integration work emphasizes the need for common representations and linked stages across product realization ⁴. Good slicing is therefore both geometry processing and configuration management.