What HelixSR actually is
Calling this "DLSS on Steam Deck" is shorthand, and it needs some unpacking. The Deck's custom AMD APU has no Tensor cores or other AI hardware. HelixSR gets around that by running the DLSS 3.7 model through standard compute shaders, with no Nvidia drivers, CUDA or ROCm.
The project's own documentation describes it as running DLSS's Model E network on AMD GPUs. It lists the Steam Deck, as an RDNA 2 part, among supported targets, using 8-bit math where that helps. The project says it is independent and unofficial. This is not Nvidia's hardware-backed DLSS arriving on a handheld. It is a community implementation of the same network on different silicon.
Early coverage described the idea as games still believing they are talking to AMD FSR 3.1 while the upscaling step is handed to DLSS. Games communicate with the mod via FSR 3.1, but the upscaling step uses DLSS 3.7. Current releases also offer a scaler route that works through a game's own DLSS, FSR or XeSS menu entry.
The setup, as XDA experienced it
XDA reports the install was simple. You download a zip from GitHub, unpack it and run the script inside. The script fetches what it needs, including the DLSS shaders for each game you choose.
The project's instructions match that account, with some caveats:
- Extract first. Unpack the archive into a folder you keep. Don't run it from inside the zip.
- Run the script. On Windows, run
helixsr-setup.bat. On Linux or Steam Deck, run./helixsr-setup.sh. The Deck can run it in a terminal, or you can double-click it and choose Run in terminal. - Expect a local build. The setup builds the upscaling network on your own device from a DLSS DLL downloaded from NVIDIA. It asks before each download. Linux needs Proton or Wine for the shader compiler.
- Start the game. The project says Insert opens the scaler's menu.
- Remove it if needed. An uninstaller restores the files it replaced.
Two details from the test are worth knowing:
- Launch options. XDA says the latest version needed nothing in Steam's launch options, though earlier versions did. The project says a
dxgi.dllloader needs no launch option on Linux. If the loader has to be namedwinmm.dllorversion.dllbecause the game already has adxgi.dll, you add aWINEDLLOVERRIDESlaunch option. - Old mods. XDA had to clear out several leftover OptiScaler installs first, because HelixSR installs as
dxgi.dll, as OptiScaler does. Remove old upscaler mods before installing.
XDA also saw an amusing side effect. Shadow of the Tomb Raider reported an RTX 4090 and complained about an outdated GPU driver. Horizon Zero Dawn loaded without comment.
The numbers
XDA tested two games. These are the author's own measurements, not a controlled lab benchmark.
| Game (preset) | Upscaler | Avg FPS | GPU FPS | Min FPS | GPU-bound |
|---|---|---|---|---|---|
| Horizon Zero Dawn Remastered (Very Low) | FSR 3.1.0 (stock) | 34 | 41 | 11 | n/a |
| Horizon Zero Dawn Remastered (Very Low) | HelixSR DLSS | 34 | 40 | 2 | n/a |
| Shadow of the Tomb Raider (High) | XeSS (stock) | 43 | 46 | 21 | 41% |
| Shadow of the Tomb Raider (High) | HelixSR DLSS | 45 | 48 | 23 | 40% |
The author calls the differences within experimental variance. He measured HelixSR's passes at roughly 3.1 to 3.9 ms per frame from the scaler's on-screen stats.
The 2 FPS minimum in Horizon Zero Dawn looks alarming. XDA cautions that it may come from first-launch shader compilation or another one-off glitch, and treats the stock row as more representative. I'd do the same. The 40–41% GPU-bound figures also belong only to the Tomb Raider rows.
Why the gains didn't show up
The key finding is that both games ran out of CPU before they ran out of GPU. An upscaler reduces GPU load. If the CPU is the bottleneck, a cheaper GPU pass can't lift the frame rate. This is general industry logic rather than something XDA proved with a CPU test, but it fits the near-identical averages.
Other coverage of the mod has focused on frame time. One Steam Deck test measured HelixSR at roughly 3.5 ms per frame at 800p, against about 4.5 ms for FSR 4. That's a different comparison from XDA's, and it measures the upscaler pass alone. A cheaper pass only shows up as higher FPS in a GPU-bound scene.
Image quality on an 800p panel
XDA couldn't see a meaningful difference on the Deck's 7-inch, 800p screen over a few hours of play. HelixSR looked slightly rougher at some sharp edges where FSR or XeSS looked a little cleaner. The author notes the screenshots weren't taken from identical spots, so that observation is inconclusive.
This is a subjective impression from one tester on a small screen. It doesn't show that HelixSR looks better or worse in general. The author suggests it might matter more in GPU-bound games, or docked at higher output resolutions.
Caveats and cautions
- A fast-moving project. XDA notes that version 1.0 arrived October 5 and 3.2.0 followed by October 30. The GitHub release page marks 3.2.0 as a pre-release. Your experience may differ from his.
- No HelixSR frame generation in 3.x. The project says AMD FSR and Intel XeSS frame generation remain in the Scaler menu, and HelixSR 2.0.0 keeps the old DLSS frame generation. That is why XDA didn't test frame generation, and nothing in his results speaks to it.
- Anti-cheat. XDA warns against installing it in anti-cheat games because you'll get flagged. The project's release notes say its FSR drop-in route is meant to work with anti-cheat games, but a separate write-up says the Scaler route isn't for online games or anything with anti-cheat (from Gaming on Steam's coverage). Whatever the documentation says, the consequence is up to the game's publisher. Don't modify protected games unless you accept the risk.
- API coverage. Early coverage said the mod only supported DirectX 12 games. The project's later releases added DirectX 11 and Vulkan support through the Scaler route.
- Back up first. Keep a way to restore the original files. The project says the uninstaller or the game's file verification in Steam are the recovery routes if a game fails to start.
Who might benefit
XDA suggests some games could gain more if they're already GPU-bound, or when docked above 800p. It also suggests faster handhelds with Z2 Extreme chips could see improvements, though native FSR 4 support is on the way for them and may close the gap. The project itself says RDNA 3 and newer GPUs "may work" but aren't its focus. XDA didn't test any of those cases.
For most Deck owners, the verdict is curiosity-driven. It costs nothing and, in this test, gained nothing visible. If you enjoy tinkering, set it up on a game you don't mind breaking, keep the uninstaller handy and try it in a GPU-heavy scenario. If you mostly play CPU-limited titles at 800p, your time is probably better spent elsewhere.