Nvidia Profile Inspector lacks profiles and the frame rate limiter is not functioning (Error NVAPI_SETTING_NOT_FOUND)
Nvidia Profile Inspector lacks profiles and the frame rate limiter is not functioning (Error NVAPI_SETTING_NOT_FOUND)
DRS_SetSetting failed: NVAPI_SETTING_NOT_FOUND
Details on using JIT debugging are provided at the end of this message.
Exception details:
nspector.Common.NvapiException: DRS_SetSetting failed: NVAPI_SETTING_NOT_FOUND
For more information, refer to the instructions for starting just-in-time (JIT) debugging instead.
I understand, I previously used V2 Limiter too, but now NCP includes a frame by frame limiter. Also, as mentioned before, you're not using the newest version of NPI. I recommend version 2.30.13, which I shared a link to earlier. A thorough guide on NPI explains that the limitation with whole numbers isn't due to performance issues, and it notes that RTSS actually performs better. If NCP's limiter doesn't suit you well, consider trying RTSS instead—it uses less RAM than any other limiter.
I previously relied on Nvidia Profile Inspector, but since most of the adjustments I made were handled through the Nvidia Control Panel, I switched to that instead. The issue you're facing is likely related to the absence of thorough testing or maintenance on an open-source tool (NPI) compared to Nvidia's internal driver team, which regularly tests and maintains their proprietary solution. Also worth noting, DRS refers to driver configurations, indicating that if this isn't functioning correctly, the NPI developers should address it.
I understand, I previously used V2 Limiter too, but NCP now includes a frame by frame limiter. Also, as mentioned before, you're not using the newest version of NPI. I recommend version 2.30.13, which I shared in the comments above.
A thorough guide on NPI explains that the limitation to whole numbers was due to performance issues with them. It also notes that the RTSS limiter performs better, so if you're having trouble with NCP's limiter, consider trying RTSS instead. RTSS uses less RAM compared to other options.
You can find more details here: https://forums.guru3d.com/threads/nvidia...de.403676/
I've personally used the RTSS limiter and it functions well. Also, RTSS comes with Rivatuner and MSI Afterburner. It can run independently, though you might see a warning about some components not being connected at once. Just ignore that message and it should work fine by itself. Often launching it separately is better, since some games don't work properly with Afterburner or Rivatuner.
For a 144hz monitor, locking to 143.5hz with RTSS might help improve stability. You're experiencing good results, so it could be worth trying.