How wannabpark/week2_texture_wf works
This project is a game engine (named “Week1-Engine”) written in C++ that provides core engine functionality for rendering, scene management, actor/component handling, hardware abstraction, and debugging. The file tree clearly separates functional areas such as Core engine systems, various Actors and their Components, Rendering (including shader management), a Mathematical library, Input management, and integration with third-party libraries like ImGui and SimpleJSON.
Main Components
• Engine Core: Represent the entry point (main.cpp) and main engine loop (Engine.cpp/Engine.h, EngineStatics.cpp). This is the central hub that drives game logic, scene management, and system initialization.
• Scene & Object Management: Include modules for Scene Managers (FSceneManager), Object system (UObject, UClass, ObjectFactory) and the Actor hierarchy (under Source/Object/Actor). Illustrate how various actor types (Camera, Cube, Sphere, etc.) are instantiated and managed.
• Actor Components & Systems: Detail the Actor Component structure (including Colliders and Primitive components) which allows behaviors to be modularly added to actors.
• Rendering System: Highlight the Rendering module (URenderer, ShaderParameterMacros, BufferCache) plus the Shaders directory where several HLSL shader files reside. Show that the Engine Core directs render calls to the rendering system.
• Hardware Abstraction Layer (HAL): Include PlatformMemory, PlatformType, and StackAllocator under the HAL directory. This abstracts underlying hardware specifics such as memory management.
• Input System: Represent the input handling via PlayerInput and PlayerController, showing how user input feeds into the system.
• Math Library: Clearly mark the Math module (Vector, Matrix, Plane, Transform, MathUtility) as it underpins physics, rendering, and transformation calculations.
• Debug & Editor Tools: Represent debugging facilities (DebugConsole) and editor management (FEditorManager) which could be used during development.
• Third-Party Integrations: Include a separate block for ThirdParty libraries (ImGui for UI, SimpleJSON for serialization). Indicate how they integrate with the engine (for example, ImGui integration in Rendering via DirectX implementations).
Relationships and Interactions
• From the Scene Manager, show interactions with the Object and Actor systems – for instance, how the game world is populated with various actors and components.
• That ThirdParty modules like ImGui integrate with the Rendering system and possibly with Debug systems for overlay UIs.