Quote from: ypsi on February 26, 2018, 05:15:44 PM

Quote from: cain2941ll on February 26, 2018, 04:25:02 PM

Man...I would love to get away from MSI Afterburner. I have nothing but issues as well on any rig that has multiple GPUs. Great idea Storx

Yeah, I moved away from AB and PrecisionX a long time ago in favor of Nvidia Inspector. The question is whether it will be updated for Ampere (or whatever the next gen cards will be called) since it seems it's not actively developed anymore.

--ypsi

I dont think it will cause an issue in the future, from my understandings is that it communicates with the GPU drivers directly to apply the changes vs afterburner communicating through the pcie bus with the GPU directly....

MSI AB when open has active connection with every sensor being communicated on the GPU, even all the ones we have no need to monitor, resulting in excess cpu power on the GPU, when i was using MSI AB i was forced to reduce my OC settings on the GPU's that kept hanging up on me, or the OC profiles would become unusable on AM tell i restarted the rig... with Nvidia Inspector, it only communicates for a split second to the driver, which then communicates a change to the GPU from the readings ive done, so its performing the OC settings at a more basic level of operation, communicates for a micro second a few commands, then closes the communication and your off to the races...

Example: my average rig running AM mining Skein on 1080ti's, the highest i could go on OC setting on core was +165 before stability issues occured, now with Nvidia Inspector all my 1080ti's are clearing +200 on core for Skein without reliability issues, i do have a few random ones that only run up to +180, but that is mostly due to built in already overclocked settings and weaker card in general issues...

--ypsi

If you want to use Nvidia Inspector now with AM you can, i have been using it in a jerry-rigged way, but i have not figured out how to use it with profit switching, so i have been forced to keep an eye on the coins i mine to assure im mining one of the more profitable ones due to the limitations, since getting rid of the OC profiles, my rigs have been way more reliable..

The way im currently doing it is i installed all 3 files of Nvidia Inspector files in AM folder or folder of your choice, then under managed template profiles, on the left command lines there is a section for batch file commands, i select the execute before starting the mining option and add command pointing the commands to the location of the Nvidia Inspector file....the key was linking the command line code to the file so it can execute it on the remote rigs, you have to change the "C:\CRYPTO\SOFTWARE\nvidiaInspector\nvidiaInspector.exe %GPU0% %GPU1% %GPU2% %GPU3%" line to the location of the file on the remote rig.

ex:

Code:

SET GPU0=-setBaseClockOffset:0,0,100 -setMemoryClockOffset:0,0,400 -setPowerTarget:0,70 -setTempTarget:0,0,70 -forcepstate:0,0
SET GPU1=-setBaseClockOffset:1,0,100 -setMemoryClockOffset:1,0,400 -setPowerTarget:1,70 -setTempTarget:1,0,70 -forcepstate:1,0
SET GPU2=-setBaseClockOffset:2,0,100 -setMemoryClockOffset:2,0,400 -setPowerTarget:2,70 -setTempTarget:2,0,70 -forcepstate:2,0
SET GPU3=-setBaseClockOffset:3,0,100 -setMemoryClockOffset:3,0,400 -setPowerTarget:3,70 -setTempTarget:3,0,70 -forcepstate:3,0
C:\CRYPTO\SOFTWARE\nvidiaInspector\nvidiaInspector.exe %GPU0% %GPU1% %GPU2% %GPU3%

A very easy way to implement Nvidia Inspector to AM so you can profit switch that i can think of is to add the tab Command Line under pools, with the same execute batch file option....
So when profit switch makes a switch to another algo using the pool profile, it can change the gpu settings based on that pool's algo basically, then all you do is link to the executable file on the rig and walla you have nvidia inspector OC