Development history
How the engine and editor arrived at their current shape. This page is a historical index, not a status report: phase labels and "planned" markers describe the plan at the time, not today's implementation.
Current status lives elsewhere. Use the documentation index and the module pages for what exists now. For release notes, see Changelog.
Timeline#
| When | Milestone | Record |
|---|---|---|
| Foundation | Fixed-width types, allocators, containers, vectors/matrices and the first Catch2 suites. | Core types, Allocators, Math |
| Runtime base | Timer, fixed-step game loop, job system, input and debug tooling. | Game loop, Job system, Debug tools |
| RHI and 2D | SDL3 GPU abstraction, batch renderer, 2D camera, asset manager and the CAF format. | RHI, Batch renderer, CAF format |
| ECS and systems | Archetype ECS, scene stack, events, physics, animation, audio and the retained UI. | ECS, Physics 2D, Audio |
| 3D transition | Quaternions, mesh loading, 3D camera, spatial partitioning, skeletal animation. | Quaternions, Camera 3D, Spatial partitioning |
| Doppio | From the ImGui C++ editor to the Rust/Iced workspace, the five-pane layout and the C ABI boundary. | Scene editor, Rust UI notes, UI test framework plan |
| Rendering push | PBR, HDR post-processing, TAA, shadows, reflections, volumetric lighting and GPU readback viewport. | Rendering roadmap, Forward PBR session, PBR materials |
| Content tools | Material Generator, Texture Generator, Texture Set painter, Nature, Water and Terrain generators. | Material pipeline, Texture guide, Terrain guide |
| Headless testing | Scripted UI flows, annotated screenshots, baselines and GIF/MP4 recording with no window. | Headless driver, Test automation |
Planning tracks#
| Track | Pages |
|---|---|
| Fundamental pillars | Engine pillars roadmap |
| Rendering | Rendering roadmap |
| Editor milestones M1–M4 | Milestones |
| Terrain module plan | Terrain milestones |
| Session archive | Archive |
Conventions that survived#
- Data-oriented design — contiguous component storage, cache-friendly iteration.
- No RTTI, no exceptions on hot paths — errors are return values.
- Custom allocators — no loose
new/deletein engine code. - C ABI for frontends — the editor is replaceable; Doppio is one frontend.
- Tests for behaviour — Catch2 for the engine, headless flows for the editor.
Full commit history#
The chronological record is the Git history of the repository. Release-level notes
live in Changelog; session notes under plans/ capture the
reasoning behind larger changes.