[Feature request] NIS and rBAR

[Ghokury]

I have 2 feature ideas for NVCleaninstall.

The first one is enabling old NVIDIA Control Panel Sharpening instead of NIS which can be done using this registry file. Reboot isn't required.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\FTS]
"EnableGR535"=dword:00000000

Another one is enabling rBAR globally with drop down menu to choose rBAR size. It can be done via Profile Inspector, but I lack knowledge of how to do it using registry editor.

0x0000000040000000 = 1gb (default value for most whitelisted games)
0x0000000060000000 = 1.5gb
0x0000000080000000 = 2gb
0x0000000100000000 = 4gb
0x0000000200000000 = 8gb
0x000000000C800000 = 200mb (Diablo 4 default value)
0x0000000012C00000 = 300mb (The Riftbreaker default value)
0x0000000280000000 = 10gb

 

[Ghokury]

The registry path was moved and now it's the following:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\Parameters\FTS]
"EnableGR535"=dword:00000000

 

[W1zzard]

Another one is enabling rBAR globally with drop down menu to choose rBAR size. It can be done via Profile Inspector, but I lack knowledge of how to do it using registry editor.

isn't this a per-game setting?

 

[Cowboystrekk]

isn't this a per-game setting?

You can set ot globally with profile inspector. Be aware that a few games like delta force gets bad performance, while others perform very well.

 

[W1zzard]

You can set ot globally with profile inspector. Be aware that a few games like delta force gets bad performance, while others perform very well.

hmm .. not sure if enabling it globally with nvcleanstall is a good idea, because people won't have a way to undo it?

 

[Cowboystrekk]

Yeah. Agree.

 

[chrcoluk]

If you enable integer scaling, then the old style sharpening is there in the Nvidia control panel, I am not sure if thats what the registry tweak does, so yeah just enable integer scaling.

 

[Ghokury]

isn't this a per-game setting?

It can be set globally like RTX HDR and improves or doesn't affect performance in most cases, other than in games like Warzone.

If you enable integer scaling, then the old style sharpening is there in the Nvidia control panel, I am not sure if thats what the registry tweak does, so yeah just enable integer scaling.

It allows you to use old sharpen mode in NVIDIA control panel with any types of scaling. Can be done with Profile Inspector with custom names per game as well.

 

[Solaris17]

hmm .. not sure if enabling it globally with nvcleanstall is a good idea, because people won't have a way to undo it?

yeah I would not make this a feature because of things like that.

 

[AsadAlrafidain]

I might be wrong, but the registry tweak to restore old sharpening method doesn't work anymore (at least not with new versions of the driver 566+)...I tried many times and it just wouldn't work....we need someone else to verify this.



edit: I didn't notice this, it seems the registry path has changed as stated by the op, and the tweak is working now.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\Parameters\FTS]
"EnableGR535"=dword:00000000

+1 to include this tweak in Nvcleanstall (it is globally agreed that the old sharpening is better).

 

[AsadAlrafidain]

just a follow up for the registry path of the old Nvidia sharpening tweak....I tried many times and reinstalled windows many times to be sure....it seems the following is the correct path:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\FTS]
"EnableGR535"=dword:00000000

which was written in the first post but then "incorretly" updated.

 

[Ghokury]

just a follow up for the registry path of the old Nvidia sharpening tweak....I tried many times and reinstalled windows many times to be sure....it seems the following is the correct path:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\FTS]
"EnableGR535"=dword:00000000

which was written in the first post but then "incorretly" updated.

I just updated to .47 from .42 and registry path I provided in the 2nd message worked for me.

 

[AsadAlrafidain]

I just updated to .47 from .42 and registry path I provided in the 2nd message worked for me.

I don't know man....I could swear that the path in the second message worked on my main system (572.16), but tried multiple times to make it work on a clean windows 11 install (and every time reinstalled windows just to be extra sure) with driver version (566.14) which is not that old, and the only path that worked is the one in the 1st message......

maybe combining both paths in one tweak is the best solution.

 

[Ghokury]

I don't know man....I could swear that the path in the second message worked on my main system (572.16), but tried multiple times to make it work on a clean windows 11 install (and every time reinstalled windows just to be extra sure) with driver version (566.14) which is not that old, and the only path that worked is the one in the 1st message......

maybe combining both paths in one tweak is the best solution.

The path was changed in 572.16.

 

[AsadAlrafidain]

The path was changed in 572.16.

I see......that explains it.

so as I said, we can combine both paths so that the tweak would work on any version:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\FTS]
"EnableGR535"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\Parameters\FTS]
"EnableGR535"=dword:00000000