Dusk v1.0.0 Known Issues & Troubleshooting (Verified May 2026)

Real GitHub-tracked bugs at Dusk v1.0.0 launch — Apple Silicon crashes, Windows non-English usernames, Linux AppImage permission, Android Ilia hair, and verified workarounds.

Published 2026-05-10

This is a verified issues list — every entry below is sourced to a real GitHub issue, official FAQ entry, or multi-user community report. We don’t list “common errors” we haven’t actually seen reported.

If your specific problem isn’t here, check the Dusk GitHub issues page for the latest reports, or ask in the Dusk team’s Discord at discord.gg/dusktp (run by them — not us).

Last updated: 2026-05-10. We refresh as patches ship and as the issue list evolves.

Crashes & Launch Failures

Apple Silicon Mac crashes on launch

Issues: #826, #805, #779 Symptom: “Dusk quit unexpectedly” dialog with crash report on first launch on M1/M2/M3/M4 Macs. Status (May 2026): Open. Not all Apple Silicon Macs affected — many users report Dusk runs fine. Workarounds:

Try the Intel (x86_64) build via Rosetta 2 (slower but may avoid the M-series crash path)
Try a different Graphics Backend in Settings → Prelaunch → Graphics Backend — cycle Metal / Vulkan / OpenGL
Watch the linked issues for updates and newer fixes

Windows: silent launch failure with non-English username

Issue: #807 Symptom: Dusk doesn’t launch at all when the Windows username contains non-Latin characters (e.g., C:\Users\ミドナ). No error dialog. Status: Open. Workarounds:

Launch Dusk from a Windows account with an English-only username
Or extract Dusk to a path that doesn’t go through the user folder (e.g., D:\Games\Dusk)
Don’t use OneDrive’s redirected Documents folder

Linux AppImage: “Couldn’t create directory ‘/TwilitRealm’”

Issue: #818 Symptom: On Linux (CachyOS reported), an AppImage variant fails to launch with:

[fatal] [dusk] Unable to get PrefPath: Couldn't create directory '/TwilitRealm': 'Permission denied'

Status: Open. Affects an AppImage variant; the official .zip builds are unaffected. Workarounds:

Use Dusk-v1.0.0-linux-x86_64.zip (or linux-arm64.zip) instead of any AppImage
If you’ve run the AppImage already, clean up: sudo rm -rf /TwilitRealm

Mac: “Dusk is damaged and can’t be opened”

Cause: Gatekeeper quarantine attribute. Dusk is not notarized. Status: Expected behavior on first launch (not a bug per se). Fix: In Terminal:

xattr -cr /Applications/Dusk.app

Then launch normally. Or right-click → Open the first time.

Random crashes mid-cutscene / mid-gameplay (Windows)

Issue: #819 Reporter setup: Windows 11, i9-13980HX, RTX 4060, Xbox One controller. Symptom: Crashes during specific cutscenes (Zelda dialog, Ordona dialog) and during Faron Woods poison lake platforming. Reporter had Fast Spinner, Fast Iron Boots, and fullscreen enabled. Status: Open. Workarounds:

Disable cheat-style options (Fast Spinner, Fast Iron Boots) before key cutscenes
Try windowed mode instead of fullscreen
Watch the linked issue for updates

Disc / ROM Issues

”The selected disc image did not pass hash verification”

Cause: Your dump’s XXH128 doesn’t match Dusk’s expected hash. Most often: corrupted dump, wrong region, or a modified/scene release. Fix:

Verify the SHA-1 of your dump:
- Windows: Get-FileHash -Algorithm SHA1 yourdump.iso
- macOS / Linux: shasum -a 1 yourdump.iso
Should match exactly:
- 75edd3ddff41f125d1b4ce1a40378f1b565519e7 (NTSC-U)
- 2601822a488eeb86fb89db16ca8f29c2c953e1ca (PAL)
If neither matches, re-dump using the legal dump guide with checksum verification ON.

”The selected game is not supported by Dusk”

Cause: You loaded a GameCube Japan, Wii, Wii Korea, or Wii U HD disc image. v1.0.0 only accepts GameCube NA and PAL. Fix: Use a GameCube NA (GZ2E01) or PAL (GZ2P01) disc dump. Other regions are on the project’s roadmap (per README).

Modded ISO won’t load

Behavior: Hash mismatch is expected when you modify the ISO (e.g., applying the Linkle character mod). Dusk shows a warning but offers a “Continue anyway” path:

