Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/CollapseLauncher/Collapse/llms.txt

Use this file to discover all available pages before exploring further.

Collapse determines whether a game is installed by checking the path stored in its per-game metadata. If the game was installed through the official HoYoverse launcher or moved after initial setup, Collapse may not find it automatically.Steps to resolve:
1

Use 'Locate Game' or migrate

On the game’s home page, click the Install button. If the game is already installed, the dialog will offer you the option to locate an existing installation. Point it to the folder containing the game’s main executable.
2

Check drive availability

If the drive letter the game was installed on has changed (e.g., after plugging in an external drive), the launcher resets GameFolder to its default on startup and sets itself to first-install mode. Reconnect the drive, then use the locate option above.
3

Verify folder permissions

Collapse checks that it can write to GameFolder. If permission is denied, it treats the installation as absent. Right-click the game folder, go to Properties → Security, and ensure your user account has full control. Alternatively, relocate the folder to a path you own.
4

Clear metadata and restart

In Settings → App Settings, click Clear Metadata Cache. This forces the launcher to re-download game metadata on the next start, which resolves stale or corrupted preset information.
The repair function verifies local game files against a repair index fetched from the CDN. Failures can have several causes.Common causes and fixes:
  • CDN connectivity — switch to a different CDN in Settings → Content Delivery Network and retry. The launcher tries fallback CDNs automatically, but a manual switch can help if one CDN is consistently unreachable.
  • Disk errors — if the console shows Disk Corruption Detected or CRC errors, run chkdsk /f /r on the affected drive before retrying repair.
  • Insufficient disk space — repair downloads replacement files before deleting the broken ones. Ensure you have free space at least equal to the largest single file being repaired.
  • Antivirus interference — some antivirus products quarantine game files while repair is reading them. Temporarily exclude the game folder from real-time scanning, run repair, then re-enable the exclusion.
  • HTTP repair override — if repair repeatedly fails on a specific file, enabling EnableHTTPRepairOverride in the config (config.ini) forces the repair to use plain HTTP instead of HTTPS for downloading replacement files. This is a last resort for environments where HTTPS is blocked or inspected.
Do not force-quit the launcher during repair. An incomplete repair can leave the game in an inconsistent state. If the launcher crashed during repair, start it again — it will detect the previous partial operation and offer to resume or restore.
Speed is unexpectedly low:Check whether the speed limiter is active in Settings → Network Settings → Limit Download Speed. If it is enabled and the limit value is very low, downloads will be throttled even if your connection supports higher speeds.Also confirm that the preallocated downloader is enabled (IsUsePreallocatedDownloader). Disabling it falls back to the legacy chunked downloader, which may be slower on some storage configurations.Downloads stop or timeout:
  • Increase HttpClientTimeout in Settings (default: 90 seconds) if you are on a slow connection.
  • Try switching the CDN — the launcher selects your preferred CDN first and falls back automatically on failure, but a proactive switch can help if the selected CDN is slow.
  • If you are behind a corporate proxy or VPN, configure the proxy settings in Settings → Network Settings → HTTP Proxy.
Download resumes incorrectly after interruption:If a download was interrupted and restarts from zero each time, the CDN you selected may not support partial/range requests. GitLab and CNB do not support partial downloads. Switch to Cloudflare, DigitalOcean, or GitHub, all of which support range requests.
Black window or immediate exit:The launcher performs a startup check on the configured GameFolder. If the drive is unavailable, it resets to first-install mode, which opens the OOBE (out-of-box experience) setup instead of the main screen. This is expected behavior — complete the setup again or reconnect the missing drive.Fatal error console appears:When an unhandled exception occurs at the top level, the launcher closes the main window, opens a fallback console window, and prints the full exception. The console reads:
FATAL ERROR ON APP MAIN() LEVEL AND THE MAIN THREAD HAS BEEN TERMINATED!!!
From this console you have two options:
  • Press any key to exit.
  • Press R to restart the launcher. Before restarting, it checks whether a recovery update is available and applies it automatically if found.
