Troubleshooting
Find the message you see in the tables below. Each row gives the cause and the fix. Messages are quoted as GameGen shows them, with ”…” where it prints a path or a value.
Engine
| Message | Cause | Fix |
|---|---|---|
| “No Unreal Engine install was found. Checked the UE_ROOT variable, the Epic Games launcher’s install list and the default install folder.” | No engine is installed where GameGen looks. | Install Unreal Engine from the Epic Games launcher, or set UE_ROOT to the folder that contains Engine/ and restart GameGen. See Engine setup. |
| “UE_ROOT is set to …, but that folder has no Engine folder.” | UE_ROOT points at the wrong folder. | Point UE_ROOT at the folder that contains Engine/, or unset it to use the installed engine. |
| Found (version unknown) | The engine’s version file could not be read. | The engine is still used. Check the install if builds fail. |
| ”… wanted, … installed” | The project asks for one engine version and another is installed. | The actions use the installed engine. Install the wanted version, or expect that code written for one version can fail to compile on the other. See Engine setup. |
| “no Unreal Engine install was found: set UE_ROOT or pass —engine-root” | The same problem, from Scripts/ue.mjs in a terminal. | Set UE_ROOT or pass --engine-root. |
Editor connection
| Message | Cause | Fix |
|---|---|---|
| Not connected, “No answer at …” | No editor answers at the Remote Control address. | Choose Open editor in the Unreal view. |
| Not connected, “An Unreal Editor is running on this machine, but it is not answering at …” | The running editor has a different project open, or its Remote Control server is off. | Choose Open editor. Or in the running editor, open this project, enable the Remote Control API plugin and run WebControl.StartServer in its console. |
| “EDITOR NOT STARTED: port 30010 is in use by another Unreal Editor (or the crash reporter of one that crashed).” | Another editor, or a crash dialog, holds the port. | Close that editor or crash dialog, then choose Open editor again. |
| “EDITOR NOT READY after … s” | The editor started but Remote Control did not answer in time. | Choose Stop editor, then read Saved/Automation/qa-editor.log. |
See Editor connection.
Build, test and action buttons
| Message | Cause | Fix |
|---|---|---|
| “This project has no Scripts/ue.mjs.” | The project has no build script. | Use a project that includes one, such as the tutorial. |
| “Node.js was not found. Install Node 18 or newer.” | No Node on this machine. | Install Node, then choose Refresh. |
| “An Unreal action from another project is still running.” | One action runs at a time. | Wait for it to end. |
| Incomplete under Last build and test | No test was selected, or a test did not report. | Read the names after “Did not report”, then open the test log. |
| A build fails with a file-lock or Live Coding error | The editor is open and holds the module binaries. | Close the project’s editor and build again. |
Views that will not load
These appear in a development build that has not been given access to the project’s files. An installed GameGen has that access.
| Message | Where |
|---|---|
| “The Unreal view needs project reads, which this desktop build has not been granted” | The Unreal view, under Unreal status unavailable. |
| “Lou Trainer needs project reads, which this desktop build has not been granted” | The Lou view. |
| “This desktop build has not been granted Unreal actions. Run the command in a terminal instead.” | The Unreal view’s action buttons. |
| A message that starts with “Tauri” and ends with “not yet available” | A feature this build does not offer yet. |
Fix: use the installed GameGen. In a development build, run the commands in a terminal instead of using the buttons.
A project that will not open
| Symptom | Cause | Fix |
|---|---|---|
| Clicking a project does nothing. The underlying error is “Project is outside this instance’s scope”. | This GameGen is limited to one folder, and the project is outside it. | Copy the game folder into that folder, then choose Open project and pick the copy. |
| New game reads “This build creates projects only inside …” | The same limit, when creating. | Choose that folder, or one inside it, under Location. |
| “The project is saved, but could not be opened.” | The project was created, but opening it failed. | Choose Open project again, or close the dialog and use Open project on the welcome screen. Do not create the game a second time. |
| Not an Unreal project | The folder has no .uproject at its root and its gamegen.json does not name the unreal engine. | Open the folder that contains the .uproject file, not its parent. |
Recording and forks
| Message | Cause | Fix |
|---|---|---|
| “Lou needs its recording tools. They are not installed yet (Lou looks for them at …).” | The one-time Python environment is missing. | Run the two commands the view shows, then choose Check again. See Set up recording. |
| “Lou needs its recording tools, and the Python that runs them was not found: …” | louTrainer.converter.python names a path that does not exist. | Set it to a Python that has the recording tools, or run the command the view shows with that Python’s path. Then choose Check again. |
| Lou could not open the recording, then “The Lou viewer could not be loaded. Check the connection (its files are fetched on first use) and try again.” | The viewer’s files could not be fetched. | Check the connection, then open the run again. |
| Lou could not open the recording, then “This system’s web view is too old to show Lou recordings (it lacks WebAssembly SIMD). Update the operating system and try again.” | The system’s web view is too old. | Update the operating system. |
| “The Lou viewer stopped unexpectedly. Open the recording again to carry on.” | The viewer stopped. | Close the run and open it again. |
| “The recording builder script was not found: …” | louTrainer.converter.script names a missing file. | Correct the path in .unrest/gamegen.json. |
| No runs recorded yet | The runs folder does not exist yet. | Play a run to GameOver. See Record a run. |
| “error: the replay did not run (exit …). Build first (ue.mjs build); see …” | The project is not built, or the editor failed to start. | Choose Build, then fork again. |
Tasks
| Symptom | Cause | Fix |
|---|---|---|
A task returns to Todo with a comment that starts [QA REJECTED] | Unreal QA found a defect. | Nothing. The coder reads the comment and fixes it. |
| A task stays in Review and QA runs again | QA hit an environment problem. | Check the editor connection and close any other Unreal Editor. |
| A task is in Blocked | It failed its checks too many times, or it needs you. | See Unblock a task. |
Still stuck
- Installing and updating: launcher troubleshooting.
- NPCs and the Awaken view: Awaken troubleshooting.
Next steps
Last updated on