Repository navigation
How it works
objtools keeps geometry in files in a private disk workspace. It reads the source sequentially, then uses memory-mapped access to those files while building glTF. This allows a single object or primitive to exceed available RAM without holding the whole mesh on the heap.
Disk-backed conversion follows the pipeline from source parsing to final output. It explains which data stays on the heap, how memory mapping uses the operating system's page cache, and what consumes workspace disk space.
Resource usage comparison illustrates the practical tradeoffs against obj2gltf, Blender, glTF Transform and TexMetro. The methodology records the sample construction, commands and limitations.
The README describes the inspect command and its reported statistics. Texture occupancy calculation explains how sampled texels are counted, including filtering, UV transforms and wrapping, and how coverage maps stay on disk.
Development covers required checks, Khronos glTF validation, real-import memory monitoring and editing this wiki.