DLSS-Enabler for non-NVIDIA DirectX 12 GPUs

DLSS-Enabler's DirectX 12 target and native game requirement

DLSS-Enabler addresses a specific gap between game support and hardware support. Its stated purpose is to simulate the DLSS Upscaler and DLSS-G Frame Generation features on any DirectX 12 compatible GPU when the game natively supports DLSS2 and DLSS3. In practical terms, the target user has an AMD or Intel graphics device and a DirectX 12 game that already presents DLSS choices, but cannot use those choices with the game’s normal NVIDIA runtime. The requirement for native DLSS support is important. The project does not claim to add DLSS controls to a game that never exposes them.

The repository also carries a file named "DLSS for AMD and Intel - License.rtf", which confirms the intended hardware direction, although its contents are not available for further interpretation. The project is therefore better described as a compatibility package for exposed DLSS features, not as a general DLSS implementation for arbitrary DirectX 12 titles. A game that supports only ordinary upscaling, lacks a DLSS configuration menu, or does not support DLSS2 or DLSS3 falls outside the repository’s documented scope.

There is no supported game list, driver matrix, minimum GPU specification, or feature comparison in the repository documentation. Users therefore cannot use this repository alone to establish whether a particular card, driver, game build, and DLSS mode form a supported combination.

How the OptiScaler and XeSS update pipeline works

DLSS-Enabler acts as a packaging layer around OptiScaler. Its automation monitors the OptiScaler repository every six hours, downloads the latest `nvngx.dll`, and renames that library to `dlss-enabler-upscaler.dll`. The README identifies that filename as a requirement of DLSS-Enabler. This rename gives the installer a known library name that can replace the runtime component expected by the game.

The pipeline also fetches the latest `libxess.dll` from Intel’s XeSS repository. It then builds an installer with Inno Setup 6.2.0 and publishes the package as a GitHub release. According to the README, automated packages can include a nightly or stable OptiScaler release and the latest XeSS library. The release process therefore combines files from separate upstream projects rather than treating DLSS-Enabler as the implementation of either temporal upscaling or frame generation.

The local update script provides a narrower maintenance path for advanced users. It can request the `nightly` channel, select a named OptiScaler version, force the update, or skip XeSS. These choices also show where the packaging boundaries sit. OptiScaler supplies the replacement DLSS runtime, while `libxess.dll` comes from Intel. The repository does not document how the components behave inside each game or how conflicts are detected.

Installing a prebuilt DLSS-Enabler release

The simplest documented installation route is the Releases page, not a package manager or source build. The README recommends downloading the latest pre-built installer, which is described as containing the latest OptiScaler component, the latest XeSS library, and required preconfigured files. No package name, installation directory, installer filename, command-line switches, or administrator requirement is supplied, so those details cannot be added safely.

A new user’s first real use begins by obtaining that installer from the Releases page. The documentation does not say which in-game option must be selected, whether a game restart is required, or what visible output confirms success. The appropriate verification point is therefore the game’s existing DLSS menu: because the project targets games that natively support DLSS2 and DLSS3, that menu is the relevant place to look for an upscaling or frame-generation choice. The repository does not describe which hardware options that menu will expose after installation.

For advanced users who need to refresh the upstream OptiScaler library locally, the README gives these PowerShell operations:

.\update-optiscaler.ps1 -OptiScalerVersion nightly -Force

This requests the nightly OptiScaler update and forces it. A specific upstream version can instead be selected as follows:

.\update-optiscaler.ps1 -OptiScalerVersion v0.7.7-pre12 -Force

The version shown here is the README’s example, not a statement of the current packaged version. An existing XeSS library can be retained with:

.\update-optiscaler.ps1 -SkipXeSS

These scripts update project files. The documentation does not state that they install the result into a game or replace the prebuilt installer workflow.

Building DLSS Enabler with Inno Setup

