User Tools

Site Tools


start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
start [2025/11/25 10:25] divinerstart [2025/11/25 11:22] (current) diviner
Line 24: Line 24:
  
   * [[MVVM]] architectural support that enables the codebase to interface with game engine code in a completely decoupled way.   * [[MVVM]] architectural support that enables the codebase to interface with game engine code in a completely decoupled way.
 +
 +  * A 3D Vector Math Library building on top of System.Numerics.
  
   * A scalable, robust and performant [[Physics System]] for 3D Rigidbody Physics, offering Raycasting, Collision Events and realtime physics simulations.   * A scalable, robust and performant [[Physics System]] for 3D Rigidbody Physics, offering Raycasting, Collision Events and realtime physics simulations.
Line 37: Line 39:
   * Server modules. The architecture is created with authoritative servers in mind, providing the ability to write game logic once and have it run both on server and client side without requiring to run the game engine on the server. Since each online game is unique in its own way and requirements, a multi-paradigm server module is not feasible. Architecture adopters are urged to use the architecture to create their own modules tailored to the needs of their games.   * Server modules. The architecture is created with authoritative servers in mind, providing the ability to write game logic once and have it run both on server and client side without requiring to run the game engine on the server. Since each online game is unique in its own way and requirements, a multi-paradigm server module is not feasible. Architecture adopters are urged to use the architecture to create their own modules tailored to the needs of their games.
  
-  * Platform deployment. The architecture depends on 3rd party support for deploying software using its features.+  * Publishing. The architecture depends on 3rd party support for deploying software using its features
 + 
 +  * Graphics Rendering. If graphics are required as an output, support must be given by interfacing with 3rd party rendering engines (game engines or custom made renderers).
  
-  * Rendering supportIf graphics are required as an output, support must be given by interfacing with 3rd party rendering engines (game engines or custom made renderers).+  * Audio SystemsMuch like Graphics Rendering, if audio output is required, support must be given through 3rd party libraries.
  
   * Game Engine integration other than Unity. The architecture was built for use primarily with the Unity Game Engine. Even though its portable nature allows it to interface with other engines too (Godot, custom ones), the necessary adapter code has to be implemented individually.   * Game Engine integration other than Unity. The architecture was built for use primarily with the Unity Game Engine. Even though its portable nature allows it to interface with other engines too (Godot, custom ones), the necessary adapter code has to be implemented individually.
start.1764066330.txt.gz · Last modified: by diviner

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki