COB File Format Explained

What It Stores

The .cob (Caligari Object) format is TrueSpace's proprietary, compiled binary 3D container. It is used to store static 3D geometry, explicitly saving data such as vertices, polygon faces, UV texture coordinates, and basic material properties to define individual 3D assets.

Primary Use Cases

• Saving and loading individual, modular 3D assets quickly within the TrueSpace environment.
• Distributing and sharing standalone 3D models and props across the TrueSpace user community.
• Acting as the foundational geometric building blocks that are later assembled into larger scene (.scn) files.

Strengths

• The compiled binary structure results in highly compact file sizes compared to plain-text alternatives like .coa.
• Extremely fast read and write speeds when parsed by the native TrueSpace rendering and modeling engine.
• Preserves TrueSpace-specific material parameters, smoothing groups, and proprietary shading data accurately.

Limitations

• As a proprietary, closed-source format, it is notoriously difficult to reverse-engineer or open natively outside of the Caligari ecosystem.
• It is strictly a static object container and completely lacks the ability to store complex rigging, skinning, or keyframe animation data.

Common Software Support

Native support was strictly limited to Caligari TrueSpace and a few specialized, legacy 3D conversion suites like Okino PolyTrans or Deep Exploration. Today, the format is completely obsolete in modern digital content creation tools and requires specialized, community-built legacy plugins to import into software like Blender.

Additional Notes

The .cob format serves as a perfect example of legacy asset management, where 3D workflows relied on separating individual static assets from the master scene hierarchy. Artists would model static geometry as .cob files, but orchestrate, rig, animate, and render them within the overarching .scn container.