AFAIK: PROTON_ENABLE_NGX_UPDATER=1 doesn’t update the dlss version/dll files, just some game-specific profile settings. You’d still need to replace the .dll files if you want newer/different dlss files.
it gets weird when there’s multiple software layers. each one has their own env’s, dxvk, proton, nvidia, and then there’s the few random 3rd party ones (eg. libmimalloc if you want to tinker with memory allocation options)
AFAIK: PROTON_ENABLE_NGX_UPDATER=1 doesn’t update the dlss version/dll files, just some game-specific profile settings. You’d still need to replace the .dll files if you want newer/different dlss files.
https://github.com/jp7677/dxvk-nvapi/wiki/Passing-driver-settings#ngx-snippet-updates-and-preset-overrides - at least the documentation here only talks about some snippets that envvar allows updating
Ah, I didn’t RTFM completely. I just read a snippet that mentioned the NGX updater and misunderstood the context.
I’ll give it a shot, thanks.
tbh, I did the exact same thing, but came across that documentation today and realized my error… :P
hope it works!
So many envs and no central documentation makes it hard to handle for everyone.
it gets weird when there’s multiple software layers. each one has their own env’s, dxvk, proton, nvidia, and then there’s the few random 3rd party ones (eg. libmimalloc if you want to tinker with memory allocation options)
it gets messy.