When a split doesn’t go as expected (missing parts, or printer-volume cubes unexpectedly added to the Workzone),
it is almost always a geometry integrity issue in the source STL.
Below is a quick diagnostic and fix guide.
1 - One or more split parts are missing.
2 - Extra bounding cubes (printer volume) appear in the Workzone.
3 - Split Time is very long !
Edges shared by >2 faces, bow-tie vertices, or “T-junctions” : the mesh isn’t a proper solid.
Missing triangles leave gaps : the model is not watertight.
Parts of the mesh penetrate each other: boolean ops become ambiguous.
Face directions disagree : inside/outside flips, confusing solid detection.
Surfaces with no volume : valid for rendering, invalid for solid boolean operations.
Zero-area triangles, duplicate faces, duplicate vertices : numeric instability.
Tiny floating islands or unintended internal shells : unexpected extra parts.
Faces lying exactly on top of each other : boolean ambiguity at split planes.
Model 1000× too big or too small : extreme coordinates can break tolerances.
Features thinner than tolerance collapse after triangulation
If you haven’t repaired yet: run the Repair command of Split3r on the original file, then do Pre-Split > Split again.
Split3r’s math engine uses Blender 4.5.3. If the in-app repair fails, the file is likely too corrupted for direct processing.
Re-import the repaired STL into Split3r.
Run Pre-Split > Split.
Verify all parts appear, and no extra cubes are injected.
As a last resort, ZIP your entire Workzone (original STL, .s3r file, repaired STL, project/session, outputs results) and submit it via the ReportBug page.
We’ll analyze it with our internal tools.
Original and repaired STL(s), .s3r file, results folders... Everything existing in the Workzone
Your environment (Windows version, Split3r version, CPU/GPU)
We’ll get back with targeted guidance or a fixed mesh if feasible.