How mhammerc/engine2 works
Core Systems Breakdown
• GBuffer Pass → Lighting Pass → Post-Processing
• ↓ ↓ ↓
• [Geometry] [Lighting Data] [Bloom, ACES Tone Mapping]
Component Relationships
Key relationships:
• Entity Component System (ECS)
• Entity → Components (Camera, Light, Material, Outline, Skybox)
• Resource Management System
• Cache Systems → [Mesh Cache, Texture Cache, Shader Cache]
Specific subsystems
a) Graphics Pipeline:
• Mesh Loading → Material System → Deferred Renderer
• ↓ ↓ ↓
• [Mesh Cache] [Shader Cache] [Framebuffers]
b) Editor Tools:
• Entity Editor → Scene Hierarchy → Property Inspector
• ↓ ↓ ↓
• [Transform] [Component List] [Material Editor]
Resource Flow
How assets are processed:
• Assets → Loading System → Cache Manager → Runtime Usage
• The deferred rendering pipeline as the core feature
• Component-based architecture using EnTT
• Clear separation between engine systems and editor tools
• Resource management and caching systems
• Debug/development tools integration
Keep the abstraction level high enough to show the overall architecture while including critical subsystems that make this engine unique, such as the deferred renderer, material system, and debug tools.
This structure reflects both the engine's technical capabilities (deferred rendering, shadows, bloom) and its development features (profiler, texture viewer, gizmos), making it valuable for both runtime and development understanding.