Support database

Dusk known issues and workarounds

This page is designed to become the highest-value page on the site: a living support database organized by symptom, platform, Dusk version, and workaround.

Updated May 12, 2026
Official Dusk project backdrop used as visual context for known issues.
Known issue pages should move users from symptom to official release, workaround, or reproducible GitHub report.
Quick answer: update to the latest official Dusk release first. Then isolate the problem: launch, disc image, input, graphics, mobile storage, save migration, or performance.

Launch failures

App does not open on macOS

Check whether the current release supports your macOS version and chip. If macOS blocks the app, use the normal right-click Open flow for first launch. If the app crashes immediately, update Dusk and check GitHub Issues.

Windows opens and closes silently

Try a short ASCII-only path such as a folder under your user directory, then retest. Non-English usernames and protected folders can be useful debugging variables.

Linux permission error

Mark the binary executable and keep the app in a folder where it can create data files.

Disc image errors

Disc image did not pass verification

Dusk expects a supported clean GameCube Twilight Princess disc image. A modified ISO, wrong region, incomplete dump, or random download can fail. See disc image safety.

Modded ISO will not load

Do not test mods through a modified base ISO first. Confirm clean Dusk launches with a supported image, then apply Dusk-compatible mods separately.

Input and controller issues

Controller does nothing

Test Dusk with a simple controller profile before custom Steam Input or third-party remappers. If you use Steam Deck, read the Steam Deck guide.

Gyro or mouse aim feels doubled

Do not enable two aim systems at once. Choose native Dusk input or Steam Input mapping, then retest.

Graphics and display issues

Visual bugs after installing textures

Remove the texture pack and test clean Dusk. If the bug disappears, move the issue to texture pack compatibility instead of engine troubleshooting.

Mobile visual artifacts

Update to the newest official release. Some Android GPU issues have been addressed by release workarounds, especially on Adreno devices.

Mobile issues

For Android, separate three problems: APK install, app data access, and rendering. If the APK will not install, verify the file came from the official release and that the device supports arm64. If Dusk opens but cannot find files, use the app's data-folder route where available. If the game loads but visuals look broken, update first and then document device model, GPU, Android version, and Dusk version.

For iOS, sideloading, app storage, and save access are usually the hard parts. Keep iOS notes separate from Android notes so search users can scan quickly.

Save migration issues

Dolphin saves and Dusk saves are not always interchangeable by simple copy-paste. Back up saves before moving files, and keep one test save separate from your main playthrough.

Version and source links

Latest official release

Before debugging, compare against the newest public release.

Open latest release

Official bug tracker

Use this only after you can describe a reproducible issue on clean Dusk.

Open GitHub Issues

How to report a new bug

Report reproducible engine bugs at official GitHub Issues.

Known issues page keyword coverage

This page should cover the phrases users search after the download: Dusk Twilight Princess not working, Dusk disc image rejected, Dusk Android visual bug, Dusk Steam Deck controller not working, Dusk texture pack not loading, and Dusk save migration. The page should remain a fix database, not a generic FAQ.