Loading DLSS from single updatable location (no DLSSTweaks required)

[emoose]

Reposting from my comment on guru3d:

Looks like DLSS can load newer ver automatically if you create a 198400 folder inside C:\ProgramData\NVIDIA\NGX\models\dlss\versions, create a files folder inside there, then copy 3.7.0 nvngx_dlss.dll into it and rename to 160_E658703.bin.
(so you should have it at C:\ProgramData\NVIDIA\NGX\models\dlss\versions\198400\files\160_E658703.bin)

Finally open the C:\ProgramData\NVIDIA\NGX\models\nvngx_config.txt file in text editor and add these lines to the [dlss] section:

app_E658703 = 3.7.0
app_E658703_forced = 3.7.0

That seems to let HFW load in 3.7.0 instead of the 3.5.10 in game folder, I'm not sure if this only works for games that use the generic appID though, if the DLSS overlay shows a different id than E658703 you might need to change the filename and INI names.

(I think nvngx is also checking for this generic appID specifically even when game is providing appID though, so maybe it'll just work - might be a nicer way than needing to swap the files for every game manually)

E: seems to work for dlssg too, the config txt also mentions dlssd so probably works for RR as well, but I don't have any RR games installed atm to check with.

A powershell script/module to handle this for you can be found here: https://gist.github.com/emoose/11271bbb3b42fb3b1b0e1c83eef47c05
With that setup you can just write UpdateDLSS into powershell whenever a new DLSS version drops and point it to your downloaded nvngx_dlss.dll, and it'll handle copying/updating INI for you.

Maybe could be something worth including into ConfigTool eventually too, hmm...

(or if any other tools want to implement it feel free)

[Loganius]

Tried with Fortnite, used it's appID, but it didn't work. DLSS indicator was still showing it runs game's 2.2.6. I wonder if there could be a way to force every app to be recognized as generic.

[emoose]

Was that with copying/editing the files manually or did you use the PS script? The script was bugged till ~5 hours ago (probably wasn't a good idea to update it right before going to bed lol...), should be fixed now though.

From the code in nvngx it looks like copying it to E658703 should let it load even for non-generic-appid games, as long as the version for E658703 is newer than the one included with the game, haven't tried checking any non-generic games to verify that yet though.

[Loganius]

Manually.

Anyway, I tried it again with the generic appid. Tried Cyberpunk with 2.5.1 in game directory and it didn't work. It was running on 2.5.1 and DLAA was somehow broken by this. The textures weren't loading properly and DLSS indicator wasn't even showing. I guess it tried to connect with the file in NVIDIA folder, but it wasn't working properly,

Maybe it only works for later versions of DLSS, but obviously not with 2.x.x. A pitty.

[geahad]

This is phenomenal!

Now to only figure out how to do this for dlssg and dlssd and we're golden...

[emoose]

Seems to at least work for dlssg if you substitute dlss -> dlssg in the folder/INI names (the PS script should handle that for you too)
I'd guess dlssd will work as well since the INI this changes does mention it, but haven't got any dlssd games installed to test that with atm.

[xCaptainTroy]

Reposting from my comment on guru3d:

Looks like DLSS can load newer ver automatically if you create a 198400 folder inside C:\ProgramData\NVIDIA\NGX\models\dlss\versions, create a files folder inside there, then copy 3.7.0 nvngx_dlss.dll into it and rename to 160_E658703.bin.
(so you should have it at C:\ProgramData\NVIDIA\NGX\models\dlss\versions\198400\files\160_E658703.bin)
Finally open the C:\ProgramData\NVIDIA\NGX\models\nvngx_config.txt file in text editor and add these lines to the [dlss] section:
app_E658703 = 3.7.0
app_E658703_forced = 3.7.0
That seems to let HFW load in 3.7.0 instead of the 3.5.10 in game folder, I'm not sure if this only works for games that use the generic appID though, if the DLSS overlay shows a different id than E658703 you might need to change the filename and INI names.
(I think nvngx is also checking for this generic appID specifically even when game is providing appID though, so maybe it'll just work - might be a nicer way than needing to swap the files for every game manually)
E: seems to work for dlssg too, the config txt also mentions dlssd so probably works for RR as well, but I don't have any RR games installed atm to check with.

A powershell script/module to handle this for you can be found here: https://gist.github.com/emoose/11271bbb3b42fb3b1b0e1c83eef47c05 With that setup you can just write UpdateDLSS into powershell whenever a new DLSS version drops and point it to your downloaded nvngx_dlss.dll, and it'll handle copying/updating INI for you.

Maybe could be something worth including into ConfigTool eventually too, hmm...

(or if any other tools want to implement it feel free)

can I ask you something. what does number 198400 refer to?

[emoose]

That's the version number converted from hex to decimal

eg. DLSS 3.7.0 would be 0x030700 in hexadecimal, if you put that into a hex -> dec converter like https://www.rapidtables.com/convert/number/hex-to-decimal.html it'll give 198400

If a DLSS 3.8 releases then the hex would be 0x030800, so the decimal/folder name would be 198656

(something like 3.1.11 would be 0x03010B though, since 11 is B in hex)

The powershell script I posted should be able to find the version number and get the right decimal for you btw

[xCaptainTroy]

That's the version number converted from hex to decimal

eg. DLSS 3.7.0 would be 0x030700 in hexadecimal, if you put that into a hex -> dec converter like https://www.rapidtables.com/convert/number/hex-to-decimal.html it'll give 198400

If a DLSS 3.8 releases then the hex would be 0x030800, so the decimal/folder name would be 198656

(something like 3.1.11 would be 0x03010B though, since 11 is B in hex)

The powershell script I posted should be able to find the version number and get the right decimal for you btw

thanks for your replay <3

[Furzide]

Hey, I tested the powershell script and it appears that it doesn't work on fortnite. I know how to use dlsstweaks as i use it on minecraft, but I am obviously weary of doing it in fortnite as I don't want to end up with a ban. do you know of the safest way to use the latest version of dlss on fortnite?

[xCaptainTroy]

Furzide

not working with 2.x versions you need version 3.0++.
Im still trying figure out why this happening the log file show that the dlss snippet feature just ignore the bin file and load the game DLL file directly when the battle eye anti cheat used I manage to swap DLL file to any version I want, if I swap it for example to version 3.5 the method will work and it will be updated automatically to version 3.7 but any 2.0 version will not work, I think its because the build of 2.x version is different from 3.x version (3.x versions have a presets but 2.x not)

[Furzide]

Furzide

not working with 2.x versions you need version 3.0++. Im still trying figure out why this happening the log file show that the dlss snippet feature just ignore the bin file and load the game DLL file directly when the battle eye anti cheat used I manage to swap DLL file to any version I want, if I swap it for example to version 3.5 the method will work and it will be updated automatically to version 3.7 but any 2.0 version will not work, I think its because the build of 2.x version is different from 3.x version (3.x versions have a presets but 2.x not)

mate I know that dlss 3 is required that's what I'm trying to use on fortnite, the issue is that I don't know what sort of anticheat issues are gonna arise from replacing the dlss dll with 3.7.0, or how to prevent them from happening.

[xCaptainTroy]

Furzide

not working with 2.x versions you need version 3.0++. Im still trying figure out why this happening the log file show that the dlss snippet feature just ignore the bin file and load the game DLL file directly when the battle eye anti cheat used I manage to swap DLL file to any version I want, if I swap it for example to version 3.5 the method will work and it will be updated automatically to version 3.7 but any 2.0 version will not work, I think its because the build of 2.x version is different from 3.x version (3.x versions have a presets but 2.x not)

mate I know that dlss 3 is required that's what I'm trying to use on fortnite, the issue is that I don't know what sort of anticheat issues are gonna arise from replacing the dlss dll with 3.7.0, or how to prevent them from happening.

@Furzide you understand what I mean ? the problem isn't the anti-cheat, the problem is Fortnite have dlss version 2.2.6 and that not swappable

[Furzide]

Furzide

not working with 2.x versions you need version 3.0++. Im still trying figure out why this happening the log file show that the dlss snippet feature just ignore the bin file and load the game DLL file directly when the battle eye anti cheat used I manage to swap DLL file to any version I want, if I swap it for example to version 3.5 the method will work and it will be updated automatically to version 3.7 but any 2.0 version will not work, I think its because the build of 2.x version is different from 3.x version (3.x versions have a presets but 2.x not)

mate I know that dlss 3 is required that's what I'm trying to use on fortnite, the issue is that I don't know what sort of anticheat issues are gonna arise from replacing the dlss dll with 3.7.0, or how to prevent them from happening.

@Furzide you understand what I mean ? the problem isn't the anti-cheat, the problem is Fortnite have dlss version 2.2.6 and that not swappable

I've seen people swap the dlss dll in fortnite. The issue is that I can't seem to recreate it. proof is in this youtube video here:
https://youtu.be/ZRubyJJP16s?si=938d3CjIaa9di58s