# Dusklight: a reverse-engineered Twilight Princess port for PC, Android and iOS

> Dusklight is a C++ reimplementation of Twilight Princess built on the GameCube decompilation and the Aurora runtime. It asks you to dump your own disc, and it is honest about the Wii version's HUD mismatch.

**TwilitRealm/dusklight** — Dusklight brings a classic adventure to PC and mobile platforms with a variety of fixes and improvements.

- Repository: https://github.com/TwilitRealm/dusklight
- Website: https://twilitrealm.dev
- Stars: 5,594 · Forks: 410
- Language: C++
- License: CC0-1.0
- Published: 2026-09-22 · Updated: 2026-09-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/twilitrealm-dusklight

## What Dusklight reimplements, and who it is aimed at

Dusklight is not an emulator. The README calls it a reverse-engineered reimplementation of Twilight Princess, which means the game logic is rebuilt from the Twilight Princess decompilation rather than executed by a virtual machine. That distinction decides who the project is for: people who want the original game running natively on PC and mobile platforms, with fixes and enhancements layered on top, and who are willing to supply their own game disc to get there. The project states plainly that it does not provide any copyrighted assets, so a copy of the original game is a prerequisite, not an optional extra. It also states that it aims to be as accurate as possible to the original while adding new options, enhancements and tools for customizing the experience, which places it between a straight port and a modding platform. The repository carries a mods/ directory and a tools/ directory at the top level, and the README credits the TP speedrunning community alongside the decompilation teams, so the intended audience includes players who treat the game as something to be tuned rather than merely replayed.

## How the decompilation and Aurora runtime fit together

Two dependencies define the architecture. The first is the Twilight Princess decompilation at zeldaret/tp, which the README says Dusklight is based on. The second is Aurora, the runtime the project is built against; the README closes with an Aurora badge and credits the Aurora developers. Aurora is the layer that turns the reimplemented game code into something that runs on modern graphics APIs, which is why the setup notes name D3D12, Vulkan 1.1 and Metal as the minimum requirement rather than describing a renderer of Dusklight's own. The top-level layout supports this reading: platforms/, sdk/, libs/ and extern/ sit beside src/ and include/, with CMakeLists.txt, CMakePresets.json, cmake-variants.yaml and a flake.nix for Nix users. The consequence worth stating is that Dusklight inherits the decompilation's state of completion. The README notes that the decompilation is currently only matching for GameCube, and that even when you play Dusklight with a Wii disc you will be presented with the GameCube version's HUD and certain other specificities. That is not a bug report; it is the project describing the boundary of what its foundation can currently express.

## Installing Dusklight and getting to a first playable state

The README splits setup into two steps: dump your game, then install Dusklight. For the first step it points to the Dolphin wiki article on ripping games, and suggests converting the dump with Dolphin or with nodtool to save space, turning an .iso into an .rvz. There is no command in the README for this, so the exact invocation depends on the tool you choose. What the README does state is the compatibility boundary: Dusklight currently supports all commercial discs except for Wii's Korean release.

```bash
# Dump the disc with your own tooling (see the Dolphin wiki article linked in the README),
# then optionally convert the .iso to .rvz with Dolphin or nodtool to save space.
```

The second step is not documented in the repository itself. The README says to visit the official installation guide at https://twilitrealm.dev/install/ for full instructions, and the project's homepage is https://twilitrealm.dev/. That is the only install path the README gives, so treat it as authoritative and treat anything else as unaffiliated. If you would rather compile it yourself, the README directs you to docs/building.md and notes that pull requests are welcome, with one condition spelled out: contributions that are primarily AI-generated will be closed. Building from source also means meeting the same GPU floor, since that requirement is about the runtime, not about the prebuilt package.

```bash
# From source: read docs/building.md first. The repository ships CMakeLists.txt,
# CMakePresets.json, cmake-variants.yaml and flake.nix at the top level.
```

## The Wii disc HUD mismatch and the hardware floor

Two limitations deserve to be read before you commit. The first is the HUD mismatch already described: play from a Wii disc and you get GameCube presentation, because the decompilation Dusklight builds on is only matching for GameCube. If your memory of the game is the Wii release, with its mirrored world and pointer controls, Dusklight will not reproduce that framing for you today. The second is the graphics API floor. A GPU supporting D3D12, Vulkan 1.1 or Metal is the stated minimum. For older devices the README says best-effort support is provided for D3D11 and OpenGL ES on Android, but that it will not achieve full accuracy or performance. The phrase best-effort is doing real work there: it means the project is not promising that an older phone or an old integrated GPU will produce a faithful result, only that it may run. The README adds that your experience with specific hardware, operating systems and drivers may vary, which is the honest way of saying there is no compatibility list. If your device sits below the D3D12, Vulkan 1.1 or Metal line, Dusklight is the wrong tool for you right now, and an emulator that already targets your hardware is the better bet.

