Output Mesh File

2 VersionsOutput

Exports each upstream Mesh to a 3D geometry file under output_path, choosing the container from format (obj, stl, ply, gltf, glb). Each call writes its own file named from name_template plus a 6-digit index.

How it fits

Typical backends

Asset capture. Load a source mesh, run a geometry transform, and write the result to disk in a chosen container type.

Reconstruction sink. Stand in a reconstruction stage that produces mesh geometry and persist every frame's mesh for later inspection.

Caveats

I/O contractA leading dot on format is stripped; the container is one of obj, stl, ply, gltf, or glb, and any other value is rejected when the backend is built.
CompatibilityWhich attributes survive the round-trip depends on the chosen container — STL keeps neither vertex colours nor UVs, PLY preserves colours, and glTF/GLB carry normals, colours, and UVs.
I/O contractVertex colours, normals, and UVs are only written when their counts match the vertex count; mismatched attribute arrays are silently omitted from the export.
I/O contractA mesh with no vertices or no faces produces a zero-byte placeholder file instead of a valid model; downstream readers must tolerate empty files.
State lifetimeThe filename index is a process-local counter that resets on restart, so reusing output_path across runs overwrites earlier files unless name_template also varies.

Versions

bf5b8713default
Automated release
8/1/2026