NVidia in their ceaseless efforts to be insane and add fake security added encrypted keys to profiles.
In NvAPIWrapper, you simply return the raw values, which are thus invalid. An example test case I used was Arma 3. The setting for
Setting ID_0x708db8c5 = 0x5e398a4c InternalSettingFlag=V0
is returned raw, as 0x5e398a4c, an invalid convergence value. The actual value should be 0x3DA26384 which is a float for 0.7.
You can see in Nvidia Profile Inspector the correct value is displayed. But returns via NvAPIWrapper's API are corrupt.
NVidia in their ceaseless efforts to be insane and add fake security added encrypted keys to profiles.
In NvAPIWrapper, you simply return the raw values, which are thus invalid. An example test case I used was Arma 3. The setting for
Setting ID_0x708db8c5 = 0x5e398a4c InternalSettingFlag=V0is returned raw, as 0x5e398a4c, an invalid convergence value. The actual value should be 0x3DA26384 which is a float for 0.7.You can see in Nvidia Profile Inspector the correct value is displayed. But returns via NvAPIWrapper's API are corrupt.
See this Issue for details on the fix: https://github.com/Orbmu2k/nvidiaProfileInspector/issues/7
Any profile entry tagged with "InternalSettingFlag=V0" is an encrypted field.