✅ Working with the current UE5.1 Preview ver.

Branch: https://github.com/lucoiso/UEProject_Elementus/tree/feature/EQUIP-26

from ueproject_elementus.

I've decided to move the entire project to UE5.1 instead adding a full support to continue using all new features that are coming with the newer engine versions.

With "full support" I mean that this project is a template to use only when is initializing a new project because each new project will have their specific assets/classes/objects and every asset inside this project are examples or came from the engine, you don't need them for your game/simulation.

And as the backend is being developed fully in C++, you'll have the same code to use with previous versions after doing some tweaks (older versions will require hard tweaks as this project born in UE5.0 Early Access) and will lost only the assets (examples and engine files like character mesh, animation, etc.)

Other reasons:

1. This project born with the intend to use the newer features from the Engine since UE5.0 Early Access 1 and will continue to use the latest releases.
2. Git LFS generate costs (and this is a free project xD). Using only 1 version of this project will reduce the size of the repository.
3. Some things change from a version to another, to add support to more than one version, will need to add macros in the code to tell the compiler to use a specific block of code and this could make reading worse and bring unnecessary code to projects that are born from this template.
4. Blueprints and other assets from different UE versions can take up twice as much space or more, as Git differentiates binary files as totally different (Increasing Git LFS cost).

Last version for UE5.0: https://github.com/lucoiso/UEProject_Elementus/releases/tag/v0.6.0a

from ueproject_elementus.