Game engines

CAD files, opened at runtime

The same reader and the same B-rep sit under every engine below. What changes is how each one turns that tree into pixels.

Available

Godot

A GDExtension for Godot 4.4 and later: CAD files import as scenes or open at runtime, and the kernel builds solids in GDScript.

Godot →
Available

LÖVE and LÖVR

LÖVE (aka Love2D) and LÖVR, through the SDK's LuaJIT wrapper: read files, build solids, draw them in 2D, 3D or VR.

LÖVE and LÖVR →
Work in progress

Unity

A package over the same C ABI, in the works.

Unity →
Unreal Engine 5.8

Unreal Engine

A plugin that opens CAD files at run time, in the editor and in a packaged game, drawn from triangles or from their exact surfaces.

Unreal Engine →
The web viewer with the nut open and its tree beside it
Browser

One HTML file, no bundler

wasm in a Web Worker, drawn with WebGPU; nine formats; the file is read and tessellated locally and never uploaded.

Open the web viewer →

Your own engine

One ABI under all of it

The engine integrations are thin: one C ABI, as a shared or a static library, opens a file, walks its parts and hands over their meshes and exact surfaces. Any engine with a C boundary can do the same; wrappers for Python, C#, Go, Java, Node.js, Rust, Swift and LuaJIT ship with the SDK. The same viewer is also a free desktop and mobile app.

Status

The C ABI and its wrappers ship: the SDK at github.com/rdeioris/cadaclysm-sdk, free to build and test with, licensed per product, server or website when they run in production. The Unreal plugin is free on Fab; the Unity package, free as well, is coming to the Unity Asset Store. A game or app shipped with either needs a product license, and a server running it a server license. The Rust wrapper is on crates.io as cadaclysm-sdk, over the same proprietary libraries.

Also today: open a file in your browser, sketch and build in the forge, and write to us at info@blitter.studio about the plugins.