How ozawataiki/gameengine works
Project Type and Purpose
• This is a native C++ DirectX-based Game Engine with an accompanying Sample application and Python-based level‐editor tools.
• It exposes a modular engine core (windowing, rendering, debug), cross‐platform subsystems (audio, input, timing, math, utilities), a feature layer (collision, model, lighting, post-effects, UI, etc.), external libraries (Assimp, DirectXTex, ImGui, stb, nlohmann::json), and resource assets (shaders, models, textures, sounds).
File Structure Analysis
Top-level modules:
• Engine/Core: low-level DXCommon (device/PSO/SRV/RTV managers), WinApp (window/message loop)
• Engine/System: OS/event subsystems (Audio, Input, Time)
• Engine/Framework: application framework, batch renderer, layer system
• Engine/Features: domain features (Animation, Camera, Collision, Effect, Event, Json, Light, Model, PostEffects, Scene, Sprite, TextRenderer, UI, UVTransform, WaveformDisplay)
• Engine/Math: linear algebra, random, easing curves
• Engine/Utility: string/file-dialog helpers
• Engine/Debug: ImGui integration, leak checker, helpers
• Engine/Externals: 3rd-party libs and their build artifacts
• Engine/Resources: HLSL shaders and asset pipelines
• Sample: a demo project consuming Engine as a library
• Tool/level_editor: Python scripts for scene export and collider handling
README Insights
• Build badges only; no direct architecture description.
• Reliance on GitHub Actions for Debug/Release builds suggests CI/CD integration but does not change runtime architecture.
Final Recommendations
• Be granular: break each feature group into its major subcomponents (e.g., CollisionManager, ParticleEmitter, SceneManager).
• Confirm with the code owners that any newly exposed subsystems (e.g., UVTransformAnimation, WaveformDisplay) are represented.