A modular C++20 game engine I'm building in my free time, with a separate editor and runtime.
Early development. The project is just getting started. Right now it is mostly the foundations. Build system, module layout and core utilities. There is nothing to run yet beyond the sandbox.
My first engine, ArtFX Game Engine, taught me how physics, rendering and gameplay code fit together. It also showed me what happens when an engine grows without a clear structure. A single Visual Studio project, modules depending on each other freely, and no tooling to see what the code is actually doing.
LoomEngine is a fresh start with those lessons in mind. The focus is on getting the foundations right before adding features. Clear module boundaries, a reproducible build, and profiling from day one.
The engine is split into modules, each built as its own CMake target:
| Module | Role |
|---|---|
Core |
Base types, memory, logging, smart pointers. Depends on nothing else in the engine |
Platform |
Abstraction over the OS: window, input, file system |
Engine |
The engine itself, built on top of Core and Platform |
Runtime |
Entry point for shipped games |
Editor |
Entry point for the editor, optional |
Sandbox |
Test project used during development |
Dependencies only go one way, from the top of the stack down to Core, which keeps each layer testable and replaceable.
Inspired by Unreal's build setup, the engine has three configurations:
| Configuration | Purpose |
|---|---|
Debug |
No optimizations, full debug info |
Development |
Optimized with debug info, the default when working |
Shipping |
Fully optimized, editor excluded |
Tracy is integrated in Core, including memory allocation tracking, so performance and memory usage can be inspected from the very first features.
Requirements: CMake 4.3+, Ninja, and a C++20 compiler (MSVC, Clang or GCC).
git clone https://github.com/IjulienI/LoomEngine.git
cd LoomEngine
cmake --preset development
cmake --build --preset development
Use the debug or shipping presets for the other configurations. Dependencies are downloaded automatically by CMake on the first configure.
- Modular CMake structure with Debug / Development / Shipping configurations
- Third-party dependencies fetched automatically
- Tracy integration with memory tracking
- Logging system
- Platform layer: window and input on SDL3
- Main loop and engine lifecycle
- First renderer
MIT. See LICENSE.