Multi-Format Ingest: Normalizing GLB / FBX / OBJ / STL into V1 Baselines
Why do mixed FBX, OBJ, and STL imports often appear rotated 90°, scaled 100× too large, or missing textures?
3D pipeline chaos often starts at intake: Blender uses Z-up while glTF/WebGL uses Y-up; CAD/STL uses millimeters while engines use meters; OBJ external `.mtl` paths break across machines. VECTOR normalizes FBX/OBJ/STL into self-contained GLB via Blender Worker and atomically writes an immutable V1 record.
The method: three small steps
Standardized intake requires three steps: 1. Format unification into binary `.glb` so textures stay embedded; 2. Transform normalization (Y-up axis, unit scale `1.0`, bottom-center pivot, verified metric bounding box); 3. SHA-256 hashing and atomic V1 registration so source bytes are never overwritten.
Transcode FBX / OBJ / STL into self-contained binary GLB
Pack meshes, materials, and textures into a single binary GLB via Blender Worker to eliminate broken external texture links.
Normalize Y-up orientation, apply Scale=1, and check Bounding Box
Fix 90° Z-up tilts, apply scale into vertices so Transform Scale is (1,1,1), and verify physical length/width/height in meters.
Commit SHA-256 checksum and immutable V1 baseline
Stream to disk, compute SHA-256, and atomically register V1 so the original intake asset remains permanently recoverable.
In the Multi-Format Ingest sandbox below, normalize axis orientation, metric scale, and V1 hash locking for the White Widebody Racer (c555ce1b).
Multi-Format Ingest & Bounding-Box Calibrator
A supplier delivers White Widebody Racer (c555ce1b) as a raw FBX (centimeter units, Z-up, unapplied scale). Select the intake pipeline.
Switch to the recommended VECTOR controlled pipeline option to resolve topology, UV, or QA gate errors.
Without format unification, applied transforms (Scale=1), and an immutable V1 hash, every downstream automated edit compounds coordinate errors.
Run it in the VECTOR 3D workbench or Blender pipeline
- Open a matching reference asset in the VECTOR 3D workbench or your Blender + AI pipeline.
- Copy the task sheet below, let AI generate an inspectable checklist or EditPlan first, and confirm before running mesh or material operations.
Why must a model’s Transform Scale be normalized to (1.0, 1.0, 1.0) before running automated bevels or sizing edits?
Explanations, cases, and exercises are authored by Reallier. Links provide further learning. The workplace activity and people are fictional.