Getting Started

Install OPAL, install an engine, launch your first project.

This guide takes you from “I don’t have OPAL yet” to “I’m looking at the O3DE Editor with my project open” in about ten minutes. There’s no prerequisite knowledge of O3DE — but if you’ve used Unity Hub or the stock O3DE Project Manager, the flow will feel familiar.


1. Install OPAL

Head to the Download page and grab the installer for your platform. Run it. On first launch, OPAL will ask for a workspace directory — this is where projects go by default. Pick something with a few GB free. You can change it later in Settings.


2. Install your first engine

On first launch (and any time you open the Engines page with no engines installed), OPAL prompts you to install one.

This is the selling point: you don’t need to visit the O3DE website. OPAL knows about every O3DE release and handles the download, install, and registration itself.

You’ll see three options:

  • Latest stable — the most recent O3DE release. Recommended for new projects.
  • Older stable — pick any prior version. Useful when a project is pinned.
  • Build from source — clone and build the engine’s development or a specific branch. Use this when you need engine patches.

Pick one. OPAL kicks off the download (or clone + build) and tracks progress in the Downloads queue. You can keep working in the rest of the app while it runs.


3. Create or import a project

Once an engine is installed, go to the Projects page.

Create a new project

Click New Project. Fill in:

  • Name — used for the folder and project_name in project.json.
  • Template — OPAL bundles the standard O3DE templates. Pick one.
  • Engine — defaults to your default engine; override per project if needed.
  • Location — defaults to your workspace; override if you want it elsewhere.

Hit Create. OPAL runs o3de create-project, registers the project, and adds it to the list.

Or import an existing project

Click Import. Point at a project folder containing a valid project.json. OPAL reads the manifest, detects the engine pin, and adds the project.


4. Launch the editor

Find the project in your list. Look at the status badge:

BadgeMeaningWhat to do
Not builtNever been configured/builtClick Build, then Open
BuiltBuild is currentClick Open to launch the Editor
OpenEditor is runningNothing — it’s already running
Build failedLast build erroredClick View logs to see why

For a fresh project, you’ll see Not built. Click Build. OPAL queues it and starts the CMake configure + compile. This will take a while the first time — that’s the O3DE engine compiling your project modules.

When the status flips to Built, click Open. The Editor launches with your project loaded.


5. Next steps

  • Configure gems for your project: Gems
  • Tweak your default build settings: Settings
  • Set up multiple engines: Engines
  • Learn the queue controls: Queues