Engine setup
GameGen uses an Unreal Engine install that is already on your machine. It finds the engine by itself in most cases. This page explains the search order, what a version mismatch means, and how to point GameGen at a specific engine.
How the engine is found
GameGen and the project’s Scripts/ue.mjs apply the same rule, in this order.
- The
UE_ROOTvariable. If it is set, that folder is used. - The Epic Games launcher’s install list. Entries named
UE_and a version are engines. - The default install folder.
| Platform | Default install folder |
|---|---|
| macOS | /Users/Shared/Epic Games |
| Windows | Epic Games inside your Program Files folder |
| Linux | None. Set UE_ROOT or pass --engine-root. |
When several engines are found, the one whose version matches the project’s EngineAssociation wins. If none matches, the newest is used.
On the command line, --engine-root overrides all of these. See the ue.mjs reference.
The version a project wants
The .uproject file’s EngineAssociation field names the engine version the project wants. The Unreal view shows it as Wants Unreal Engine and a version.
When you create a project with New game, GameGen writes the version of the engine it finds on your machine. If it finds none, it writes 5.9.
When the versions differ
The Version row reads, for example, “5.9 wanted, 5.8 installed”, and explains the effect:
- Build, Run tests and Open editor use the installed engine.
Scripts/ue.mjscalls that engine’s build script and editor directly, and those do not readEngineAssociation. - The Epic Games launcher and a double-click on the
.uprojectdo read it, so they ask which engine to use. - Code written for one version can fail to compile on another.
Two other messages can appear in the Version row:
| Message | Meaning |
|---|---|
| “The .uproject names no engine version (EngineAssociation is empty).” | There is nothing to compare. |
| “The project is tied to a specific engine build (…), not a release version, so it cannot be compared with the installed engine.” | EngineAssociation is not a version such as 5.9. |
Set UE_ROOT
Set UE_ROOT when the engine is somewhere the search does not look, or when you want a specific install.
Find the engine folder
Find the folder that contains Engine/. For a launcher install it is named like UE_5.9.
Set the variable
When no engine is found, the Unreal view shows this command with a Copy button.
export UE_ROOT="/path/to/UE_5.x"This is a shell command for macOS and Linux. The steps for setting UE_ROOT on Windows are not yet verified.
Restart GameGen
Quit GameGen and start it again so it picks up the variable.
If UE_ROOT points at a folder with no Engine folder, the Engine row shows Not found and says so. Point it at the folder that contains Engine/, or unset it to use the installed engine.