Launcher: Existing game build is not shown after updating to RC9 #141
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
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
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher#141
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Reported on Discord
What happened
After updating Longshot Launcher, the home screen asks the reporter to build the game from scratch and asks for the game dump, although the launcher previously detected an existing build. The launcher still counted one version using 34.8 GB, but no existing build was offered on the home screen.
Steps to reproduce
The reporter opens Longshot Launcher after updating it; the home screen displays “Build your game” and a Build button, with no option to select an existing build.
Expected behavior
The existing build should be detected and offered for use, rather than prompting for a fresh build.
Actual behavior
The launcher asks for the original game dump (.nup/.nx or romfs and exefs) to build again. Screenshot shows “Builds v3.0.0-rc.5” and launcher v1.0.0-rc.9.
Launcher version and channel
Longshot Launcher v1.0.0-rc.9 (release candidate). Screenshot also shows game build v3.0.0-rc.5, rc channel.
System
Windows is implied by the D:\ paths in screenshots/logs; Windows version unknown. The reporter uses Run portable. Both existing game folders,
v3.0.0-rc5andrc, remain insideLongshotLauncher-data\builds, besideLongshotLauncher.exe.Launcher log
The reporter attached five files named
longshot_log.txtandlongshot_log.1.txtthrough.4.txt; these are Longshot game runtime logs, not the launcher log. Inspected files show game runs of v3.0.0-rc.5 and v3.0.0-rc.3 using paths underD:\Games\zelda\LongshotLauncher-data\builds\.... The newest inspected log identifies an NVIDIA GeForce RTX 5050 Laptop GPU (driver 616.92) and Intel UHD Graphics. No launcher log has been provided.%LOCALAPPDATA%\LongshotLauncherwas empty; portable data is inLongshotLauncher-data.Still needed
LongshotLauncher-data/ launcher executable (only the build paths are known).Related context
The reporter previously showed an SSL update-check failure; Longshot Launcher #120 tracks that separate TLS issue. The screenshots/logs do not establish that it caused the missing build. PR #105, first included in nightly-84-e5c36756, improves explanations when game files cannot be used; it does not address this missing-build detection symptom.
Attachments
Screenshots show the “Build your game” page and the earlier failed SSL update check. Submitted
.txtfiles are game runtime logs; relevant smaller logs were attached for investigation.Files from the Discord report:
From Discord:
The reporter says
%LOCALAPPDATA%\LongshotLauncheris completely empty, so no launcher log was found there. It remains unknown whether they used the installed or portable launcher (portable data is beside the executable inLongshotLauncher-data) and whether the existing game-build folder is still present and where it is.From Discord:
Reporter confirms they use the Run portable option and that both existing game folders remain present, named
v3.0.0-rc5andrc. Their locations are not yet known.%LOCALAPPDATA%\LongshotLauncheris empty; advised to checkLongshotLauncher-databesideLongshotLauncher.exefor launcher data/logs. Please provide the folder locations and portable log if available.From Discord:
Reporter confirms both existing build folders (
v3.0.0-rc5andrc) are insideLongshotLauncher-data\buildsin portable mode, besideLongshotLauncher.exe.%LOCALAPPDATA%\LongshotLauncheris empty. They ask where the launcher log is; none has been provided.Updated with more from Discord: Added the submitted game logs, hardware and portable build-path details; noted PR #105 is related only to unusable-file explanations, not this detection symptom.
Files:
From Discord:
Reporter attached five Longshot runtime logs (
longshot_log.txtand.1–.4), not launcher logs. They confirmed portable mode and that both existing build folders,v3.0.0-rc5andrc, remain insideLongshotLauncher-data\builds. No further information is needed from the reporter right now; launcher log remains unavailable.From Discord:
Additional report: the launcher home screen shows v3.0.0-rc.5 as the default build (35.0 GB), but clicking Play starts v3.0.0-rc.3. File Explorer shows
LongshotLauncher-data\buildscontains foldersrcandv3.0.0-rc.3, with no rc.6 folder. Screenshot also shows launcher v1.0.0-rc.9. This is consistent with the missing/misidentified existing build after updating already tracked here.From Discord:
From Discord (2026-11-17): reporter is on Windows 11, Longshot Launcher v1.0.0-rc.10, and has a v3.0.0-rc.7 build. After updating the launcher, opening it shows the “Build your game” page rather than recognizing the existing build (screenshot attached in conversation). They say the previously suggested update to nightly-115-321a9e1c did not fix it. They don't know how to find the launcher log.