Skip to content
Novus Examples
glb1.6 MB

A av m4: reconstructed mesh (GLB)

A single-image 3D reconstruction of head and shoulders portrait of a south asian man in his fifties, written as binary glTF, geometry addressed through an accessor table. Its twin in this group is the same mesh written as the other format, from ONE reconstruction rather than two runs - so the pair tests whether a reader returns the same geometry from two containers with nothing in common. Both hold 28,536 vertices and 57,064 triangles; those counts were read from the GLB's accessor table and by counting lines in the OBJ, by separate code, and a disagreement would have stopped this shipping. It is closed: every edge belongs to exactly two triangles, so there are no holes and no non-manifold edges. The bounding box measures 0.3191 x 1.0247 x 0.8981 units.

Loading 3D preview…

Specifications

Vertices
28536
Triangles
57064
Boundary Edges
0
Non Manifold Edges
0
Container
GLB
Role
pair-member
Pair Format
obj
Model
TripoSR (MIT), marching cubes at detail 128
Cutout
BiRefNet background removal, applied before reconstruction
Detail
128
Surface Threshold
25
Object Fills
0.85
Source Plate
nss-a-av-m4_00001_.png
Bounding Box Extent
0.3191 x 1.0247 x 0.8981
Synthetic
true
Disclosure
Reconstructed from an AI-generated plate. Synthetic geometry, not a scan of a real object.
Schema Version
1

Testing contract

Expected to pass
Scenario
Load this file and its OBJ twin in the same pair, then compare vertex count, triangle count and bounding box between the two.
Expected result
Both report 28,536 vertices and 57,064 triangles over a bounding box of 0.3191 x 1.0247 x 0.8981 units, because they were written from ONE reconstruction rather than two runs. That is the check worth making: a reader that drops vertices, re-triangulates a face or flips an axis still returns a file that loads and still looks like the object, and only a second encoding of the same geometry exposes it. Every edge belongs to exactly two triangles, so the surface is closed: no holes, no non-manifold edges.

What is a .glb file?

GLB is the binary form of glTF, packaging 3D scene geometry, materials, textures, animations, and node hierarchy into a single self-contained file. It is optimized for efficient runtime loading and is often called the JPEG of 3D. It is widely used in web, AR, and real-time 3D applications.

How to use this file

Use an example GLB to test glTF loaders, embedded-texture and animation handling, and real-time rendering pipelines in web or game engines.

How to use this file for testing

“A av m4: reconstructed mesh (GLB)” is a deterministic Novus Examples fixture for Mesh processing QA. Deterministic GLB meshes with known geometry and triangle counts for regression-testing mesh import/export, decimation, repair, and validation pipelines.

Documented properties for this file: pair-member. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

3D and CAD fixtures carry one small, documented solid or scene. Convert and inspect against the known geometry, units, and structure; format twins let you diff interchange fidelity, and the 3D viewer previews the actual mesh.

Code examples

import trimesh  # pip install trimesh

mesh = trimesh.load("a-av-m4.glb")
print(mesh.bounds, mesh.faces.shape)

Generated by generation/comfy_tripo_wave.py. Free for any use, no attribution required, license.