Before you update
The current stable release is v2.0.2. Version 2.0.2 expands Save Manager imports across regions and GameCube/Wii, fixes startup on some Macs with AMD GPUs, and fixes file selection on some sideloaded iOS installations. Version 2.0.1 fixed save handling, an Android Vulkan startup crash, and Intel Mac startup.
Keep a note of your existing version, platform, selected disc and data folder. Download from the official Twilit Realm release page, and match the build to your device. You still need your own supported Twilight Princess disc image; an app update does not include the game.
Back up saves and settings first
If you are running v2.0.0 or later
- Finish saving in the game and return to the launch menu. In Settings, open the Prelaunch tab and choose Open Save Manager. Select your supported disc first if the control is unavailable. Pending disc or data-folder changes may need a restart.
- Select your save, choose Export Save…, then Save + mod data (.dusksave). This includes the save and its associated mod data. Save only (.gci) exports the game save without that mod data.
- Save the export somewhere outside Dusklight’s app-managed storage. Check that the exported file exists, and keep a separate copy before replacing the app.
Create Backup and View Backups provide local recovery copies. They live with your save storage, so they are not a substitute for an external export before uninstalling or clearing app data.
If your old version has no Save Manager
Preserve the existing app data before updating. Where available, use Open Data Folder to locate it, close Dusklight, and copy the folder to a separate location. Do not delete an old portable installation until you have identified and copied its data. If you cannot access the data on your device, resolve that before uninstalling.
A .dusksave export is not a full app backup: keep installed mod packages, texture packs and settings separately. Record controller mappings and graphics settings. On desktop, copy the data folder while the app is closed; on mobile, keep any accessible files outside the app’s storage.
Update on Windows, macOS or Linux
Close Dusklight after backing up. Keep the old package until the updated app starts and your progress is confirmed.
Windows
Choose the x86_64 ZIP for an Intel/AMD PC or the ARM64 ZIP for Windows on ARM. Extract the complete archive into a new folder and launch its executable. Check which data folder it uses before playing, especially if your old copy used Portable Mode. Point your shortcut to the new executable after verification. See the Windows install guide for files and requirements.
macOS
Choose ARM64 for Apple Silicon or x86_64 for an Intel Mac. Extract the ZIP, quit the old app, then replace the application in Applications after securing your backup. Version 2.0.1 fixed Intel Mac startup; v2.0.2 adds a fix for startup on some AMD GPU Macs. The macOS guide covers the matching builds and launch requirements.
Linux and Steam Deck
Download the matching AppImage, make the new file executable and launch it. Steam Deck uses the x86_64 AppImage. Update any desktop shortcut or Steam non-Steam entry that still points to the old filename. Keep the same data location and check your saves before removing the previous file. Follow the Linux or Steam Deck guide for setup details.
Updating on Android
Export your saves first, then get the official ARM64 APK from the Android install guide. Use Android’s package installer to open it. If it offers to update your existing installation, confirm that you selected the official package.
If installation fails or asks you to uninstall the existing app, stop and check the error, package source and backup. Do not clear storage or uninstall as a first troubleshooting step: app-managed saves may be removed.
After updating, check disc access and load an existing save. The current build includes the v2.0.1 Vulkan startup fix, but this does not guarantee compatibility with every GPU or driver. If the app still fails, follow the Android startup and file-access checks.
Updating on iPhone or iPad
Back up accessible saves before changing a sideloaded installation. Continue with the same installation method you already use. The official guide supports AltStore with the Twilit Realm source and iloader with an imported IPA; iloader updates require importing the new IPA manually.
Version 2.0.2 fixes file selection on some sideloaded installations. Follow the iOS install guide and official iOS instructions for that method’s signing, trust and Developer Mode requirements. If the method requires deleting the old app, secure an external backup first. Signing errors alone do not show that your game save is damaged.
Check the updated app before you play
- Launch the newly downloaded app, not an old shortcut. Confirm you used the current release file for your platform and architecture.
- Check the selected disc and data folder. Re-select your own disc image if its path or mobile file permission has changed.
- Open an existing save and confirm its slot and progress. If it is missing or appears empty, stop before saving over it.
- Check controller mappings, touch controls, graphics and enabled mods. If a mod fails, test with it disabled and check its compatibility notes. Keep the external backup until you have verified normal play and saving.
If something goes wrong
The app opens, but my save is missing
First compare the disc region, Save File Type and data folder with the old installation. Version 2.0.2 lets Save Manager import saves between different regions and between GameCube and Wii. Use it to import your external copy for the intended disc; do not overwrite your only backup.
I have a backup in Save Manager
Open View Backups, inspect the intended backup and use Restore This Backup…. Read the confirmation before replacing the current save. Export any current progress you want to keep first. Local backups are useful only while their storage is still available.
A copied GCI file is not being loaded
Version 2.0.1 loads the exact expected GCI filename to avoid treating duplicate backups as memory-card files. Import a custom-named file through Save Manager instead of adding more renamed copies to the save folder.
Can I return to an older version?
Keep the old app and a separate pre-update backup, but do not assume an older release can read newer save or mod data. Check the relevant release and mod compatibility notes before trying a downgrade.
For an unresolved crash, record the app version, OS, device or GPU, graphics backend, enabled mods and exact error. Check the upstream issue tracker for a matching current report.
Sources and scope
This independent guide was checked against the release notes, official installation instructions and versioned Save Manager code. These are source-verified instructions; we have not tested an update on every device or sideloading method.