Dusk is now Dusklight

Dusklight is the current name for the project many users still search as Dusk Twilight Princess. This page explains the rename, the v1.2.0 file names, and which setup guide to use next.

Current v1.2.0 file names

The v1.2.0 release uses Dusklight- file names instead of the older Dusk- pattern. That is expected and does not mean you found the wrong project.

What changed in v1.2.0

• Current official release assets use the Dusklight-v1.2.0-* naming pattern.
• Experimental D3D11 on Windows and experimental OpenGL ES on Android create fallback routes for devices that cannot use the preferred graphics APIs.
• A capped FPS option helps handheld, laptop, and battery-sensitive users avoid uncontrolled rendering.
• Texture replacement can be toggled in-game, and a v1.1.1 mipmap replacement regression was fixed.
• Autosave safety, controller bind cleanup, shoulder analog values, macOS boot, and several crash or gameplay issues were improved.
• Adreno driver issues remain a known Android concern, so Android users should still record device and GPU details.

For rename history, v1.1.1 was the first official release under the Dusklight name. It also introduced desktop Change Data Folder support, Windows Portable Mode, new custom action binds, and PNG custom texture support. Users updating from an older Dusk build may experience the rename and the v1.2.0 feature changes at the same time.

Why this matters for searchers

For a while, users will type both names: Dusk Twilight Princess download, Dusklight download, Dusk v1.2.0, and Dusk renamed Dusklight. The safe answer is to keep the old search phrase visible, explain that Dusklight is the current name, and send users to the official release page.

This page avoids a common failure state: a user sees a Dusklight- file after searching for Dusk and assumes it is a copycat or mirror. It is the current official naming pattern.

How to read old Dusk guides

Older Dusk Twilight Princess guides are still useful when they explain general concepts such as supported disc images, texture replacement folders, Steam Deck setup, or Android APK installation. They become risky when they name old files, old issue status, or old workarounds as if nothing changed. Use this page as the bridge: if the guide says Dusk but the official release says Dusklight, follow the current Dusklight release for downloads and use the older guide only for background.

The safest rule is to separate app version, data folder, and game data. The app version should be the newest official Dusklight release. The data folder should be backed up before updates or portable-mode changes. The game data should be your own supported GameCube Twilight Princess disc image, not a file supplied by a download guide. That separation keeps the rename from turning into a troubleshooting mess.

Searchers also need to know which guide to open after the rename question is answered. If you are choosing a platform file, use download. If you already installed an older build, use update. If a graphics backend fails, use graphics backends. If saves, config, or texture folders are confusing after the rename, use save file location. If the app launches but input is wrong, use controls first and controller troubleshooting second.

Rename checklist before troubleshooting

1. Confirm the file came from the official TwilitRealm GitHub release.
2. Confirm the file name starts with Dusklight-v1.2.0- for the current release.
3. Confirm the platform suffix matches your device: Windows, Linux, Android, iOS, macOS arm64, or macOS x86_64.
4. Back up saves and config before replacing an older Dusk app folder.
5. Launch clean before adding texture packs, mods, controller profiles, or external frame limiters.

Next steps