SuSto Engine

Engine Theme

XML loader implemented

Geometry Test First Assignment

Console Window

AppVeyor implemention

Json Module

Profiler Window

Configuration Window

Hardware Window

Key Binding implemention

Docking

Layouts implemention

Cursor class

Component Transform

Component Mesh

Component Camera

Mesh Rendering

Texture Rendering

Orbit behaviour for assignment implemented

Parenting of GameObject shown at hierarchy

Frustum implemented

Mouse picking

ImGuizmo implemention

Play, Stop and Pause modes implemented

First approach to Explorer Window

User Interface 2D Plane Rendering

UI Canvas

UI Image

Mouse pick in User Interface

UI Text and UI Text Input

• Random Number Generation implemention
• About Window
• MMGR implemention
• Wireframe, Fill and Point Rendering modes implemented
• Hardware Window
• Ambient, Diffuse and Specular lights with color picker
• VRAM and RAM shown in profiler
• Docking
• Menu Bar for the editor
• Inspector Window
• Icon added
• First approach to Mesh rendering
• TextureLoader and MeshLoader
• Unity-like Movement
• K-D Tree Implemention
• First approach to Save and Load
• Explorer Implemention
• Base for the User Interface event system
• Keyboard and Mouse events for the User Interface
• Anchors, Position and Scale of the UI Components serialization
• UIElements texture serialization
• Button implemention
• Checkbox implemention
• Button implemention
• HTML Website

GameObjects are shown at the hierarchy. There, they can be selected (by right clicking) and created (with a button above the list of GameObject. Also, by right clicking and then pressing the button delete it will erase the GameObject.

At the inspector it is posible to look at the components of a selected GameObject, which would be the next ones:

• Transform
• Mesh
• Texture
• Camera
• UICanvas
• Other User Interface Elements

The console prints the log of the engine, and also admits commands. At the momement, there are two commands:

• .Clear: clears the log of the console.
• .Help: Shows a list of commands.

Mainly, the user can look at the memory usage and the framerate within the profiler window.

We created a user interface that can be accessed by creating UI components. First, to use the UI elements in a proper manner there must be a canvas which will be the parent of the elements created later. In this version of the engine the UI elements that can be used are:

• Button: A button has 3 textures, an idle texture (when there is no event activated), an over texture (if the cursor is over the element) and a pressed texture (if the element is clicked).
• Image: An image is basicaly a texture rendered in the canvas.
• Checkbox: A checkbox has 2 states, ruled by a bool that changes between true or false if the element is clicked.
• Text: A text is printed in the canvas by converting it to a texture using a font.
• Input Text: The text input is an element that lets the user write text into the space given by the element.

We created a user interface that can be accessed by creating UI components. First, to use the UI elements in a proper manner there must be a canvas which will be the parent of the elements created later. In this version of the engine the UI elements that can be used are:

• Move: Selects the current guizmo mode to Movement.
• Rotate: Selects the current guizmo mode to Rotation.
• Scale: Selects the current guizmo mode to Scale.
• Play: Starts the game, every object that is moved during play-time will return to its original position, also for the rotation and scale.
• Pause: Only shown during play-time. It will change to editor mode, stoping the game.
• Draw KDTree: Debug functionality that shows the planes that are dividing the gameobjects to create the KDTree.
• Draw BBoxes: Draws the bounding boxes of all gameobjects that have one.