// the find
PanosK92/SpartanEngine
A game engine with a fully bindless, GPU-driven renderer featuring real-time path-traced global illumination, hardware ray tracing, and a physics simulation running at 200Hz, built over 10+ years of R&D
SpartanEngine is a Windows-only C++ game engine built by one person over ten years, focused on modern GPU rendering techniques rather than production usability. It's for graphics programmers who want to study or experiment with bindless rendering, ReSTIR GI, and GPU-driven pipelines in a codebase that actually works, not a tutorial project that stops at triangle rasterization.
The renderer architecture is genuinely rigorous: a single global vertex and index buffer, all per-draw data in one bindless storage buffer, one DrawIndexedIndirectCount per pass, with per-meshlet frustum and Hi-Z occlusion culling done entirely on GPU. That's the id Tech 7 school of thought applied consistently rather than selectively. The car physics goes embarrassingly deep for a general-purpose engine — Pacejka MF 5.2 with thermal tire models, roll center weight transfer, LSD differentials, and ABS, running at 200Hz inside the PhysX timestep. That's a dedicated racing sim physics stack. HLSL compiled to both SPIR-V and DXIL via a single shader source is non-trivial to get right and means you're not locked to one API. ReSTIR GI with spatiotemporal reservoir resampling for real-time multi-bounce path tracing is current state-of-the-art research implemented and running in a publicly available codebase, which is rare.
Bus factor is one, and the README is explicit about it: no support queue, no roadmap promises. If the author loses interest, this stalls. The build setup depends on Dropbox-hosted assets for the one-click experience — an external consumer file hosting service is load-bearing infrastructure, and that URL will eventually die. The 'ECS' appears to be a traditional component model with transform hierarchies rather than a data-oriented archetype ECS; if you're expecting cache-friendly iteration over large entity counts, the source code will disappoint you before the docs do. VR is marked WIP, there's no scene format anyone else uses, no export pipeline, and no notion of shipping a game — it's a renderer research vehicle, and adopting it for anything other than learning or graphics experimentation means building the production layer yourself from scratch.