1

HOME/USEFUL GUIDES/GUIDE TO 3D FILE FORMATS/SCN FILE FORMAT EXPLAINED

SCN File Format Explained

The .scn (Caligari Scene) format is TrueSpace's master container. It stores the complete scene graph, including lighting, cameras, skeletal hierarchies, rigging, and keyframe animations, linking individual .cob assets into a final scene.

	Icon	Extension	Original Software	Year	Primary Industry	Geometry	UV Maps	Textures	PBR	Animation	Rigging	Open Use
		.SCN	TrueSpace	1994	Game Development Architecture Product Visualization	None	–	–	–	–	✔	–
SCN File Format Details What It Stores The .scn (Caligari Scene) format is TrueSpace's master scene container. Unlike formats that only hold geometry, .scn stores the complete scene graph, encompassing multiple 3D objects, lighting setups, camera positions, hierarchical linking, skeletal rigging data (bones and IK constraints), and keyframe animation tracks. Primary Use Cases Saving fully composed 3D environments and complex multi-object scenes. Storing comprehensive character animation data, including skeletal rigs, skinning, and keyframe timelines. Preserving render settings, global lighting rigs, and animated camera paths for final rendering output. Strengths Acts as a comprehensive container capable of holding every element required for a final rendered image or animation sequence. Accurately retains TrueSpace's proprietary Inverse Kinematics (IK) solvers and vertex weighting for character rigs. Utilizes an efficient binary structure optimized for loading complex scene hierarchies and animation data natively within the software. Limitations Deeply coupled with TrueSpace's internal memory state, making it incredibly difficult to export animated, rigged characters to other 3D applications. Highly proprietary structure that is completely inaccessible and unreadable without specialized conversion software or TrueSpace itself. Common Software Support Native support was virtually exclusive to Caligari TrueSpace. Because it stores complex, proprietary scene graphs and mathematical solvers rather than just raw geometry, third-party support was extremely rare. Even professional conversion tools of the era, such as Okino PolyTrans, often struggled to translate .scn rigging and animation data without breaking the hierarchy. Additional Notes The .scn format perfectly illustrates the "walled garden" architecture of 1990s 3D software. By tightly coupling geometry, rigging, and animation into a single, highly complex proprietary file, Caligari ensured optimal internal performance but inadvertently created massive interoperability bottlenecks for artists trying to move assets into early game engines or competing pipelines.