HelixSR runs NVIDIA's DLSS network on AMD hardware

Model E as plain Direct3D 12 compute shaders

The technical claim at the centre of HelixSR is specific. The project runs NVIDIA's DLSS Model E upscaling network as standard Direct3D 12 compute shaders, without NVIDIA Tensor Cores, without an NVIDIA driver, without CUDA and without ROCm. That is the whole trick. Nothing about the upscaler requires the hardware NVIDIA designed it for, only a shader environment that can execute the network. Once that is true, the rest follows from DLSS itself, and the project documentation lists the behaviour it inherits: every quality mode from native, which the DLSS documentation calls DLAA, through Ultra Performance, plus dynamic resolution. So a player on an older AMD card is not getting a lookalike upscaler with different artefacts. They are getting the same network, executed by a different backend, and the observable image quality differences come from the game and the mode rather than from an approximation.

Frame generation through the game's own Streamline

Since version 2.0, the same DLL also carries experimental support for NVIDIA's DLSS frame generation, and the implementation detail explains how it can work in games that ship DLSS. HelixSR's FidelityFX DLL, HelixSR-fsrfg\amd_fidelityfx_dx12.dll, does both upscaling and DLSS frame generation, and when a game switches on DLSS frame generation, HelixSR runs NVIDIA's own frame generation through the game's own Streamline. The plumbing in OptiScaler terms is given explicitly: FGInput = nvngxfg and FGNvngxReplacement = HelixSR, which means HelixSR registers itself as a frame-generation provider next to OptiScaler's own. AMD FSR and Intel XeSS frame generation stay available in the menu, so this is a menu of options rather than a takeover. Two settings are exposed for NVIDIA's implementation, light mode at 310.9.16 which is the default, and full mode at 310.3, one click away in the HelixSR Scaler menu with QuickFlow for extra speed. The 2.0.0 release notes are blunt about the status: frame generation is a work in progress, may not work at all in some games or on some GPUs, and even when it runs the performance and image quality may be poor, with visual artifacts or instability.

What the frame generation time figures actually say

The 2.0.0 notes carry the kind of numbers that usually get left out, so they are worth reading carefully. Light mode uses about 20 to 30 percent less GPU time per generated frame than at the start of 2.0's development, and the stated costs on the BC-250 are 2.2 ms at 1080p, 3.6 ms at 1440p and 4.2 ms at 4K. Full mode is about 6 to 11 percent cheaper than its own starting point. The same release notes describe Ultra Performance as running the network at twice the render size with a Lanczos pass scaling to the screen, roughly a third less GPU time, with NetworkResolution = full giving the sharpest image. Upscaling at DLAA and Ultra Quality is about 15 to 18 percent cheaper for the same image, and there are faster 32-bit paths for GPUs without fast 16-bit math. Two caveats apply to every figure here. They are measured on one AMD BC-250, and the maintainer is explicit that other GPUs and Windows are not tested by the maintainer, so treat the percentages as relative movement of a single configuration rather than as a performance claim for your card.

Installing with HelixSR Desktop or with the setup scripts

Two paths exist. The recommended one is HelixSR Desktop, downloaded from the latest release, with a Windows .exe installer and an .AppImage or .deb for Linux and Steam Deck. It sets HelixSR up on the machine once and then installs it per game with one button. The manual path is a zip you unpack and a setup script you run.

1. Download `HelixSR-2.0.0.zip` and extract it into a folder you keep (for example `C:\HelixSR` or your home folder).
2. Close your games and run the setup in that folder:

On Windows you double-click helixsr-setup.bat, and on Linux or Steam Deck you run ./helixsr-setup.sh, either in a terminal or by double-clicking and choosing Run in terminal. The first run asks before each download from NVIDIA, which covers the DLSS DLL holding the network, NVIDIA's DLSS frame generation DLLs and NVIDIA's NGX core, then builds everything locally, which takes a few minutes. The setup then lists your games across Steam, Epic, GOG, Xbox, Heroic and Lutris and asks per game: install? [s/f/n]. Press Enter to install. s selects HelixSR Scaler, where you then pick DLSS in the game, and f selects the FSR drop-in for games with FSR 3.1, where you pick AMD FSR. Games with anti-cheat get the FSR drop-in and never HelixSR Scaler by default.

