Open 3D Engine (O3DE) is an Apache 2.0-licensed 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.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
lawsonamzn 6a7a86062e Updates AutomatedTesting project and adds atom support 5 years ago
Assets Remove Assets/Engine/Shaders and the root Tests folder (#831) 5 years ago
AutomatedTesting Updates AutomatedTesting project and adds atom support 5 years ago
Code Merge pull request #772 from aws-lumberyard-dev/Prefab/Create/PositionFix 5 years ago
Gems Updates AutomatedTesting project and adds atom support 5 years ago
Registry Merge branch 'main' into Helios_DataDrivenAssetImporter 5 years ago
Templates O3de updates restricted download (#229) 5 years ago
Tools Reduce AP race conditions and fix minor bugs 5 years ago
cmake The new gem registration and usage system 5 years ago
python SPEC-6276 Move ci_build and ci_build_metrics to scripts\build 5 years ago
scripts Disable shallow checkout in initial setup step 5 years ago
.clang-format Integrating latest 47acbe8 5 years ago
.editorconfig Initial commit 5 years ago
.gitattributes Merge branch 'main' into cpack_installer 5 years ago
.gitignore updating gitignore for python packages 5 years ago
.lfsconfig Updating lfs endpoint 5 years ago
CMakeLists.txt The new gem registration and usage system 5 years ago
Doxyfile_ScriptBinds Initial commit 5 years ago
LICENSE.txt Initial commit 5 years ago
README.md Fix repo url 5 years ago
SerializeContextAnalysis.bat Initial commit 5 years ago
SliceBuilderSettings.json Initial commit 5 years ago
aztest_bootstrap.json Initial commit 5 years ago
bootstrap.cfg LYN-2537 engine assets (#254) 5 years ago
ctest_pytest.ini Initial commit 5 years ago
editor.cfg Initial commit 5 years ago
engine.json O3de updates restricted download (#229) 5 years ago
system_android_es3.cfg Initial commit 5 years ago
system_ios_ios.cfg Initial commit 5 years ago
system_linux_pc.cfg Initial commit 5 years ago
system_mac_osx_gl.cfg Initial commit 5 years ago
system_windows_pc.cfg Initial commit 5 years ago

README.md

Project Spectra Private Preview

Confidentiality; Pre-Release Access

Welcome to the Project Spectra Private Preview. This is a confidential pre-release project; your use is subject to the nondisclosure agreement between you (or your organization) and Amazon. Do not disclose the existence of this project, your participation in it, or any of the materials provided, to any unauthorized third party. To request access for a third party, please contact Royal O'Brien, obriroya@amazon.com.

Download and Install

This repository uses Git LFS for storing large binary files. You will need to create a Github personal access token to authenticate with the LFS service.

Create a Git Personal Access Token

You will need your personal access token credentials to authenticate when you clone the repository.

Create a personal access token with the 'repo' scope.

Recent versions of Git install a credential manager to store your credentials so you don't have to put in the credentials for every request.
It is highly recommended you check that you have a credential manager installed and configured

Clone the repository

> git clone https://github.com/aws-lumberyard/o3de.git
Cloning into 'o3de'...

# initial prompt for credentials to download the repository code
# enter your Github username and personal access token

remote: Counting objects: 29619, done.
Receiving objects: 100% (29619/29619), 40.50 MiB | 881.00 KiB/s, done.
Resolving deltas: 100% (8829/8829), done.
Updating files: 100% (27037/27037), done.

# second prompt for credentials when downloading LFS files
# enter your Github username and personal access token

Filtering content: 100% (3853/3853), 621.43 MiB | 881.00 KiB/s, done.

If you have the Git credential manager core installed, you should not be prompted for your credentials anymore.

Building the Engine

Build Requirements and redistributables

Build Steps

  1. Download the 3rdParty zip file from here: https://d2c171ws20a1rv.cloudfront.net/3rdParty-windows-no-symbols-rev13.zip

  2. Unzip this file into a writable folder. This will also act as a cache location for the 3rdParty downloader by default (configurable with the LY_PACKAGE_DOWNLOAD_CACHE_LOCATION environment variable)

  3. Install the following redistributables to the following:

    • Visual Studio and VC++ redistributable can be installed to any location
    • FBXSDK should be installed to <3rdParty path>\FbxSdk\2016.1.2-az.1. See the README in this folder for details
    • WWise should be installed to: <3rdParty Path>\Wwise\2019.2.8.7432
    • CMake should be installed to: <3rdParty Path>\CMake\3.19.1
  4. Add the following environment variables through the command line

    set LY_3RDPARTY_PATH=<Location of the unzipped 3rdParty zip>
    set LY_PACKAGE_SERVER_URLS="https://d2c171ws20a1rv.cloudfront.net"
    
  5. Configure the source into a solution using this command line, replacing to a path you've created

    cmake -B <your build location> -S <source-dir> -G "Visual Studio 16 2019" -DLY_3RDPARTY_PATH=%LY_3RDPARTY_PATH% -DLY_UNITY_BUILD=ON -DLY_PROJECTS=AutomatedTesting
    
  6. Alternatively, you can do this through the CMake GUI:

    1. Start cmake-gui.exe
    2. Select the local path of the repo under "Where is the source code"
    3. Select a path where to build binaries under "Where to build the binaries"
    4. Click "Configure"
    5. Wait for the key values to populate. Fill in the fields that are relevant, including LY_3RDPARTY_PATH, LY_PACKAGE_SERVER_URLS, and LY_PROJECTS
    6. Click "Generate"
  7. The configuration of the solution is complete. To build the Editor and AssetProcessor to binaries, run this command inside your repo:

    cmake --build <your build location> --target AutomatedTesting.GameLauncher AssetProcessor Editor --config profile -- /m
    
  8. This will compile after some time and binaries will be available in the build path you've specified

Setting up new projects

  1. Setup new projects using this command
    <Repo path>\scripts\o3de.bat create-project --project-path <New project path>
    
  2. Once you're ready to build the project, run the same set of commands to configure and build:
    cmake -B <your build location> -S <source-dir> -G "Visual Studio 16 2019" -DLY_3RDPARTY_PATH=%LY_3RDPARTY_PATH% -DLY_PROJECTS=<New project name> -DLY_MONOLITHIC_GAME=1
    
    cmake --build <your build location> --target <New Project Name> --config profile -- /m
    

License

For terms please see the LICENSE*.TXT file at the root of this distribution.