fix(launcher): recognize source-built game folders #63
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/ui
area/updates
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!63
Loading…
Reference in a new issue
No description provided.
Delete branch "Anarkkie/LongshotLauncher:fix/source-built-game-folders"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source-built Longshot games can place the executable in the game folder's root, which the launcher currently marks as not built and cannot start. Recognizing the builder's source and packaged layouts lets these games use the normal Play and save handling.
Prefer
bin/longshot[.exe]when present. Otherwise acceptlongshot[.exe]at the root only when its platform renderer is beside it; a packaged root helper alone does not enable Play. The working directory and existing save arguments are unchanged. Both Windows and Linux layouts emitted bynx2/make_game.pyare covered.Fixes #53.
Validation
Code
4c238d6, based on accepted main01f2797; the final check against main9b3d202applies cleanly. The following documentation commit only records acceptance.cdf3d9d8), Kokiri Forest, Windows 11 Pro 10.0.26300, RTX 3080 Ti / NVIDIA 610.88, Ryzen 7 5800X3D / 32 GB. Both root and bin layouts loaded the intended isolated save, rendered the settled scene, accepted movement and exited 0. Bin won when both executables existed. All 70 original save hashes remained unchanged. Runs are recorded indocs/tested-configurations.md.Native acceptance ran offscreen with
HOS_HEADLESS=1,HOS_AUDIO=0,RX_VK_LOAD=createandRX_VK_PRECOMPILEunset. A prior automatic all-program preload stalled at the intro and was quit cleanly; both controlled layout runs use the same loading policy. No rendering/performance improvement or native Linux gameplay acceptance is claimed.The standalone full Windows core runner retains the
SelfUpdateChecksfailure reproduced on unchanged main. That and the other Windows runner/filesystem corrections are submitted separately in #64. A private integration with those fixes and the player/save framework passes Windows/Linux strict core 1,120 / 1,145 and headless UI 290 / 289; those are combined results, not standalone counts for this PR.Screenshots
Same authored fixture, compiled launcher at 960 x 600; launch-check details.
Scope and risk
The fallback requires the supported executable-plus-renderer layout. A failed packaged cleanup leaving a stale root renderer plus a later missing bin executable remains a narrow ambiguity. This does not change installed layouts, launcher arguments or game files.
If merged after #55, retain that feature's explicit Linux
--userrouting in the new launch-command test; the standalone main-based assertion here preserves main's existing Linux behavior. This combined case has been tested locally.AI-assisted implementation and independent source review with OpenAI Codex. No game files, real saves or game-derived assets are included.
Same authored root-layout fixture, rendered in the compiled launcher at 960 x 600. Before: the existing root executable is reported missing and Play is disabled. After: the supported executable-plus-renderer layout enables Play; the probe launch also verified executable, working directory and save argument. Native root/bin acceptance and its hardware are recorded in the description.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.