Source packaging has a stricter dependency chain. The README instructs developers to install Inno Setup from the linked jrsoftware.org download page and states that version 6.2.0 is the optimal supported choice. It explicitly says to use neither an older nor a newer version, attributing the restriction to antivirus software that can produce false positives. The project expects the build to run through Inno Setup Editor using `DLSS enabler.iss`.

Before compiling a package, `libxess.dll` must be downloaded from Intel’s repository and placed in the `Dll version` subdirectory. Without it, the README says the setup build fails. After a successful build, the installer is written to the `Output` directory. The repository layout also contains `build-optiscaler.ps1`, but the README does not document its parameters or provide a command for invoking it.

This build path is primarily relevant to maintainers and advanced users. It does not explain how to sign the resulting installer, validate its contents, reproduce the automated nightly selection, or identify which game runtime directory receives the libraries. Those omissions limit independent release verification. The documented build should be treated as packaging work, not as a complete source compilation of the upscaler or frame-generation technology.

DLSS-Enabler limitations and NVIDIA runtime risk

The central limitation is the dependency on games that already support DLSS2 and DLSS3. DLSS-Enabler is not documented as a universal DirectX 12 wrapper, and it cannot be assumed to expose missing DLSS settings. Hardware compatibility is similarly broad in the description but unconstrained in the documentation. The phrase “any DirectX 12 compatible GPU” states a target, not a published test matrix, and the absence of a game or driver list leaves users without a reliable compatibility reference.

Frame generation also adds operational questions that the README does not answer. It does not document latency behavior, supported resolutions, refresh rates, multi-GPU configurations, HDR, borderless mode, capture tools, or conflicts with other runtime replacements. It also provides no troubleshooting guide for a black screen, unstable rendering, absent options, or a game update that changes the expected runtime.

The presence of `NVIDIA Environment` in the repository layout signals that NVIDIA runtime files are part of the project’s operating context. The available documentation does not explain their exact contents or the replacement procedure. The MIT license covers the repository. Users should inspect its license files rather than assuming that MIT applies to every file or binary. No legal interpretation of those terms is needed to reach that boundary.

Maintenance signals and upgrade trade-offs

The repository is not archived, and its last push was on 2026-07-19. Recent releases include v0.9.4 on 2026-07-19, v0.9.3 on 2026-06-18, and v0.9.2 on 2026-05-17. These dates show recent project changes, while the README also describes a six-hour monitor for new OptiScaler releases. The repository does not separately state which upstream OptiScaler or XeSS version is present in each published installer.

That distinction affects upgrade cost. End users can take a prebuilt package, but the package may track upstream changes without documenting every intermediate change in the DLSS-Enabler release notes. Advanced users can select a named OptiScaler version or retain an existing XeSS library through `update-optiscaler.ps1`, which offers more control at the cost of managing component compatibility.

The documented alternative approach is to rely on the game’s normal DLSS support on compatible NVIDIA hardware. That avoids replacing runtime libraries, but it excludes the AMD and Intel use case targeted by DLSS-Enabler. Another alternative is a game-specific OptiScaler installation, if its upstream documentation supports the title. The available DLSS-Enabler documentation does not describe that procedure, so the concrete difference here is limited: DLSS-Enabler packages a renamed `nvngx.dll`, adds XeSS, monitors upstream releases, and produces a standard installer.

Editorial conclusion

Users should adopt DLSS-Enabler when they have a DirectX 12 GPU, a game that natively supports DLSS2 and DLSS3, and a documented reason to replace its NVIDIA runtime dependencies. Users who need per-game troubleshooting, confirmed hardware compatibility, or a documented uninstall and rollback path should pause until they can verify those details with the maintainer. The first checks should be the game-specific DLSS menu, the selected upscaler and frame-generation mode, and whether the release matches the game runtime currently installed.

Frequently asked questions

Official sources

1. artur-graniszewski/DLSS-Enabler on GitHub
2. Issues
3. License: MIT
4. README
5. Releases