Skip to content
This repository has been archived by the owner on Jan 7, 2024. It is now read-only.

Latest commit

 

History

History
99 lines (97 loc) · 2.02 KB

README.md

File metadata and controls

99 lines (97 loc) · 2.02 KB

Neon Game Engine Project.

  • Modern C++.
  • Easy usage.
  • Appeal to different demographics
    • Beginners
    • Intermediate
    • Advanced
    • Developper
  • Basic Features
    • Frameworks
      • Modules can be extended / overridden depending on what the user wants.
    • Graphics
      • DirectX 12
      • Vulkan
      • Metal
    • Window
      • Basic window
      • Customized window
      • Editor
      • Dockable window
    • Audio
    • Input
      • Basic pooling
      • Input hooking
    • Math types
      • Vector
      • Matrix
      • Rect
      • Viewport
      • Color
    • Logging
      • Console logging
      • File logging
    • Event system
      • Private events
      • Public events
    • Scripting
      • C# Support
    • Concurrency
      • Thread pooling
      • Coroutines
    • Editor
      • Compose Assets
      • Prepare the runtime
    • Runtime
      • Run only on assets
      • Can Run without any assets
      • Extendable
    • Resource Management
      • Async
      • Customizable Loaders, Savers, Exporters, Importers
      • Multiple packs and resource format
      • Resource dependecy resolution
    • Rendering
      • 2D
      • 3D
      • 2.5D
      • Render graph
        • Automatic resource management
        • Automatic nodes dependecy resolution
      • GUI
      • Frustum culling
        • GPU Side
        • CPU Side
      • Ray tracing
        • GPU Side
        • CPU Side
      • Light management
      • Post process effects
    • Scene
      • ECS (Flecs)
      • Components
        • Transform
        • Mesh
        • CSG
        • Sprite
        • Audio player
        • Lights
    • Networking
    • Cross platform
      • Windows
      • Linux
      • Mac
      • Mobile

Layer of usage.

  • Simple
    • Easy to use, Easy to understand.
    • Game loop won't be visible.
    • Everything is hidden in simple classes/functions when needed.
    • Customizable, user will write simple main function, hook up any needed callbacks and call it a day.
    • Self contained resource management.
  • Advanced
    • Internal API is exposed.
    • User must provide a propper management of game loop.
    • User can choose what framework / module to enable / disable.
  • Framework Individual modules can be constructed / changed.