Recovery update:If a newer launcher build is available at the time of the crash, the fatal error console will download and apply it automatically. After the update completes, the launcher restarts. This is the built-in crash recovery / fallback update mechanism.Corrupt metadata:A corrupted metadata cache can prevent the launcher from initializing correctly. In Settings → App Settings, click Clear Metadata Cache and restart, or delete the _metadatav3 folder inside GameFolder manually.
On the first-time setup page, select your language from the Language dropdown before proceeding. The selection is applied immediately to the OOBE UI and saved as AppLanguage in the config.If the launcher starts in the wrong language after an update or reinstall, open Settings, change the language, and restart. See Localization for a full list of supported locale IDs.
The ShowRegionChangeWarning setting (default: false) controls whether the launcher shows a confirmation dialog before changing the active game region. If this is unexpectedly enabled, go to Settings → App Settings and toggle it off.
A restart is required after toggling this setting for the change to take effect. The Settings page will show a warning indicator until you restart.
Collapse passes launch arguments to the game process and monitors for game-level crashes. If the game crashes and the launcher was configured to minimize or go to tray on game launch, it returns to the foreground and displays the crash details.Common steps:
  1. Check game repair (see the repair failure entry above) to rule out corrupted game files.
  2. Review game-specific settings via the in-launcher game settings page — Collapse exposes the same settings as the official launcher.
  3. If the game is Genshin Impact and you are seeing HDR-related issues, check the ForceGIHDREnable setting in config.ini.

​
Enabling console logging

The launcher’s console output is disabled by default in release builds to avoid opening an extra window. Enabling it writes detailed log output that is useful for diagnosing issues.
1

Open Settings

Click the gear icon in the launcher.
2

Enable the console

In App Settings, toggle Enable Console on. This sets EnableConsole to true and switches the logger to LoggerConsole, which writes to both a log file and a console window.
3

Optionally enable game logs

Once the console is enabled, an additional Include Game Logs toggle becomes visible. Enabling it (IncludeGameLogs = true) captures log output from the game process as well as the launcher.
4

Reproduce the issue

Perform the action that causes the problem. The console window will show real-time output. Log files are also written to <GameFolder>/_logs/.
You can toggle the console window’s visibility from the system tray icon even after the launcher is running — right-click the tray icon and select Show Collapse console window.

​
Sentry error reporting

Collapse uses Sentry to automatically report unhandled crashes and exceptions to the development team. The configuration key is SendRemoteCrashData (boolean, default: true). What is sent:
  • Exception type, message, and stack trace.
  • Launcher version, build channel (Stable/Preview), branch, and commit SHA.
  • Selected CDN.
  • Launcher log file (up to 2 MB) attached to the report.
What is NOT sent:
  • Your IP address (explicitly set to null in the Sentry scope).
  • Any personally identifiable information.
  • Game account data.
Opting out:
1

Open Settings

Go to Settings → App Settings → Debug.
2

Disable crash data

Toggle Send Remote Crash Data off. This sets SendRemoteCrashData to false and shuts down the Sentry SDK for the current session.
You can also opt out permanently by setting the environment variable DISABLE_SENTRY=1 before launching the executable. When this variable is detected, the toggle in Settings is disabled and the opt-out cannot be reversed from the UI.
Opting out means crashes will not be automatically reported to the developers. If you encounter a reproducible bug, please report it manually on GitHub (see below).

​
Reporting issues on GitHub

If you encounter a bug that is not covered by the above steps, open an issue on the Collapse Launcher GitHub repository: https://github.com/CollapseLauncher/Collapse/issues Before opening an issue:
  1. Search existing issues to avoid duplicates.
  2. Enable the console and capture the full log output for the session in which the problem occurred.
  3. Note your launcher version (shown in Settings → About), Windows version, and which game/region is affected.
  4. Include steps to reproduce the problem.
Attaching logs: Log files are stored at <GameFolder>/_logs/. Attach the most recent log file (or paste the relevant portion) to your issue report. If Sentry error reporting is enabled, a crash report may have already been sent automatically — you can mention this in the issue.

Build docs developers (and LLMs) love

Get started for freeTalk to us