NVIDIA Profile Inspector 2.3.0.13

UPDATE January 19th 2021

New Nvidia Profile Inspector version 2.3.0.13 is available.

Link: https://github.com/Orbmu2k/nvidiaProfileInspector/releases/tag/2.3.0.13

Changes:

• Updated driver settings to R460, removed deprecated settings from CSN.

Notes:

• 2.3.0.13 is labeled as a Pre-release version.
• Latest release version is still 2.3.0.10: https://github.com/Orbmu2k/nvidiaProfileInspector/releases/tag/2.3.0.10

 

AF HQ fix is gone.

 

It's called Texture filtering - Quality substitution now due to the updated settings constants to R418.

 

Yeap. Just noticed.

https://********/n8fz6Dh/image.png

 

All this setting does is work around a Engine side issue where HQ texture filtering causes artifacts by forcing the setting back to Quality.

 

There's a newer version available below in case someone is only reading this sticky:

https://forums.guru3d.com/threads/nvidia-profile-inspector-2-3-0-2.425906/

 

what is wrong with these new versions, the frame limiter just dosent work, neither v1 or v2. still using 2.1.3.3 and this one works as it should with no tearing

 

for me working flawleslly

 

then i dont know why its not working, all of them dont work since he added a separete category for frame limit mode, it does limit the frames but there is tearing in every mode

 

tearing will happen, use normal vsync or fast sync on top of fps limiter.



btw

all works fine here and resizing window is fixed too, so :thumbsup:

 

why would i use normal vsync on top? that just adds latency. i use 2.1.3.3 and i dont have a single tear with either v1 or v2 if set properly, same settings with newer profile inspector is tearing all over the place

 

Any fps limiter has nothing to do with tearing.

 

i know but for some reason i dont have any with the older versions

you should test yourself with the old version and see if you have any tearing, most games prefere +1 or +2 fps above refreash rate with v1, other games like battlefield v2

 

FYI, in Nvidia Profile Inspector, the new Low Latency Mode flag introduced in the latest Nvidia drivers is 0x0005F543 in the Unknown section. Settings are 0 = off, 1 = On, 2 = Ultra. In addition, setting this flag to 1 and 2 appear to require setting Maximum pre-rendered frames to 1.

 

^ Indeed and I ran nvidiaProfileInspector.exe -createCSN and added the following to the resulting file, putting "Low Latency Mode (NVCP)" right above Max pre-rendered frames in the Sync and Refresh section.

Update: I think it's the "FRL Low Latency" setting that actually engages ultra low latency mode. The setting with the hex ID 0x0005F543 may just hold the state of the NVidia Control Panel (NVCP) setting.

Code:

<CustomSetting>
      <UserfriendlyName>Low Latency Mode (NVCP)</UserfriendlyName>
      <HexSettingID>0x0005F543</HexSettingID>
     <GroupName>2 - Sync and Refresh</GroupName>
      <SettingValues>
        <CustomSettingValue>
          <UserfriendlyName>Off</UserfriendlyName>
          <HexValue>0x00000000</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>On</UserfriendlyName>
          <HexValue>0x00000001</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>Ultra</UserfriendlyName>
          <HexValue>0x00000002</HexValue>
        </CustomSettingValue>
      </SettingValues>
      <SettingMasks />
</CustomSetting>

Thanks for this topic, I wasn't aware newer versions existed.

 

Does Inspector let you set low latency off with Max pre-render frames =2 then?
working 2 value.

 

2 frames works for me, and the hex ID setting didn't seem to matter, as the latency was higher than 1 frame.

 

Today I ran some experiments and came to the conclusion that the new hex ID setting 0x0005F543 is not what actually engages ultra low latency mode. It's the "FRL Low Latency" setting when set to 1, as well as "Maximum pre-rendered frames" set to 1 at the same time.

"FRL Low Latency" set to 0 enables the use of "Maximum pre-rendered frames" as we had always used it in the past. We can force 1, 2, 3, 4 or whatever.

I updated my previous posts to reflect this information. Sorry for the double post, but I couldn't figure out how to delete my posts and thought this information could warrant a bump.

 

I don't think I overlooked this but who knows...is there not a way to enable DSR through the profile inspector?

 

No there is not. You have to use NVCP or DSRTool