Main Core Sub-Systems

-Geometry Viewer

This subsystem can import dragged resources as fbx files to be imported with assimp. Later this can be shown throught viewport to be rendered.

-Gameobjects and Components

This structure enables us to work properly with different subsystems as Physics in our case due We force to cluster all stuff as Transforms, Mesh info and Renderers, Materials..., furthermore helps us to Serialize info to be stored.

-User Interface

Basic user interface developed with ImGui to visually work with our elements Ex: Gameobjects can be modified from hierarchy/inspector window, resources can be managed...

-Time Manager

Simpler subsystem that only takes in charge of time step in game. Useful to work with animations physics and particles

-Resource Manager

Subsystem that cares how resources are managed by user. User can drop resources and this will be imported with own data structures to be loaded faster. Moreover user can search resources in engine window and make use of them. Ex: Drop texture into material or load saved scenes

-Cameras and Guizmos

Here We can find minimal render optimizations with frustum culling, developed due to camera near/far planes and geometry bounding boxes. Also camera's raycast enables us to activate mouse picking feature and display guizmos to interact with gameobjects

Physics System

Physics system have been developed with Nvidia PhysX 4.1. This libraries enables us to add into our scenes and gameobjects physicalized properties as gravity forces, mass, friction, restitution... through rigidbody , collider and constrain structures.

Gameobjects now can create new components as:

-Rigidbody

This component will create a dynamic actor that will interact with physical forces and will take control about which position does the gameobject have in the world

-Colliders

Will create into the gameobject selected a collider with desired primitive shape by user that can be Box, Sphere or Capsule. If the gameobject does have already a rigidbody the shape collider will be attached to the rigidDynamic to react with world collisions. If the gameobject doesn't own a rigidDynamic body, shape will be settled and attached to a rigidStatic body

-Constrains

Constrains between rigidBodies can be created with joint components(Distance, Hinge, Slider, Spherical). Like rigidbody and collider components, joints can be settled from inspector window. Joint's main function it's attach two rigidbodies and interact between both with world physics and own properties.

Otherwise We've developed two extra core modules to manage physics and create the mentioned structures. This core modules will be ModulePhysics and ModuleVehicle

-ModulePhysics

This module initialize main core SDK structures related to physX libraries as PxPhysics that make us able to create materials, actors(rigid static/dynamic bodies) and constrains. Also takes in charge of initialize world physics and calculations depending time step assigned.

-ModuleVehicle

Like ModulePhysics module, this one takes in charge of initialize physX vehicle SDK to create properly physicalized vehicles with gears/tires/chassis adjustments