Unhooked Engine V2

Introduction

Unhooked Engine V2, forked with Sheeesh Engine, is a 3D game engine made by two students, David Ruiz Luengo & Pau Garriga Brotons, as part of their university subject at CITM-UPC Terrassa.

Team

Meet the team:

David Ruiz Luengo

Github: https://github.com/xdavido

Tasks:

• Physics Engine Base 2
• Extract Glut
• Add Glew, SDL2, MathGeoLib
• Implement ImGui (FPS, Hardware, options...)
• Load and Save Textures
• Implement DevIL library
• Load FBX (drag and drop)
• Load and Save Image Devil
• Support drag and drop of textures
• Play/Stop/Pause management
• Viewports windows (scene and game)
• Assets tree viewer window
• Timmer
• Load scene
• Create a Particle Module
• Create a Particle System
• Create a Emitter instance
• Apply Billboard to particles
• Continous loop smoke come out of 2 houses in scene
• Particle Editor showed at inspector
• Fire works casts
• Camera animation
• Update Readme

Pau Garriga Brotons

Github: https://github.com/DonnoNonno

Tasks:

• Normal vertex and faces
• Draw Normales vertex y faces
• Solve general errors
• ImGui Useful Windows implementation
• Create GameObject Class
• Components transformations
• Camera and Frustrums
• Create particles from menu Gameobjects
• Load and save particles properties
• Saver for tamplated particles in files
• Clean up code
• Update Readme

Core Sub-systems

Our engine comprises several core sub-systems:

• Rendering System

The rendering system is responsible for generating the visual output of the game. It handles rendering 3D models, textures, lighting effects, and shaders to create the graphics displayed on the screen. The goal is to produce realistic and visually appealing scenes.

• Physics System

The physics system simulates physical interactions within the game world. It manages collision detection and response, object movements, gravity, and other forces. This subsystem ensures that in-game objects behave realistically and interact with each other according to the laws of physics.

• Input Handling System

The input handling system captures and processes user input from various devices, such as keyboards, mice, game controllers, and touchscreens. It translates input events into actions that can be used to control the game, such as moving characters, triggering abilities, or navigating menus.

• Resource Management System

The resource management system is responsible for loading, unloading, and managing game assets. It handles textures, models, audio files, and other resources efficiently, ensuring that only the necessary assets are loaded into memory at any given time to optimize performance.

• ImGui

ImGui, or Immediate Mode Graphical User Interface, is a GUI system that allows developers to create in-game user interfaces. It provides a simple way to create and customize UI elements, such as buttons, sliders, and text boxes, to enhance the user experience during development and debugging.

• Texture Handling

The texture handling subsystem manages the loading, manipulation, and rendering of textures in the game. It handles tasks such as loading image files, applying textures to 3D models, and managing texture resources efficiently for optimal performance.

• Scene Loading (GameObjects and Components)

The scene loading subsystem is responsible for loading and initializing game scenes. It manages the instantiation of GameObjects and their associated Components, setting up the initial state of the game world based on predefined scene configurations.

• Hierarchy

The hierarchy subsystem provides a structured view of the game objects in the scene. It allows developers to organize and manage the relationships between different game objects, making it easier to navigate and manipulate the game hierarchy during development.

• Camera Movement

The camera movement subsystem controls the movement and behavior of the in-game camera. It allows players and developers to navigate and explore the game world from different perspectives, enhancing the overall gaming experience and facilitating scene composition.

• Optimization

The optimization subsystem focuses on improving the performance and efficiency of the game engine. It includes techniques such as code optimization, rendering optimization, and resource management to ensure smooth and responsive gameplay even on lower-end hardware.

• Time Management

The time management subsystem is responsible for managing and controlling the flow of time within the game. It ensures consistent frame rates, handles animations, and provides a reliable mechanism for measuring and controlling time-based events.

• Mouse Picking

The mouse picking subsystem allows the selection of game objects in the 3D world using the mouse cursor. It involves techniques to cast rays from the mouse position and determine which object or point in the scene the cursor is interacting with.

• High Level System

The high-level system encompasses various features and functionalities that operate at a higher level of abstraction. This may include systems related to game logic, artificial intelligence, scripting, and other high-level components that contribute to the overall gameplay experience.

Last Assignment Sub-system

Particles High Level System

Last assignment was to implement a particle system inside our general engine:

The CEmitter component plays a crucial role in our game engine as it defines and oversees particle emitters. When an emitter is created, its constructor sets default values for the particles it will emit. Importantly, the emitter can be linked to a specific object in the game. The Update() and RenderParticles() methods control the regular updates and visualization of the emitter's particles. For user convenience, PrintInspector() offers an interface to adjust emitter properties, and save/load methods enable storing and retrieving the emitter's state from files.

The ModuleParticles module takes on the responsibility of globally managing the particle system. Its constructor and destructor handle the initialization and release of module resources. The update methods (PreUpdate, Update, PostUpdate) are in charge of keeping emitters updated and managing logic related to the life and explosion of fireworks. CleanUp() is used to free up memory occupied by emitters. This module also provides functionalities for saving/loading the state of the particle system to/from files. Additionally, castFirework() is a function that creates and launches fireworks with random properties.

Moving on to the ParticleSystem component, it defines the overall particle system in our game engine. The constructor initializes a system with a fixed-size list of particles. The Update() method takes care of updating particle positions and life. Emit() generates new particles with specific properties. ParticleBuffer() fills buffers with indices and vertices to represent a particle, while Render() displays active particles using OpenGL, applying interpolation to enhance visual quality. Billboard() ensures that particles always face the camera.

The cohesion of these components is achieved through ModuleParticles, which handles both the update and rendering of emitters and fireworks. ParticleSystem manages the life, emission, and rendering logic of particles. CEmitter defines the specific properties and behavior of individual particles. This system is designed with user-friendliness in mind, offering a straightforward interface to adjust particle properties in real-time. Its modular structure facilitates system expansion and maintenance. In summary, this setup provides a robust foundation for creating and managing dynamic visual effects in graphic environments or games.

Videos:

Video

One-minute speed-up video showing the Engine:

Repository

Link to the code repository and last release to download:

License

Unhooked Engine V2 is licensed under the MIT License:

		MIT License

		Copyright (c) 2023 Pau Garriga Brotons & David Ruiz Luengo

		Permission is hereby granted, free of charge, to any person obtaining a copy
		of this software and associated documentation files (the "Software"), to deal
		in the Software without restriction, including without limitation the rights
		to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
		copies of the Software, and to permit persons to whom the Software is
		furnished to do so, subject to the following conditions:

		The above copyright notice and this permission notice shall be included in all
		copies or substantial portions of the Software.

		THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
		IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
		FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
		AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
		LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
		OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
		SOFTWARE.