Also known as O3DE
free and open-source 3D engine based on the CryEngine
O3DE (Open 3D Engine) is an open-source, real-time, multi-platform 3D engine that enables developers and content creators to build AAA games, cinema-quality 3D worlds, and high-fidelity simulations without any fees or commercial obligations. Roadmap For information about upcoming work and features, please visit Progress against the roadmap is tracked here. Verify you have Git LFS installed by running the following command to print the version number. For the latest details and system requirements, refer to System Requirements in the documentation. Visual Studio 2019 16.9.2 minimum (All editions supported, including Community): Check System Requirements for other supported versions. Install the following workloads: Game Development with C++ MSVC v142 - VS 2019 C++ x64/x86 C++ 2019 redistributable update CMake 3.24.0 minimum: (Release Candidate versions are not supported) Wwise audio SDK For the latest version requirements and setup instructions, refer to the Wwise Audio Engine Gem reference in the documentation. To set up a project-centric source engine, complete the following steps. For other build options, refer to Setting up O3DE from GitHub in the documentation. 1. Create a writable folder to cache downloadable third-party packages. You can also use this to store other redistributable SDKs. 1. Configure the engine source into a solution using this command line, replacing , , and with the paths you've created: 1. The configuration of the solution is complete. You are now ready to create a project and build the engine. For more details on the steps above, refer to Setting up O3DE from GitHub in the documentation. 1. From the O3DE repo folder, set up a new project using the o3de create-project command. 1. Build the project, Asset Processor, and Editor to binaries by running this command inside your project: Note: Your project name used in the build target is the same as the directory name of your project. This will compile after some time and binaries will be available in the project build path you've specified, under bin/profile . For a complete tutorial on project configuration, see Creating Projects Using the Command Line Interface in the documentation. For terms please see the LICENSE .TXT files at the root of this distribution.
Excerpt from the source-code README · 6,043 chars · not written by Vinony
via Wikidata · CC0
Discovered by embedding cosine similarity (sentence-transformers MiniLM, 384-dim).