How painfulexistence/atmosphericengine works
Project type and purpose
• The project is a game engine aimed at 3D graphics, physics, audio, and more. It is structured as a full‐engine core (located in the AtmosphericEngine directory) with several example applications (HelloWorld, Terrain, MazeWorld, Breakout2D) demonstrating its use.
• The README emphasizes graphics programming, PBR texturing, dynamic terrain tessellation, job system, and debug UIs, indicating that the engine subsystems are tightly coupled yet modular.
File structure to pinpoint the main architectural components
• The AtmosphericEngine folder holds the core engine code. Within this folder, you have headers and source files for major subsystems such as:
• Application (application.cpp/.hpp)
• Asset Manager (asset_manager.cpp/.hpp)
• Audio Manager (audio_manager.cpp/.hpp)
• Graphics/Rendering (camera, shader, graphics_server, renderable, window)
• Physics (physics_server, bullet_*, physics_debug_drawer)
• Input (input.cpp/.hpp, keyboard.hpp)
• ECS (ecs_server, entity, component, and integration of the external entt library)
• Job system (job_system.cpp/.hpp)
• Miscellaneous systems like messaging (messagable#, message_bus, message) and debugging/console
• Utility modules (file handling, math utilities such as frustum, etc.)
• There is also a “default_assets” folder for shaders, textures, and other built-in assets.
• The external folder includes third-party dependencies (entt, imgui, nlohmann, raudio, sol2, stb) that the engine uses to power various subsystems.
External components and build configuration
• CMake files, the vcpkg directory, and Docker-related files indicate an emphasis on cross-platform support and containerized/devcontainer-based setups.