“Just install the [mod] as you usually would directly to the GameCube or Wii .iso and then direct Dusk to that modded .iso file and confirm that you still want to use it when it tells you it’s probably corrupted or modified.” — TomoAries, r/pcgaming, 14 upvotes

So mods work — Dusk just warns you that the hash differs from the known-good values.

Controller & Input Issues

Selecting non-GCN controller with WUP-028 adapter creates 4 GiB junk file

Issue: #810 Symptom: With Nintendo’s WUP-028 GameCube USB adapter connected, selecting a non-GCN controller from the dropdown writes a junk file of 2^32 + 32 bytes (~4 GiB), mostly zeros. Causes long hangs on HDDs and brief hangs on SSDs. Status: Open. Workarounds:

Disconnect the WUP-028 adapter before changing controller selection
Or pick the matching GCN controller in the dropdown

Cannot bind keyboard on macOS

Issue: #830 Symptom: Keyboard binding through Dusk’s controller config UI doesn’t work on macOS. Status: Open. Workaround: Use a controller until patched.

Steam Controller leaves mouse cursor on screen

Issue: #811 Symptom: When using a Steam Controller, the mouse cursor remains visible during gameplay. Status: Open.

AYN Thor rumble doesn’t work

Issue: #812 Status: Open. AYN Thor handheld supported; rumble specifically broken.

Issue: #824 Symptom: You can rebind game controls but not the menu / UI navigation controls. Status: Open enhancement request.

Issue: #814 Symptom: D-Pad doesn’t navigate menus. Status: Open enhancement request.

Right shoulder / Z mapping confusion

Community report: r/pcgaming user LargeBirdInATree:

“Right Bumper is mapped to Right Trigger under ‘Digital Trigger’. I don’t know what ‘Digital Trigger’ is, and pressing left and right shoulder doesn’t appear to do anything.”

Workaround: In Settings → Input → Controller → Configure Controller → Triggers, the “Digital Trigger” terminology refers to whether the triggers report as analog or digital. Cycle through configurations until the bumpers + triggers match what your physical controller expects.

Graphics / Display Issues

Pulsating bloom at unlocked framerate

Issue: #825 (label: Interpolation) Symptom: Bloom effect pulses noticeably when Settings → Video → Rendering → Unlock Framerate is enabled. Status: Open. Workaround: Lock framerate (toggle Unlock Framerate off) until patched.

21:9 cutscenes cropped vertically

Issue: #813 Symptom: On ultrawide (21:9) displays, in-game cutscenes are cropped at top and bottom. Status: Open. Workaround: Use 16:9 for cutscenes, or lock 4:3 aspect ratio (Settings → Video → Display → Lock 4:3 Aspect Ratio) — the latter ensures consistent framing throughout.

Bo’s house table shadows cropped

Issue: #815 Symptom: Specific lighting bug at Bo’s house in Ordon Village. Status: Open.

Mini-map moves when mirror mode enabled

Issue: #809 Symptom: Cosmetic positioning bug for mini-map in Mirror Mode. Status: Open.

First-person switch hiccups

Issue: #816 Symptom: Brief hitch when switching to first-person view. Status: Open.

Internal resolution looks like 4:3 even with 4:3 lock off

Community report (r/SteamDeck): User SEANPLEASEDISABLEPVP (3 upvotes):

“the ‘internal resolution’ setting for me defaults to 1216×896 for some reason, it looks like a 4:3 aspect ratio even though that’s turned off. EDIT: Nevermind, I had to toggle fullscreen lol.” Workaround (verified): Toggle fullscreen on/off in Settings → Video → Display → Toggle Fullscreen.

Audio Issues

Recording Mode kills music until restart

Issues: #821, #832 Symptom: Toggling Settings → Interface → Recording Mode off doesn’t re-enable music; you have to restart Dusk to get music back. Status: Open. Workaround: Restart Dusk.

Mobile Issues (Android & iOS)

Android: Ilia missing hair (and other model glitches)

Issue: #827 Symptom: On various Android devices (Retroid Pocket 5, Samsung Galaxy series, others), the character model for Ilia renders without hair. Confirmed by multiple Reddit users: splashtext, Shizzawn, OutsiderInCider (r/SteamDeck thread). Status: Open. Cosmetic, not gameplay-breaking.

Android: Galaxy S26 Ultra visual bug (“string cheese”)

Issue: #801 Status: Open.

iOS: Save location not user-accessible