Anti-cheat games get the FSR file replaced instead

The two installation modes are not equally invasive, and the difference decides where HelixSR is usable. HelixSR Scaler is the full option: it puts HelixSR behind the game's own DLSS, FSR or XeSS option with an in-game menu opened with Insert, and it is explicitly not for online games or games with anti-cheat. The FSR drop-in is the conservative one: only the game's FSR file is replaced, which is the only route offered to titles with anti-cheat, and the in-game choice becomes AMD FSR. The manual route is spelled out for people who prefer it, where the files of the helixsr-scaler folder go next to the game's .exe, OptiScaler.dll is renamed to dxgi.dll, and the HelixSR-fsrfg folder that the setup built is copied next to it. One detail deserves attention from anyone with several games. The setup keeps track of what it installed per game, so running the setup of a new version asks installed. Update? [Enter/s/f/r/n], where Enter updates, s and f switch the mode and r removes it. HelixSR Desktop 1.1.0 adds the same per-game update and removal, updates itself, and can put back the version a game had before.

RDNA 1 and RDNA 2 are the target, and one GPU was actually tested

The project is explicit about who it is for. HelixSR is focused on older graphics cards, especially AMD RDNA 1 and RDNA 2, with the stated goal of helping gamers get more from hardware they already own. RDNA 3 and newer GPUs may work, but the project states they are not the focus of the work. The testing status is narrower still: version 2.0.0 was developed and tested on the AMD BC-250, which is gfx1013 on Linux with Mesa RADV, and other GPUs and Windows are not tested by the maintainer. Frame generation adds a second requirement on top of that, since the experimental feature needs a Direct3D 12 game that has DLSS frame generation. In practice that means a 2020 and 2021 era AMD card on Linux, or a Windows machine nobody has validated for you, running a game with a DX12 path. The README points to a GPUs section for the compatibility list and the current testing status, and that list is the first thing to read before anything else.

An unofficial project under a custom freeware licence

Two legal and practical realities come with the project. The first is that it is independent and unofficial, with no affiliation to or endorsement from NVIDIA or AMD, which means it carries no support relationship with either company and no guarantee that the DLSS components it downloads will keep working the way the project expects. The repository carries SOURCE.md and THIRD_PARTY_NOTICES.md alongside a LICENSE file, and the licence is the HelixSR Freeware License, a custom licence that GitHub classifies as Other rather than as a standard open source licence. That classification is not a technical detail. A freeware licence may restrict redistribution or commercial use in ways that MIT or Apache 2.0 do not, and a project that ships NVIDIA's own DLLs has a third party's terms layered on top of its own. Read the licence file before putting it in a build pipeline, and treat the answers to those questions as your legal review rather than as this article's opinion. The second reality is the maintenance one: releases v2.0.0, v1.9.3 and v1.9.2 all landed between 2026-10-16 and 2026-10-19, the last push was on 2026-10-19, and 2.0.0 is labelled experimental in the release header. The project is moving quickly and labelling its most interesting feature as unfinished.

Editorial conclusion

Adopt HelixSR if you own an RDNA 1 or RDNA 2 card, want DLSS quality modes without NVIDIA hardware, and can tolerate an unofficial build whose frame generation is still experimental. Skip it if you need a supported driver stack, if you play online or anti-cheat titles through the Scaler path, or if your organisation cannot accept a custom freeware licence that a GitHub cannot classify. Before running it, confirm your GPU is one the project lists, read the HelixSR Freeware License in the repository, and try version 2.0.0 in a single title first, because the maintainer developed and tested it on an AMD BC-250 under Linux with Mesa RADV and did not test other GPUs or Windows.

Frequently asked questions

Official sources

1. Issues
2. lonewolf0622/HelixSR on GitHub
3. README
4. Releases