Esoterica 引擎
Esoterica Engine is an MIT licensed prototype game engine framework. It's intended for use either as a proprietary engine starter pack, a technology demonstrator, an educational tool or an R&D framework. The goal of Esoterica is to provide a solid and robust starting point for folks that are looking to build their own tech or transition off of existing tech. It provides a lot of the boring and time consuming boilerplate systems (reflection, serialization, resource management, math, etc...) as well as a tool framework allowing people to rapidly build their own tool/editors.
We need to be clear that Esoterica is NOT an off the shelf game engine that you can just take and work with. It is intended for technical teams that have the ability to extend and build upon it.
Esoterica is a prototype engine that's being developed in our spare time and as such there will likely be bugs and crashes (primarily with the tooling side). It is not intended as a stable production tool. If you encounter any crashes or bugs, please file issues and we'll try to get to them as soon as we can.
Esoterica is not a product and so there wont be any formal releases or versions. As such, we are not looking for any feature requests, nor are we looking for large PR contributions. Any feature requests or large PR will be rejected. That said, please feel free to create issues for bugs, clearly broken/incomplete pieces of code or for general questions.
The level editing experience is intentionally barebones and rough. In our experience, level editing workflows and tools are incredibly subjective. There is no way to provide tools or workflows that will work for everyone. It will also go against the goal of Esoterica, which is to be a starting point for custom engine development. If a team wants to use Esoterica as a base we want to provide the simplest base for them to build whatever tooling they need for their team and their game.
We are providing some tools in a more polished form like the animation tools and ragdoll editor. This is because we believe that this area is a significantly less subjective field as the problem is better defined and constrained. This makes it easier to build tooling and guide folks down a specific tooling path.
The import pipeline is currently a bit rough from a front-end experience, this is being iterated and played with currently to see if we can find a balance between simplicity and the relatively painful importing other engines provide.
As Esoterica is constantly being iterated and worked upon, it becomes hard to provide any documentation that isnt immediately out of date. Additionally, it becomes even less relevant for people forking it to build their own engine with. The code itself is heavily commented and written to be as readable as possible, this is how we intended to provide documentation moving forward.
We do have highlevel docs for the renderer here:
And we have several presentations that cover the high level decisions regarding the entity model and the animation systems here:
If really you do wish to contribute, we do need some help. We are looking for folks to help us build out a simple sample game that we can include with the project.
We are looking for the following:
More details can be found here:
| Resource Pipeline | Basic Editor |
|---|---|
| Animation Graph | Ragdoll Editor |
|---|---|
Esoterica uses vanilla msbuild for its build system. There are a set of property sheets that control all the build settings for Esoterica in the "code/property sheets" folder.
Get the external dependencies set up: there are two ways to do this:
DownloadDependencies.bat script found in the root folderOpen the solution "Esoterica.sln"
Manually rebuild the "Esoterica.Scripts.Reflect" project (under the "0. Scripts" solution folder) - this will generate all the required Esoterica reflection code needed for the project to compile.
Build the solution
Easiest way to get started, is just set the "Esoterica.Applications.Editor" as the startup project and hit run. If you want to run the engine, use the "Esoterica.Applications.Engine" project with the "-map data://path_to_map.map" argument.
These middleware packages are also integrated but require a license to use (so they are disabled by default)
If you use the SmartCommandLineArguments plugin for VS then there are supplied saved arguments to help you start the engine.
暂无开放 Issues，或尚未同步最近议题。