Quote from: Zminer777 on August 29, 2019, 05:44:04 PM

Quote from: scryptr on August 29, 2019, 05:25:07 PM

The miner does not print to the console when an overclock "OC" kernel is in effect. Whatever improvement to the hash rate that results from the kernel seems minimal at best.

Miner print when selected OC kernel: "Selected OC1 solver"
When there is no OC1 kernel for card and algorithm then miner print "Selected Normal solver"

Quote from: abudfv2008 on August 29, 2019, 05:28:09 PM

How to set OC paremeter in config files? Maybe "sample-config" needs to be updated?

Will do it in next update, example:
oc=0 1 1 0 1 1

I am running v1.60. This is the syntax I tried but it will not work for me. I have a PNY xlr8 1070 card in a rig with 3 1070ti cards. I run two miner instances, one with "devices=0" to run the 1070 buy itself and the other with "devices=1 2 3" for the 1070ti cards. For my 1070 config file, I added OC=1, but it still uses the normal solver.

Additional question... I have another computer with two 1070 cards that I run in different miner instances because I am running one for me and one for my brother. So in one config file, I have devices=0 and the other config file I have devices=1. Does the "OC=" line reference the GPU in the devices= line or reference the GPU in the system? In other words, for the config file that has devices=1, would OC=1 reference the GPU in the devices line (GPU1) or would it reference GPU0 on the system?

Thanks