Self Intersections and Non-Manifold Edges Are Different Checks

A non-manifold edge concerns how faces are connected. A self intersection concerns where surfaces cross in space. A mesh can pass an edge-incidence check while its triangles still intersect. InspectMesh collection review does not detect self intersections. Local STL preflight runs a bounded BVH screen; zero non-manifold edges alone must not be presented as an intersection clearance.

Two independent questions

Boundary edges have one incident triangle; an ordinary closed-surface edge has two. The collection non-manifold edge count flags more than two. Broader manifoldness also includes vertex neighbourhoods, so passing this edge-only screen is narrower than proving a manifold solid.

Reproduce the crossing-shell counterexample

Download two overlapping closed cubes. Each is 20 mm wide; the second is translated 10 mm on X. Expected combined bounds are 30 × 20 × 20 mm, with two connected shells and zero boundary or over-shared edges after exact-coordinate welding. The surfaces intersect even though these counts are zero. The collection report withholds volume because shell interpretation is unresolved.

Local STL preflight can report triangle pairs for supported files up to its documented triangle limit. The reported location is an approximate pair centre, not an exact intersection curve or a 3D highlight. Exact duplicate and coplanar overlaps are labelled ambiguous. Larger, malformed or resource-limited inputs are skipped or incomplete, never reported as a clean check. The screen is diagnostic; it does not infer whether to union shells, preserve a cavity or retain separate parts. Duplicate removal cannot resolve a crossing between unrelated triangles merely because their faces occupy some of the same space.

Practical inspection sequence

1. Run collection review and retain topology counts and method limits.
2. Inspect the crossing region in the viewer or a mesh editor. A cross-section can reveal interior surfaces but is a visual aid, not an exhaustive test.
3. Check the native CAD Boolean/assembly intention: union, separate movable parts or an internal cavity?
4. Use a source-CAD solid or mesh editor with an explicit intersection check when required; review that tool/version’s limitations.
5. Export a corrected copy, compare revisions and inspect the affected slicer layers.

Stop before guessing the intended solid

If union would close a deliberate cavity or merge separate moving pieces, ask the designer. A successful slice is evidence of that slicer’s chosen interpretation, not proof that it matches intent. Return to CAD when the crossing involves functional surfaces or a missing Boolean result.

The non-manifold explainer classifies connectivity patterns; the repair guide chooses a corrective workflow. This page separates the diagnostic tests. The 3MF mesh requirements provide a normative solid-mesh reference, reviewed 7 October 2026. Fixture outcomes come from owned geometry tests, not physical prints.