pgalve100 / turbox-engine

3D Game Engine built from the ground up using C++ and OpenGL

TurboX-Engine

TurboX-Engine is a 3D Game Engine with an integrated particle system built from scratch in C++ and OpenGL. We are two future game developers that are currently studying at CITM (Barcelona, Spain).

Website: pablogalve.github.io/TurboX-Engine Repository Link: github.com/pablogalve/TurboX-Engine

Particle System

How to compile

• Clone or fork the repository
• Open TurboX-Engine.sln in the 'TurboX-Engine\Source_Code' folder
• Set up the necessary dlls:
  • Inside Visual Studio 2019 -> Debug > TurboX-Engine Properties... > Debugging > Working Directory: ..\Engine\TurboX-Engine\TurboX-Engine

Continuous Integration & Deployment

• Commits on master branch will generate an automatic build (ready to use by the end user) and deploy it in GitHub Releases.

Team Members

• Pablo Galve Millán
  • github.com/pablogalve
  • linkedin.com/in/pablogalve/
• Macià Dalmau Roig
  • github.com/maciadalmau

Engine Controls:

• WASD: move camera around the scene.
• Mouse wheel: Zoom in and out.
• Alt+Left click: Orbit the object.
• F: Focus the camera around the geometry.
• SHIFT: duplicates movement speed.
• W: translate
• R: rotate
• E: scale

LICENSE

TurboX-Engine is using a dual-license. Which one applies to me?

MIT LICENSE

You will be using the MIT LICENSE by default, provided that you are compliant with at least 1 of the following conditions (Only 1 is needed):

• You credit the authors on your project. You must include our MIT LICENSE in the same folder where you store the licenses from other libraries or projects that you are using.
• You contribute to this project. For example, you open a pull request to add a feature, solve a bug or improve something.
• You fork this project. You can fork this repository for your own purposes (including commercial use) following the MIT LICENSE.
• Any other situation that is not covered in the PROPRIETARY LICENSE. If you are using this project for a case that does not meet the conditions of PROPRIETARY LICENSE, then you are covered by default by MIT LICENSE

Free open-source license: MIT LICENSE.

PROPRIETARY LICENSE

• If you want to use this repository for any use without being compliant with the MIT LICENSE above mentioned, then you must follow the PROPRIETARY LICENSE.
• If you copy this entire project or some parts of it without giving credit to the original authors (e.g. plagiating a project and claiming it was made by you when in fact it wasn't), then we will understand that you are acting on bad faith and against us and the open-source philosofy, and therefore you must follow the PROPRIETARY LICENSE.

Paid proprietary license: PROPRIETARY LICENSE.

You still have doubts about which license to follow?

• You will copy parts or the entirety of this project without crediting the original authors: PROPRIETARY LICENSE.
• Any other case: MIT LICENSE.

turbox-engine's Issues

'Smoke' should be its own Particle Emitter template

Is your feature request related to a problem? Please describe.
It's related to doing modular and cleaner code to improve the engine.

Describe the solution you'd like
'Smoke' should be its own Particle Emitter template instead of being hardcoded.
See 'Firework' as a reference. We should do the same for the smoke:

Custom Particle Emitters (Smoke, Firework) are not updating the inspector values

Describe the bug
Custom Particle Emitters (Smoke, Firework) are not updating the inspector values

To Reproduce
Steps to reproduce the behavior:

1. Create a custom particle emitter (smoke)
2. Go to the inspector
3. The values shown in the inspector do not correspond to the real values

Expected behavior
The inspector should display the actual values of the particle emitter

Desktop (please complete the following information):

• Version 0.6.31

Hierarchy parenting not displaying correcly

Describe the bug
Hierarchy parenting not displaying correcly

Expected behavior
It should move the childs to the right to have a better visualization

Screenshots
The problem:

Desktop (please complete the following information):

• Version 0.6.31

Create default particle systems from tab

Describe the solution you'd like
The user should be able to create a default particle system (e.g. smoke or fireworks) by clicking a button.
That button may be located here (optional)

or maybe here: