How thattanishqtak/3d-renderer works
Project type and purpose
• This is a native C++ 3D‐renderer engine (“Trident”) plus an editor/sample application (“Trident-Forge”).
• Trident implements the core engine subsystems (windowing, event dispatch, ECS, rendering, resource loading, UI, AI integration). Trident-Forge sits on top as an application layer that loads assets and exercises the engine.
File structure
• Top-level:
• CMakeLists.txt / cmake/ – build configuration, external dependency management
• Scripts/ – helper scripts for building on Windows
• Trident/ – the engine library: organized into src/{AI, Application, Core, ECS, Events, Geometry, Layer, Loader, Renderer, UI, Window, vendor}
• Trident-Forge/ – editor application: Assets (models, shaders, fonts), CMakeLists.txt, src/{EntryPoint, ApplicationLayer, Panels}
• Key patterns:
• Layered architecture: ApplicationLayer → Engine Core → Renderer / ECS / Loader / UI / Window
• ECS (Entity, Components, Systems) for scene management
• Renderer subsystem built around command buffers, pipelines, swapchains
• UI subsystem uses ImGui via an ImGuiLayer
• Loader subsystem uses Assimp and stb for assets
• AI subsystem using ONNX Runtime