Issue: #804 Symptom: Save file lives in iOS app sandbox; not visible in Files app for backup or transfer. Status: Open. Workaround: Use Finder iPhone backup (encrypted full device backup includes Dusk’s save).

Save Migration Issues

Dolphin save not appearing in Dusk

Cause: Wrong filename, wrong path, or wrong save format. Fix (per official FAQ):

The Dolphin save file is at:
- Windows: Documents\Dolphin Emulator\GC\USA\Card A\01-GZ2E01-gczelda2.gci
- macOS: ~/Library/Application Support/Dolphin/GC/USA/Card A/01-GZ2E01-gczelda2.gci
- Linux: ~/.local/share/dolphin-emu/GC/USA/Card A/01-GZ2E01-gczelda2.gci
The Dusk save folder is at:
- Windows: %APPDATA%\TwilitRealm\Dusk\USA\Card A\
- macOS: ~/Library/Application Support/TwilitRealm/Dusk/USA/Card A/
- Linux: ~/.local/share/TwilitRealm/Dusk/USA/Card A/
Replace USA with EUR if you’re using the PAL disc

If your Dolphin save is in .raw format (single memory card image instead of separate .gcis), use Dolphin’s Memory Card Tool to extract the individual .gci first. Or change Dusk’s Settings → Prelaunch → Save File Type to Card Image to use .raw directly.

Save loaded but progress doesn’t carry over

You may have loaded an empty save slot. In TP, load from Card A (which is what 01-GZ2*-gczelda2.gci represents). The other slots are typically empty.

Performance Issues

Stuck at 30 FPS even with Unlock Framerate enabled

Community report (r/pcgaming): User Thr0waway_Joe:

“I can’t get it past 30fps. Even with unlocked fps” Status: Sporadic, no definitive root cause as of v1.0.0. Possible causes:

VSync still capping (Settings → Video → Display → Enable VSync → toggle off)
Monitor refresh rate cap
Graphics backend bottleneck — try a different one (Settings → Prelaunch → Graphics Backend)

Performance lower than expected

Lower Internal Resolution (Settings → Video → Resolution)
Cap framerate to 60 instead of unlocked
Disable post-processing (Settings → Video → Post-Processing → Bloom)
Try a different Graphics Backend (D3D12 / Vulkan are usually fastest on PC; Metal on Mac; OpenGL ES on mobile)

“Disputed” / “Resolved” Reports

”Mirror Link battle unwinnable at uncapped FPS” (DISPUTED)

A user (r/pcgaming, WiglyWorm, 10 upvotes) claimed:

“I just watched a video where someone was playing this game uncapped and certain things like the mirror link battle were actually unwinnable due to FPS changes.”

Counter-clarification by liamwilliams93:

“on this recomp it still runs the game logic at 30fps and uses interpolation to render at higher frame rates”

Verdict: Dusk’s design decouples logic (30 Hz) from rendering. The “FPS-tied gameplay break” is not how Dusk works. The original user may have been thinking of a Dolphin or earlier port-attempt patching scheme. Dusk’s interpolation does not affect game logic timing.

Bugs Already Fixed (Don’t Re-Report)

These were fixed in v0.x.x → v1.0.0 — if you’re on v1.0.0, they don’t apply:

Windows Unicode paths in appdata folder (#767, #755 — closed)
Gyro sensitivity axes swapped (#764, #759 — closed)
Linux x86_64 didn’t start after configuring settings (#788 — closed)
GameCube controller B / X swap default (#732 — closed)
Recording Mode mute streams initial bug (different from #821) (#735 — closed)
Mac: Fails to open after clicking livesplit setting (#773 — closed)

If you’re hitting one of these, you may be on an older version. Update to v1.0.0.

How to Report a New Bug

If your problem isn’t on this list:

Check the Dusk GitHub Issues page (someone may have reported it)
If new, file a new issue on GitHub with:
- OS + version
- Dusk version
- Steps to reproduce
- Screenshots if visual
Or post in the Dusk team’s Discord at discord.gg/dusktp

We don’t accept bug reports for Dusk — we’re an independent content site, not the project. Reports go directly to TwilitRealm.

Version History on This Page

Date	Change
2026-05-10	Initial publication based on v1.0.0 GitHub issues snapshot + community reports from launch day

This page reflects state at v1.0.0 as of 2026-05-10. Dusk releases patches frequently — bookmark and check back, or watch the GitHub releases page for the latest.

← Pillar guide · Install guides