Why an image-generated GLB needs more than an STL export button

A textured 3D preview can look convincing while still being a poor input for a slicer. The preview answers whether an asset reads well on screen. A printable mesh also needs a deliberate scale, closed surfaces, consistent orientation and geometry that survives the chosen print process.

This development note comes from the Voxel3D example-asset pipeline. The starting assets were generated from reference images; the printable editions were prepared separately. For the earlier image-selection and generation steps, the 3d model from image guide provides the context. This post focuses on what happens after the GLB exists.

1. Validate the geometry instead of trusting the render

The first pass should produce a report, not silently alter the mesh. Here is a small check using Python, NumPy and Trimesh:

python -m venv .venv . .venv/bin/activate python -m pip install trimesh numpy 

# inspect_mesh.py import json import sys import numpy as np import trimesh mesh = trimesh.load(sys.argv[1], force="mesh") if mesh.is_empty or len(mesh.faces) == 0: raise SystemExit("No triangle mesh found") finite = bool(np.isfinite(mesh.vertices).all()) report = { "triangles": len(mesh.faces), "finite_vertices": finite, "watertight": bool(mesh.is_watertight), "winding_consistent": bool(mesh.is_winding_consistent), "volume": round(float(mesh.volume), 1) if finite else None, "extents": [round(float(x), 1) for x in mesh.extents] if finite else None, } print(json.dumps(report, indent=2)) if not ( finite and report["watertight"] and report["winding_consistent"] and report["volume"] > 0 ): raise SystemExit("Mesh needs inspection before printing") 

Run it against the file you intend to distribute:

python inspect_mesh.py explorer.stl 

For the prepared Trail Explorer STL in this project, the check returned:

{ "triangles": 99830, "finite_vertices": true, "watertight": true, "winding_consistent": true, "volume": 21507.8, "extents": [44.5, 31.8, 90.3] } 

Those extents are millimetres because the preparation pipeline deliberately scaled that mesh for millimetre-based printing. An STL file does not carry a dependable unit declaration: a different file needs its own scale check.

This is an automated geometry result, not a physical print test. It does not establish support placement, minimum wall thickness, tolerances or how a particular printer will reproduce the face and hands.

2. Make coordinate and scale decisions explicit

In this pipeline, the source GLB was loaded as a scene, its transformed mesh parts were collected, and the coordinates were converted from the glTF orientation to the printing orientation. Scaling happened before voxel reconstruction, so the voxel pitch had a physical meaning.

The important relationship is between the smallest feature you want to keep and the reconstruction pitch. A narrow connection that occupies too few voxels can disappear. Making the file smaller is a poor trade if it disconnects a hand from an arm or closes an opening in a terrain piece.

After any orientation or scale change, inspect the bounding dimensions and the contact with the build plate. A numeric validation pass cannot decide whether a character is facing the right direction or whether the base is useful for your intended print.

3. Reconstruct first, then smooth the mesh

One concrete failure in this project's conversion work was applying smoothing to a floating-point voxel field before extracting the surface. Thin connections could be lost, and degenerate geometry appeared in the resulting mesh.

The retained approach extracted a surface from the binary solid field, then applied Taubin smoothing to the mesh. A minimal illustration of that order of operations, using Trimesh’s default smoothing factors, is:

import numpy as np import trimesh from skimage import measure # `solid` is the prepared boolean voxel grid. # `pitch_mm` is the physical spacing chosen before reconstruction. vertices, faces, _, _ = measure.marching_cubes( solid.astype(np.uint8), level=0.5, spacing=(pitch_mm, pitch_mm, pitch_mm), ) result = trimesh.Trimesh( vertices=vertices, faces=faces[:, ::-1], process=True, ) if result.volume < 0: result.invert() result = trimesh.smoothing.filter_taubin( result, iterations=12 ) 

This illustrates the order of operations rather than reproducing the complete conversion script. It assumes the solid field has already been constructed and that pitch_mm has been selected for the model. It also requires scikit-image. The result still needs the checks from the first section; these settings are not a universal recipe for arbitrary meshes.

4. Put a guard around decimation

A triangle target is a budget, not a correctness condition. Some of the project's meshes retained internal cavity surfaces, and reducing the triangle count could open a seam. The pipeline kept the simpler candidate only when the basic geometry checks still passed:

candidate = result.simplify_quadric_decimation(face_count=120_000) if ( candidate.is_watertight and candidate.is_winding_consistent and candidate.volume > 0 ): result = candidate # Otherwise keep the previous mesh and record why the candidate was rejected. 

Trimesh's decimation backend requires its optional simplification dependency. Even when a candidate passes these checks, compare its silhouette and small details with the previous version. A closed mesh can still be the wrong shape.

5. Keep the preview and printing deliverables distinct

The browser preview, the full textured asset and the prepared STL have different jobs. A lower-weight GLB is useful for checking appearance without loading the largest file. The STL edition is geometry for a slicer and does not preserve the coloured appearance of the textured preview.

For the six example assets in this project, the preparation records keep each model's dimensions, triangle count and mesh-check results. That makes it possible to describe a download precisely and to distinguish a render from evidence of an actual print.

Before distributing your own file, inspect the slice layer by layer, choose supports for the printer and material, and revisit fragile features at the final scale. The useful deliverable is a model with known preparation steps and limits, rather than just a file with an .stl extension.

References and disclosure

• Trimesh documentation
• scikit-image marching cubes documentation
• Prusa: corrupted 3D models for printing

This post was drafted and published with AI assistance from the project's conversion source code and validation records. The inspection script was run against the prepared example STL. Model illustrations are digital renders, not photographs of a physical print.