## Dusklight against Dolphin as an alternative

The obvious alternative is Dolphin, and the difference is architectural rather than a matter of polish. Dolphin emulates the GameCube and Wii hardware, so it runs the disc you already have as the console would, and its compatibility story is about emulation accuracy across a large library of titles. Dusklight reimplements one game in C++ on top of the decompilation and Aurora, so its accuracy story is about how faithfully that reimplementation reproduces Twilight Princess, and its compatibility story is about which of your discs it accepts (all commercial releases except Wii's Korean version). Dolphin can also do the disc-to-.rvz conversion the README recommends, which makes it a useful companion even for Dusklight users. Where Dusklight differs in practice is the surface it exposes: new options, enhancements and customization tools, plus a mods/ directory in the repository and a community the README credits through the speedrunning scene. If you want one emulator for a shelf of games, Dolphin is the fit. If you want one game rebuilt natively with hooks for modification, that is the gap Dusklight occupies.

## Licence, build cost and what upgrades look like

Dusklight is released under CC0-1.0, which is a public domain dedication rather than a permissive software licence in the MIT or Apache sense. For anyone embedding or redistributing code, that distinction is worth reading in full rather than skimming, and it is not legal advice to say so. Note also that the licence covers the project's own code, not the game: the README is explicit that Dusklight does not provide any copyrighted assets and that you must provide your own copy of the original game. On upgrade cost, the release cadence is visible in the tags. v1.4.1 landed on 2026-06-16, then v2.0.0 on 2026-09-19 and v2.0.1 on 2026-09-20, with the last push to the repository on 2026-09-22. That is a major version bump followed by a patch within a day, which suggests you should read the v2.0.0 notes before moving from the 1.4.x line rather than assuming a drop-in upgrade. The build side carries its own cost: CMake, the presets, the Nix flake and a vendored extern/ tree mean a source build pulls in a real toolchain, and the README's code conventions document in docs/code-conventions.md signals that patches are held to a house style.

## Conclusion

Dusklight suits players who already own a Twilight Princess disc, can dump it, and have a GPU that speaks D3D12, Vulkan 1.1 or Metal; anyone without a legal disc copy, or on a D3D11 or OpenGL ES device expecting full accuracy, should stay away. Before installing, verify three things: that your disc is not the Korean Wii release, that your GPU meets the API floor, and that you are downloading from https://twilitrealm.dev/ rather than a mirror, since the README states any other site is unaffiliated and may be promoting AI-generated misinformation.

## FAQ

### What does Dusklight do?

It is a reverse-engineered reimplementation of Twilight Princess that runs on PC and mobile platforms, based on the Twilight Princess decompilation and the Aurora runtime. The README says it aims to be as accurate as possible to the original while adding new options, enhancements and tools.

### Where can I find Dusklight?

The README states that the official website is https://twilitrealm.dev/ and that the full installation guide lives at https://twilitrealm.dev/install/. It also warns that any other website is not affiliated and may be promoting AI-generated misinformation.

### How do I install Dusklight?

Setup has two steps: dump your own copy of the game, then install Dusklight. The repository itself does not carry the install steps; the README directs you to the official installation guide at https://twilitrealm.dev/install/ for full instructions.

### How do I use Dusklight with a Twilight Princess disc?

You must dump your own copy of the game, following the Dolphin wiki article the README links, and you can convert the .iso to .rvz with Dolphin or nodtool to save space. Dusklight supports all commercial discs except for Wii's Korean release, and Wii discs are presented with the GameCube version's HUD.

### How do I use mods in Dusklight?

The README does not document a mod installation procedure; it points to the official installation guide at https://twilitrealm.dev/install/ for setup instructions. What the repository does show is a top-level mods/ directory alongside tools/, which is where the project keeps modification-related files.

## Sources

- [License: CC0-1.0](https://github.com/TwilitRealm/dusklight/blob/main/LICENSE)
- [Project website](https://twilitrealm.dev)
- [README](https://github.com/TwilitRealm/dusklight/blob/main/README.md)
- [Releases](https://github.com/TwilitRealm/dusklight/releases)
- [TwilitRealm/dusklight on GitHub](https://github.com/TwilitRealm/dusklight)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/twilitrealm-dusklight