NVIDIA Profile Inspector 2.3.0.13

Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by Ital, Mar 16, 2019.

  1. BlindBison

    BlindBison Master Guru

    Messages:
    766
    Likes Received:
    156
    GPU:
    RTX 2080 Super
    Thanks for your work, Nvidia Inspector is such an awesome tool -- it boggles my mind that enabling "Half-Refresh V-Sync" via the driver can't be done in the standard control panel without it also being the "adaptive" type -- don't get me wrong, on paper I like Adaptive v-sync as much as the next guy, but the issue is the adaptive v-sync type doesn't work in conjunction with the low lag v-sync trick in my tests/you get tearing constantly and have to cap to something closer to refresh rate/2 + 1 to avoid tearing.

    Nvidia Inspector --> Half-Refresh V-Sync + something like an RTSS cap to the monitor refresh/2 - 0.01 (and maybe the ULLM mode -- not sure if it has any effect when reaching your fps limit though) has produced pretty solid results with a controller all things considered (I say with a controller since input isn't 1:1 like a mouse and I don't notice the latency quite as much personally). Anyway, all that to say I just wish Nvidia would add standard half-refresh rate v-sync to their panel.

    RTSS scanline sync is also terrific, but on some of my older systems (my laptop for example), I don't have the overhead to consistently prevent tearing that way as the tear moves around quite a bit and all, but an awesome tool there nontheless. Had great results with it in DOOM 2016 to my recollection.
     
  2. Y0!

    Y0! Active Member

    Messages:
    50
    Likes Received:
    1
    GPU:
    Intel HD
    Hello, thank you for your work.

    First I'd like to inform you that "NVIDIA predefined profiles CAN be restored". When you remove a profile, it writes to one of the two files: nvdrsdb0.bin or nvdrsdb1.bin (looks like half of the profiles are linked to the first file and another half - to the second one). Those files can be found in the \ProgramData\NVIDIA Corporation\Drs folder. But those predefined profiles are not stored in those two files and if you remove them - all predefined profiles will be restored. You might try it yourself.

    Second - there's a reason for me to try and remove all preinstalled nvidia profiles for all applications. The problem is that with your program I can only remove 1 profile at a time and after each time it jumps to the default profile so I need to press "Down" everytime, plus after I confirmed the remove it shows another window saying it's removed which I do not want to see. So please tell me how to remove several profiles at a time or even all of them without pressing all those redundant buttons?
     
  3. Astyanax

    Astyanax Ancient Guru

    Messages:
    11,009
    Likes Received:
    4,074
    GPU:
    GTX 1080ti
    Export nvidia format
    blank everything except base profile.
    import nvidia format.
     
    Cave Waverider likes this.
  4. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    7,821
    Likes Received:
    710
    GPU:
    Inno3D RTX 3090
    Is the v2 limiter still working? I'm getting this with the latest Inspector and the latest driver:
    Code:
    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.
    ************** Exception Text **************
    nspector.Common.NvapiException: DRS_SetSetting failed: NVAPI_SETTING_NOT_FOUND
       at nspector.Common.DrsSettingsServiceBase.StoreDwordValue(IntPtr hSession, IntPtr hProfile, UInt32 settingId, UInt32 dwordValue)
       at nspector.Common.DrsSettingsService.<>c__DisplayClass15_0.<StoreSettingsToProfile>b__0(IntPtr hSession)
       at nspector.Common.DrsSettingsServiceBase.<>c__DisplayClass5_0.<DrsSession>b__0(IntPtr hSession)
       at nspector.Common.DrsSessionScope.DrsSession[T](Func`2 action, Boolean forceNonGlobalSession, Boolean preventLoadSettings)
       at nspector.Common.DrsSettingsServiceBase.DrsSession(Action`1 action, Boolean forceNonGlobalSession, Boolean preventLoadSettings)
       at nspector.Common.DrsSettingsService.StoreSettingsToProfile(String profileName, List`1 settings)
       at nspector.frmDrvSettings.StoreChangesOfProfileToDriver()
       at nspector.frmDrvSettings.tsbApplyProfile_Click(Object sender, EventArgs e)
       at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
       at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
       at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
       at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
       at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ToolStrip.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
    ----------------------------------------
    nvidiaProfileInspector
        Assembly Version: 2.3.0.10
        Win32 Version: 2.3.0.10
        CodeBase: file:///C:/ProgramData/chocolatey/lib/nvidia-profile-inspector/tools/nvidiaProfileInspector.exe
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.8.4084.0 built by: NET48REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.8.4084.0 built by: NET48REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    Microsoft.GeneratedCode
        Assembly Version: 1.0.0.0
        Win32 Version: 4.8.4084.0 built by: NET48REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    Microsoft.GeneratedCode
        Assembly Version: 1.0.0.0
        Win32 Version: 4.8.4084.0 built by: NET48REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    
    
     

  5. dr_rus

    dr_rus Ancient Guru

    Messages:
    3,033
    Likes Received:
    397
    GPU:
    RTX 3080
    Latest Inspector is 2.3.0.13, you seem to be using 2.3.0.10
    There's only v3 limiter in the latest Inspector and - presumably - drivers.
     
    PrMinisterGR likes this.
  6. Rootax

    Rootax Member Guru

    Messages:
    157
    Likes Received:
    25
    GPU:
    3090 MSI Suprim X
    Is it possible to make some kind of "template", to enable/change values for all profiles at once ?
     
  7. MrBonk

    MrBonk Ancient Guru

    Messages:
    3,251
    Likes Received:
    200
    GPU:
    MSI RTX 2080
    You can export user modified profiles only. Open the file in Notepad++ and use the Replace all function. Then re-import
     
    Rootax likes this.
  8. adelheid

    adelheid New Member

    Messages:
    1
    Likes Received:
    0
    GPU:
    nvidia 1050ti 2gb
    First time posting here.

    Is frame rate limiter v3 cpu-level or gpu-level? (rivatuner limiter is said to be cpu-based)
    I also read from the previous pages that v3 is v1 with some tweaks

    TIA
     
  9. aufkrawall2

    aufkrawall2 Master Guru

    Messages:
    868
    Likes Received:
    142
    GPU:
    3060 TUF
    The render speed metering is always "CPU-based", I don't think there can be such a thing as a "GPU-based" limiter.
    Nothing's wrong with limiter v3. For VRR it's a no-brainer with NULL, thus the driver even sets it automatically. With D3D12/Vulkan, in-game limiters can have lower lag, but also can have noticable variance (not necessarily noticeable though, decide individually for each case).
     
  10. NiColaoS

    NiColaoS Master Guru

    Messages:
    654
    Likes Received:
    47
    GPU:
    GTX 1660 SUPER
    Anyone else noticed ANSEL cannot be disabled anymore? Previously I was just pressing "continue" at the error it was throwing, but currently doesn't work either. Created new profile, too, which wasn't throwing the error but still no avail. I'm talking specifically for War Thunder. Don't know about other games. FYI I'm using NVSlimmer with bare minimum plus the USB-C driver despite I don't have the appropriate slot. Inspector version 2.3.0.13 and drivers 471.41. The Inspector version by the other guy, 3.5.0 doesn't even mention ANSEL.

    PS Anyone knows an other solid way to disable the maΦaker?
     
    Last edited: Jul 23, 2021

  11. Astyanax

    Astyanax Ancient Guru

    Messages:
    11,009
    Likes Received:
    4,074
    GPU:
    GTX 1080ti
    can still be disabled.
     
  12. tsunami231

    tsunami231 Ancient Guru

    Messages:
    11,974
    Likes Received:
    893
    GPU:
    EVGA 1070Ti Black
    Is not Nvidia Low latency mode and and max perrender frames in inpsector the same? or are the separate now? I thought low latency mode "on" is 1 to prereneder max frames. so should 1 prerendered max frames be "on" in low latency mode in nvcp?

    I was just looking at NVCP and changing inspector pre rendered max frames does not change NVCP for low latency mode do they not do the same thing or are the diffrent?

    Edit
    I redowload and 2.3.0.13 and let override things most setting stand same but not the "maximum pre rendered frames" that all got reverted to defaults for everything and now changing Low Latency mode to on in NVCP flips "Maximum pre rendered frames" to default or 1 in inspector. before it did not such thing? so I assuming what ever issue i was have is now fixed cause tag low latency mode in NVCP did not change anything in inspector before and it does now?
     
    Last edited: Jul 27, 2021
  13. Krzyslaw

    Krzyslaw Master Guru

    Messages:
    229
    Likes Received:
    71
    GPU:
    RTX2080 SUPER
    Mayby inspector should be updated as per r470 nvapi as far as I know it uses r460 now. It would be nice to refresh it.
     
  14. tsunami231

    tsunami231 Ancient Guru

    Messages:
    11,974
    Likes Received:
    893
    GPU:
    EVGA 1070Ti Black
    might be nice then again i am still using 466.11 when did the 471 api even start? assuming march of 2021?
     

Share This Page