Coaster Studio on Ercan Akyürek

Exporting a whole park as animated glTF

Mon, 10 Aug 2026 11:00:00 +0100

Coaster Studio can write a whole park into a binary glTF file: track, supports, train, cameras, the sun, and the ride itself as animation. That works because the exporter is not really an exporter, it is just another host.

The scene is the React style component tree from one core, two and a half engines, written in C++ on cppreact. Components build the park out of engine elements, a mesh, a camera, a light, and what such an element means is up to the host.

One core, two and a half engines

Mon, 10 Aug 2026 08:00:00 +0100

Coaster Studio runs on Unreal Engine 5 and on Google Filament, in the browser and on the desktop. Same application, same user interface. Two engines, and the glTF exporter as the half one, because it hosts the same scene without rendering a single pixel.

Everything that matters lives in one portable C++ core: math, curves, force vector design, physics, the data model, saving and loading, the scene and the whole user interface. A host only brings an engine, a window and the input.

The user interface, written once

Mon, 10 Aug 2026 07:30:00 +0100

The user interface of Coaster Studio is not written per host. It is C++ in the core, like everything else, and every host shows the same one. Not a rebuilt copy, the same components and the same stylesheets.

Here is the same toolbar, once in Unreal Engine 5 and once in the Filament build:

Unreal Engine 5

Google Filament