Linux x86_64 AppImage
Steam Deck uses the Linux x86_64 AppImage in this guide, not the Windows zip. The Windows build through Proton can be useful for experiments, but it is not the clean Dusk Light install path.

Steam Deck uses the Linux x86_64 AppImage, but the setup feels different because you move between Desktop Mode and Gaming Mode. Start in Desktop Mode, put the AppImage and your own supported dump somewhere stable, then add Dusklight to Steam if you want a console-style launch flow.
Last reviewed: September 19, 2026 against GitHub v2.0.0
The Deck route starts from Dusklight-v2.0.0-linux-x86_64.AppImage, the same official Linux asset used by other x86_64 Linux machines. The difference is workflow. You normally download and prepare the file in Desktop Mode, then optionally add it as a non-Steam game for Gaming Mode. SteamOS is Linux, so Vulkan and AppImage behavior still matter, but the Deck also adds Steam Input, controller templates, resolution scaling, battery limits, and quick-access performance settings.
Steam Deck uses the Linux x86_64 AppImage in this guide, not the Windows zip. The Windows build through Proton can be useful for experiments, but it is not the clean Dusk Light install path.
Desktop Mode is the easiest place to download, move, mark executable, and first-launch the AppImage. Gaming Mode is better treated as the second step after the app already works.
The official README requires a supported graphics backend, and the Deck path depends on Vulkan through SteamOS. Keep SteamOS and system updates in mind when comparing your results with older issue reports.
Before playing for hours, decide whether you want default controls, Steam Input changes, gyro aim, or an external controller. Many Deck-specific reports are really input or performance context problems.
These commands can be run from Konsole in Desktop Mode. They keep the Deck install path close to Linux while making the Steam Deck-specific workflow explicit.
sha256sum ./Dusklight-v2.0.0-linux-x86_64.AppImageUse this after downloading from GitHub. It records the exact Linux x86_64 AppImage used on Steam Deck.
chmod +x ./Dusklight-v2.0.0-linux-x86_64.AppImageThis is the common Desktop Mode terminal step when the file manager does not mark the AppImage executable for you.
./Dusklight-v2.0.0-linux-x86_64.AppImageLaunch from terminal once before adding it to Steam. If something fails, you will see AppImage, Vulkan, or driver messages that Gaming Mode may hide.
Linux x86_64 AppImage
Stay in this language while comparing Dusk Light downloads, file sizes, update times, and platform notes.
GitHub marks v2.0.0 as the latest stable release. Steam Deck uses its 45.1 MiB Linux x86_64 AppImage.
v1.4.0 overhauled renderer performance and added full mouse controls. Those changes affect Deck performance, touchpad, and gyro setups.
v2.0.0 restores simultaneous gyro and joystick aiming and fixes the mouse cursor appearing with mouse-based gyro controls, including on Steam Deck. It adds the mod browser and Save Manager. Record SteamOS, resolution, graphics settings, and launch mode if problems remain.
The project closed this Deck performance issue after the v1.4.0 renderer overhaul. Keep it as historical context when comparing older builds or settings.
Open sourceA merged pull request added mouse as a gyro input source and mentions Steam Deck compatibility. This supports describing gyro as a real Deck concern rather than generic controller filler.
Open sourceThis Wii-style pointer request remains open. v1.4.0 added full mouse controls, but that does not provide every Wii pointer behavior requested here.
Open sourceA closed report says ReShade did not work with the Windows build on Steam Deck/Linux through Proton. It reinforces why this guide starts from the native Linux AppImage.
Open sourceAll files listed here point to the official TwilitRealm/dusklight GitHub release assets. Dusk Light does not mirror binaries or host copyrighted game data.