PROJECT AT A GLANCE
Project scope
Engine architecture · Rendering · Editor tooling. Individual responsibilities are not yet documented.
A small engine with explicit boundaries
Arcglass Engine is a Windows game-engine prototype in C++20. Its repository separates core utilities, the Win32 platform layer, a Direct3D 12 rendering interface, world and asset modules, a standalone runtime and a custom editor. The screenshot above is from the editor launched from the fresh local build.
What I verified
On 14 November 2026 I configured and built the Windows x64 MSVC Release preset, launched the editor on a GeForce GTX 1660 SUPER, and ran CTest. Its one registered target passed. That is useful evidence that this checkout builds and its registered test runs; it is not evidence of complete subsystem coverage or production readiness.
The editor title shows its own frame indicator. I did not measure frame time, GPU time or throughput during this check. Earlier performance figures in planning documents have not been reproduced and are not presented as current results.
Architecture and limits
The repository contains CMake targets for core, platform, RHI, world, assets, renderer, runtime and editor. A native test executable exercises selected modules. Some systems, such as renderer utilities, CPU-side physics and animation, remain isolated or are covered only at unit level. The project does not yet provide a complete asset-to-game pipeline or a finished production editor.
The screenshot and architecture notes are useful for discussing subsystem boundaries, build setup and the difference between a compiled module and an end-to-end feature. They are not a claim that every listed subsystem is active in the shown frame.
Source and build
The public repository includes the CMake presets, CI workflow, source, shaders and a repeatable technical demo guide. It is licensed MIT for original source code; third-party dependencies and assets retain their own terms.
Evidence record
The project capture and documented stack were migrated from the original portfolio.Individual ownership boundaries, testing history, failure reports and benchmark measurements have not been supplied.
System diagrams on this page describe documented capabilities. Profile and Source state explicitly which supporting materials are available.
Continue exploring
Browse the project archive or run an engineering experiment.
