Skip to content

Compatibility

Supported Versions & SHA-1 Check

Dusk recognizes specific clean dumps of the original game by their SHA-1 hash. This page lists the currently supported builds and explains how to confirm — without piracy or bypass — whether a copy you legally own is supported.

UPDATED 2026-05-106 minBeginner

Independent guide

Independent fan-made guide. Not affiliated with Nintendo, The Legend of Zelda, Twilight Princess, Twilit Realm, or Dusk. We do not host, link to, sell, mirror, or distribute ROMs, ISOs, disc images, game files, copyrighted assets, keys, cracks, or bypass tools. Use your own legally obtained copy.

Why supported versions matter

Dusk expects a clean, supported copy. The reimplementation maps addresses, file structures, and behaviors derived from specific original builds. If your copy doesn’t match a known SHA-1, Dusk may fail to recognize it, refuse to launch, or behave unpredictably.

Current supported versions

The following builds are currently listed by the Dusk project:

BuildSHA-1Status
GameCube USA75edd3ddff41f125d1b4ce1a40378f1b565519e7supported
GameCube EUR2601822a488eeb86fb89db16ca8f29c2c953e1casupported

Last checked 2026-05-10. Source: https://github.com/TwilitRealm/dusk

What SHA-1 means

SHA-1 is a hash function that produces a 40-character fingerprint for a file. Two files that produce the same SHA-1 are byte-identical for practical purposes; two files that produce different SHA-1 values are different files, period. Dusk uses SHA-1 to confirm that a user-owned copy is one of the supported builds.

How to compare a hash safely

Compute the SHA-1 of your own file and compare the resulting string against the table above. Standard built-in tools work:

  • macOS / Linux: shasum -a 1 yourfile or sha1sum yourfile
  • Windows PowerShell: Get-FileHash -Algorithm SHA1 yourfile

See the dedicated SHA-1 walkthrough for screenshots and the equivalent commands on each platform.

What unsupported means

If your hash doesn’t match a listed build, Dusk will likely report an “unsupported version” error. Common reasons:

  • Your copy is from a region or revision Dusk doesn’t list.
  • Your file has been modified, repacked, or trimmed.
  • The file is corrupt — try recomputing the hash on a fresh copy of your own file.
  • You ran the wrong file through the hash command.

Future support note

Troubleshooting links

Related guides