How stickyfingies/gengine works
Main Components Structure
a) Application Layer
• Examples/native.cpp and examples/javascript.js as entry points
• To the Core Engine layer
b) Core Engine Layer (Middle)
• Following major components:
• Asset Management (core/assets.h)
• Physics System (core/physics.h)
• Scene Management (core/scene.h)
• Camera System (core/camera.hpp)
• FPS Controller (core/fps_controller.h)
• Kernel (core/kernel.h)
c) Platform Abstraction Layer (Bottom)
• GPU Backends:
• Vulkan Implementation (gpu/gpu.vulkan.cpp)
• OpenGL Implementation (gpu/gpu.opengl.cpp)
• WebGL (through Emscripten)
• Window Management (core/window.h)
Dependencies Integration
• GLFW3 (Window Management)
• Bullet3 (Physics)
• Assimp (Asset Loading)
• GLM (Mathematics)
• STB (Image Loading)
• ImGui (UI System)
Data Flow Representation
• Asset Pipeline: Asset Files → Assimp → Asset Manager → Scene Graph
• Rendering Pipeline: Scene Graph → GPU Interface → Platform-specific Backend
• Physics Pipeline: Collision Data → Bullet3 → Physics System → Scene Graph
• Runtime Architecture
• Build System Flow
• Asset Pipeline
• Platform Abstraction Layer
Key Elements to Emphasize:
Build system configuration
• Adaptive GPU backend
• Cross-platform support (Linux and Web)
• Physics integration
• Asset management system
• Platform-specific optimizations
This structure will provide a clear understanding of how Gengine works across different platforms while maintaining its core functionality.