Launcher: Existing game build is not shown after updating to RC9 #141

Closed
opened 2026-11-16 08:34:49 +00:00 by BeanBot · 8 comments
Member

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-rc5 and rc, remain inside LongshotLauncher-data\builds, beside LongshotLauncher.exe.

Launcher log

The reporter attached five files named longshot_log.txt and longshot_log.1.txt through .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 under D:\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%\LongshotLauncher was empty; portable data is in LongshotLauncher-data.

Still needed

  • Launcher log from the portable data folder, if present.
  • Exact location of LongshotLauncher-data / launcher executable (only the build paths are known).
  • Windows version and whether the issue happens consistently.

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 .txt files are game runtime logs; relevant smaller logs were attached for investigation.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571746937860784168) ## 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-rc5` and `rc`, remain inside `LongshotLauncher-data\builds`, beside `LongshotLauncher.exe`. ## Launcher log The reporter attached five files named `longshot_log.txt` and `longshot_log.1.txt` through `.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 under `D:\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%\LongshotLauncher` was empty; portable data is in `LongshotLauncher-data`. ## Still needed - Launcher log from the portable data folder, if present. - Exact location of `LongshotLauncher-data` / launcher executable (only the build paths are known). - Windows version and whether the issue happens consistently. ## 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 `.txt` files are game runtime logs; relevant smaller logs were attached for investigation.
Author
Member

Files from the Discord report:

Files from the Discord report: - [image.png](https://git.magicbean.dev/attachments/54f722fe-d664-4407-add7-63d70291fd53)
Author
Member

From Discord:

The reporter says %LOCALAPPDATA%\LongshotLauncher is 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 in LongshotLauncher-data) and whether the existing game-build folder is still present and where it is.

From [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571746937860784168): The reporter says `%LOCALAPPDATA%\LongshotLauncher` is 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 in `LongshotLauncher-data`) and whether the existing game-build folder is still present and where it is.
Author
Member

From Discord:

Reporter confirms they use the Run portable option and that both existing game folders remain present, named v3.0.0-rc5 and rc. Their locations are not yet known. %LOCALAPPDATA%\LongshotLauncher is empty; advised to check LongshotLauncher-data beside LongshotLauncher.exe for launcher data/logs. Please provide the folder locations and portable log if available.

From [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571746937860784168): Reporter confirms they use the **Run portable** option and that both existing game folders remain present, named `v3.0.0-rc5` and `rc`. Their locations are not yet known. `%LOCALAPPDATA%\LongshotLauncher` is empty; advised to check `LongshotLauncher-data` beside `LongshotLauncher.exe` for launcher data/logs. Please provide the folder locations and portable log if available.
Author
Member

From Discord:

Reporter confirms both existing build folders (v3.0.0-rc5 and rc) are inside LongshotLauncher-data\builds in portable mode, beside LongshotLauncher.exe. %LOCALAPPDATA%\LongshotLauncher is empty. They ask where the launcher log is; none has been provided.

From [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571746937860784168): Reporter confirms both existing build folders (`v3.0.0-rc5` and `rc`) are inside `LongshotLauncher-data\builds` in portable mode, beside `LongshotLauncher.exe`. `%LOCALAPPDATA%\LongshotLauncher` is empty. They ask where the launcher log is; none has been provided.
Author
Member

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:

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1571746937860784168/1571809031205421136): 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: - [longshot_log.txt](https://git.magicbean.dev/attachments/29b4a3fa-f008-48c1-a0b5-9b5e4a6790d6) - [longshot_log.1.txt](https://git.magicbean.dev/attachments/a962bb4e-10c3-4004-bd70-f77c0430e0e2) - [longshot_log.2.txt](https://git.magicbean.dev/attachments/7a70fdae-0343-43d2-8981-4d094ddd7dc5) - [longshot_log.3.txt](https://git.magicbean.dev/attachments/41af257b-e3d4-4b88-9f4c-8e2c538852fb)
Author
Member

From Discord:

Reporter attached five Longshot runtime logs (longshot_log.txt and .1–.4), not launcher logs. They confirmed portable mode and that both existing build folders, v3.0.0-rc5 and rc, remain inside LongshotLauncher-data\builds. No further information is needed from the reporter right now; launcher log remains unavailable.

From [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1571746937860784168): Reporter attached five Longshot runtime logs (`longshot_log.txt` and `.1`–`.4`), not launcher logs. They confirmed portable mode and that both existing build folders, `v3.0.0-rc5` and `rc`, remain inside `LongshotLauncher-data\builds`. No further information is needed from the reporter right now; launcher log remains unavailable.
Author
Member

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\builds contains folders rc and v3.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](https://discord.com/channels/1569849200047427645/1571984777253228568/1571984777253228568): 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\builds` contains folders `rc` and `v3.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.
Author
Member

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.

From [Discord](https://discord.com/channels/1569849200047427645/1572350087483367625/1572350087483367625): 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/LongshotLauncher#141
No description provided.