Every reader produces the same thing: a tree of nodes with a name, a placement and a B-rep, whatever the file called them. STEP's assembly graph and IFC's storeys land in the same tree the Rhino blocks do.
| File | Standard | What is read | Status |
|---|---|---|---|
| .step .stp | ISO 10303 AP203 / 214 / 242 | The assembly graph, product names, colours, and the geometry each part carries | shipping |
| .ifc | IFC 2x3 / IFC4 | The building's spatial tree, placements and openings, over the same STEP reader | shipping |
| .3dm | Rhino | B-reps, blocks, layers; trims re-fitted to the face they sit on | shipping |
| .igs .iges | IGES 5.3 | The five card sections, the directory, meshes from trimmed NURBS | shipping |
| .brep .brp | OCCT | The geometry tables and the shape tree above them | shipping |
| .sat | ACIS (text) | The record stream, the topology, analytic and spline surfaces | shipping |
| .scad | OpenSCAD | The language, interpreted and evaluated to meshes | shipping |
| File | What | From |
|---|---|---|
| .step | ISO 10303 AP203, exact B-reps | The blacksmith: what you built, or a solid read from any format above |
| .stl | Binary or ASCII triangles | Any node's mesh, at the tolerance you ask for |
| .glb .gltf | glTF 2.0: the whole scene, the tree, a material per colour | A document, Y-up and in metres as the format specifies |
| .obj | Wavefront OBJ: every placement a named object, an .mtl beside it for the colours | A document, baked into world space; or any node's mesh |
| .msh | Gmsh mesh | Any node's mesh, for meshing and simulation tools |
Names in an encoding the file never declared — CP1251 in a SAT, IGES or STEP export — are detected from the text itself, and reported as the guess they are. In the browser the file is read and tessellated locally; it is never uploaded.
The two libraries ship: the SDK at github.com/rdeioris/cadaclysm-sdk fetches them for your machine, licensed per seat or per server. The Unreal plugin and the Unity package are not on their marketplaces yet; the crates are proprietary and not on crates.io.
What you can do today: open a file in your browser (the forge runs from the repository), and write to us at info@blitter.studio about the plugins or a kernel licence.