How livinamuk/hell2025 works
Project Type and Purpose
• Hell2025 is a standalone C++ real-time game engine with an integrated level editor.
• It supports both OpenGL and Vulkan back-ends, physics via PhysX, audio, scripting (Python), and an ImGui-based editor.
• Primary use case: splitscreen roguelike/deathmatch survival horror.
a. Platform & Windowing
• GLFWIntegration (window creation, input callbacks)
• Main loop (Main.cpp → Core/Game.cpp)
b. Graphics API Layer
• OpenGL backend (src/API/OpenGL/…)
• Vulkan backend (src/API/Vulkan/…)
c. Renderer
• RenderPasses & ComputePasses (deferred G-buffer, lighting, post-processing)
• GlobalIllumination (custom compute shaders)
• Renderer utilities & Resource binding
d. Asset Management
• AssetManager (meshes, textures, animations)
• BakeQueue (asynchronous asset pre-processing)
• File importers (AssimpImporter)
e. Physics
• PhysX wrapper (src/Physics/Types + Physics_*.cpp)
• Collision, character controllers, ragdolls
f. Audio & MIDI
• Audio subsystem (WAV, MP3 playback)
• MidiFileManager & Synth
g. Game Logic & World
• Player & Entities (Enemies, Allies)
• World/Sector/Map/House managers
• Pathfinding (AStar, NavMesh)
• BVH structures (CPU/GPU)
h. Editor (ImGui front-end)
• Editor UI & tools (placement, heightmap, sectors)
• Gizmo, ObjectPlacement modules
i. Utilities & Tools
• JSON, Config, Util_* (math, file, debugging)
• Python scripts (Blender model exporters)
j. External Libraries
• GLFW, PhysX, Assimp, ImGui
• At startup: Config → BackEnd (GLFW) → choose API (OpenGL or Vulkan)
• AssetManager loads files → sends GPU resources to Renderer → shaders invoked via API
• Main loop:
• Input → Player & Editor
• Update: Game logic → Physics → World managers (BVH, pathfinding)
• Audio subsystem ← events from Game/Player
• Editor UI overlays on Render output and can modify World Managers in real time.
• Python scripts are invoked offline to prepare assets.
Architectural Patterns and Principles
• Manager pattern: single-responsibility managers for each resource type (AssetManager, MapManager, etc.).
• Modular back-ends: Abstract API interface with two interchangeable implementations.
• Data-driven: JSON configuration for maps, sectors, houses, fonts.
• Pub/Sub via Callbacks for cross-subsystem events (e.g., input, physics contact callbacks).
• Job queue for asset baking, allowing asynchronous pre-processing.
Essential Details to Capture
• How the Main Loop orchestrates Input → Update → Physics → World → Render → Audio.
• Editor’s connection into the same core loop but injecting UI events and scene changes.
• Resource-loading flow from disk (JSON, meshes, textures) through AssetManager into GPU memory.