fix: autoexec.cfg loads the actual default level, not a missing "start" placeholder#20
Open
nickschuetz wants to merge 1 commit into
Open
fix: autoexec.cfg loads the actual default level, not a missing "start" placeholder#20nickschuetz wants to merge 1 commit into
nickschuetz wants to merge 1 commit into
Conversation
The previous loadlevel command pointed at "start" -- a placeholder inherited from the engine's ScriptOnlyProject template. The project ships three real levels (Neighborhood, NeighborhoodAlex, CharacterSample) and Registry/game.setreg already declares Neighborhood as the default; this aligns autoexec.cfg with it. Before: GameLauncher boots, autoexec runs "loadlevel start", the level system reports "Requested level not found: 'start'", and the launcher parks in a non-rendering state with no obvious cause (black window). New users running the launcher with no extra flags hit this on first run. After: GameLauncher loads Neighborhood automatically. Verified on Fedora 44 / NVIDIA RTX 2080 Ti / Vulkan RHI: title screen renders, score / lives / home-time HUD active, character control works. Signed-off-by: Nick Schuetz <nschuetz@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
autoexec.cfgshipped withloadlevel start, but no level named "start" exists in the project. On launch, the level system logsRequested level not found: 'start'and the launcher parks in a non-rendering state -- a new user sees a black window with no indication of what went wrong.The placeholder
startwas inherited from the engine'sScriptOnlyProjecttemplate; this project never customized it.Fix
Change the autoexec to load
Neighborhood, which matches the default already set inRegistry/game.setreg.An alternative would be to delete the
loadlevelline entirely and letRegistry/game.setregdrive the default; I went with the minimum-edit form so the autoexec.cfg stays a working starting point that downstream forks / template-derived projects can copy from. Happy to switch to the delete form if maintainers prefer.Verification
Built and ran on Fedora 44 / NVIDIA RTX 2080 Ti / Vulkan RHI.
Verified visually:
From Game.log:
Game Level Load Time: [...] Level Levels/Neighborhood/Neighborhood.spawnable loadedpresentRequested level not foundwarningsNote for maintainers
The same
loadlevel startplaceholder ships in O3DE'sScriptOnlyProjecttemplate atTemplates/ScriptOnlyProject/Template/autoexec.cfg. Worth a separate engine-side fix to comment it out or change it to; loadlevel YourLevelNameso future template-generated projects don't inherit the same broken default. Happy to file a separate engine-side PR if useful.