DLSS 5 implementation

[bruno_carnevalli]

Hello,

I think DLSS 5 is a game changer. I wonder if that is something Chaos team are considering implementing on Vantage.

[jmdvella]

You can check this thread here, Chaos mentioned they are working on it. Avalanche_1 has tested it with other methods.

Dlss5?

[32] [32_DLSS5_IMAGE_20260903-005051-550300-0001] Yes, I tried it out yesterday as an alternative. It actually performs quite well. It adds detail, reflections in areas where they were faint, and shadows. I especially like how it handles foliage (subsurface scattering). However, there are a couple of things about DLSS 5 that I don’t like specifically, the way it tones down the bloom and glare effects I intended. Here is a comparison between the original Vantage render and the render processed …

[Sadaf_Bijan]

Hi everyone,

I’ve been spending serious technical hours troubleshooting the leaked DLSS 5 (Neural Rendering) mod / RenoDX generic build inside Chaos Vantage v3.1 on an RTX 4090, and I’ve hit a wall that I’d appreciate some expert insight on.

Here is a summary of what’s already verified and configured on my end:

• Environment: Windows 11 with HAGS enabled, clean latest Game Ready driver, and AllowUnsignedDrivers=1 set in the NGXCore registry.

• ReShade & Add-on Hooks: ReShade 6.8.x is successfully hooked into vantage.exe (DirectX 12), and the RenoDX DLSSNR add-on (renodx-dlss5.addon64) loads with a clean reference match (E16BCF15...).

• The Conflict Handled: Disabled native DLSS Ray Reconstruction (Feature 13 / DLSSD) in Vantage preferences to prevent pipeline clashes, leaving native DLSS/DLAA active in the viewport.

The Core Issue: Despite having valid NGX hooks and a clean Streamline setup, whenever the add-on attempts to initialize Feature 18 (NVSDK_NGX_D3D12_CreateFeature), it immediately fails with the dreaded 0xbad00001 (Invalid Parameter) error.

Looking at the logs, the runtime initializes fine (nvngx_dlssnr.dll), but the hook fails at the feature creation stage. Given that Nvidia has been tightening restrictions around signed runtimes and feature locks on the RTX 40 series, is there something specific in the latest driver/NGX pipeline flags that is rejecting Feature 18 in non-game workstation apps like Vantage?

Any technical pointers or bypasses would be immensely appreciated. Logs and setup are clean—happy to share specific trace data if needed. Thanks!

[georgi.zhekov]

Hello,

Thanks for reaching out, and it’s great to see you exploring what’s next for Vantage!

Unfortunately, we can’t help with this one. DLSS 5 isn’t officially supported in Vantage yet, and the DLL you’re using comes from an unofficial source. Because of that, we’re not able to troubleshoot it or advise on getting it working.

When official support arrives, we’ll announce it in the release notes and on our forum, so keep an eye out there. In the meantime, if you run into anything with the supported setup, we’re always happy to help.