emoose
emoose
Updated ConfigTool to let you change these NV profile settings, requires tool to be ran as admin in order to change them, but the current values can be viewed without...
ConfigTool 0.200.7.5: [DLSSTweaksConfig_0.200.7.5.zip](https://github.com/emoose/DLSSTweaks/files/12617248/DLSSTweaksConfig_0.200.7.5.zip) ConfigTool can now work without requiring the DLSSTweaks DLL/INI itself, allowing you to configure the DLSS profile settings, when there's no dlsstweaks.ini file to configure in the...
VSR isn't handled with the normal NvProfile stuff sadly, seems to be kept with some other VideoState settings instead, not sure if ProfileInspector includes anything for those atm. Did add...
Hm maybe will have to take another look at it, it was a couple driver versions ago that I tried measuring level 5, maybe newer drivers have changed it now....
ConfigTool 0.200.7.6: [DLSSTweaksConfig_0.200.7.6.zip](https://github.com/emoose/DLSSTweaks/files/12653909/DLSSTweaksConfig_0.200.7.6.zip) This allows changing the NvProfile globals via command-line args, eg you can run the program like the following (or create a shortcut to run this): `DLSSTweaksConfig.exe -GlobalForceDLAA...
`-VSR 5` would change the `VSRQuality #0` setting shown at https://github.com/emoose/DLSSTweaks/issues/85#issuecomment-1720870346 to level 5, VSR is just a shorthand for it, you can use `-VSRQuality` instead if you want to...
Yep noticed it earlier too, seems there's 2 different versions of 3.1.30 around, github is the older one while a slightly newer one was included in the NV dev SDK:...
Did you try the nonwatermarked version of dlssg.dll 3.5? https://pixeldrain.com/u/XkbtyC4B (check nvidia signature in file properties) 0.200.7 should have been able to remove it even in the watermarked version really,...
That was from the UE5 plugin on NV's developer site (https://developer.nvidia.com/rtx/dlss/get-started), seems that's the only place they post it, some reason github always has the watermarked version. Did send the...
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...