From eec22d1ba6e3eeead6b04ef114fe1b65c8318816 Mon Sep 17 00:00:00 2001 From: Nick Schuetz Date: Fri, 22 May 2026 07:30:21 -0500 Subject: [PATCH] fix: autoexec.cfg loads the actual default level, not "start" 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 --- autoexec.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/autoexec.cfg b/autoexec.cfg index 66b4c3a..f1d7d71 100644 --- a/autoexec.cfg +++ b/autoexec.cfg @@ -1,6 +1,6 @@ ; edit this file to make it load whatever level you want on startup automatically ; You can also add additional commands in here that you want it to exec on startup. -loadlevel start +loadlevel Neighborhood ; uncomment the following line in any game packages that have all the ; assets precompiled, so that it doesn't try to launch the Asset Processor in