HelixSR 1.4.3 Rolls Back an Update After AMD Handheld Visual Bugs

An experimental upscaling project has given AMD handheld PC owners an unusual option: use NVIDIA's older DLSS neural reconstruction model without an NVIDIA graphics card. But the rapid pace of HelixSR development has already exposed the trade-off. On October 9, developer lonewolf0622 published HelixSR 1.4.3, reverting the main code to version 1.3.0 after newer builds caused ghosting and smearing on some RDNA 3 GPUs under Windows.

That makes the latest release a stability-focused rollback, not a straightforward feature upgrade. The developer says versions 1.4.0 through 1.4.2 introduced visual problems that have not yet been reproduced reliably. Until the cause is understood, the newer QSSM and PRSM presets and the single-file DLL are not part of 1.4.3.

What HelixSR actually does

HelixSR is an unofficial hybrid upscaler for Direct3D 12 games. It presents an FSR 3.1-compatible interface to a game, then uses NVIDIA's DLSS Model E neural network to reconstruct the image through a custom DirectX 12 compute implementation. The idea is to use the game's existing motion-vector, depth and color inputs while running the reconstruction work on AMD graphics hardware.

This is not NVIDIA adding DLSS support to Radeon GPUs, nor is it a new neural network trained by the HelixSR developer. The project is independent of NVIDIA and AMD. Its repository says it does not bundle NVIDIA's model weights. Instead, its setup process obtains an NVIDIA DLSS DLL from an official source with user consent and builds the required local network files.

The approach is especially interesting for Steam Deck and ROG Ally-class devices because these machines are often limited by graphics performance and power. An alternative upscaler could improve the trade-off between sharpness and frame rate in supported games. That possibility is real, but the project's compatibility and performance claims need to be read carefully.

Which devices and games are supported?

The developer lists AMD RDNA 1 and newer GPUs as the target, with Radeon Vega and Radeon VII not currently supported. The implementation targets Direct3D 12 titles using FSR 3.1. Games without a suitable integration may need a separate compatibility tool, and DirectX 11 or native Vulkan support should not be assumed.

The developer reports testing primarily on an AMD BC-250 under Linux, with community feedback helping address ROG Ally X behavior on Windows. That is not the same as a complete validation matrix for every handheld, driver and game. Reports of better performance than FSR 4 come from early community measurements, not a broad independent benchmark suite.

What changed in version 1.4.3?

According to the official release notes, 1.4.3 restores the same DLL code and setup used by 1.3.0. The version number changes, and the installer can still update existing installations with the required network files. Users coming from a 1.4.x release are instructed to extract the new release into a separate folder, run setup again and use the installer to update selected games.

For handheld owners, the practical takeaway is simple: treat HelixSR as an experiment, not a guaranteed performance upgrade. Keep a backup of any original game files, read the developer's instructions and expect differences between games. The project is also not fully open source: the repository says its setup scripts are available under Apache 2.0, but the HelixSR binary is distributed under a freeware license without its full source code.

HelixSR's rapid rollback is a reminder that clever graphics workarounds can be promising and fragile at the same time. The project is worth watching, especially for older AMD handhelds, but the safest conclusions will come from repeatable testing after its Windows RDNA 3 issues are resolved.

Read the project README for supported configurations and the latest release details.