it fails to detect secondary algo sometimes
@tutulfo, perhaps when you search for max value, the eth max value was paired with 0 secondary and then it fails to update it as pair?
No, this is the code for update stats, if miner needs bechmarks (it is same var used to show "benchmarkin" msg) and actual readed value is greater than stored value stats are updated
$Value=[long]($Miner_HashRates[0] * 0.95)
if ($Value -gt $_.Hashrate -and $_.NeedBenchmark) {
$ValueDual=[long]($Miner_HashRates[1] * 0.95)
$_.Hashrate= $Value
$_.HashrateDual= $ValueDual
Set-Hashrates -algorithm $_.Algorithms -minername $_.Name -value $Value -valueDual $ValueDual
}
While benchmarking must appear speed on active miners section and must appear a file on stats folder with this value on it.
If you have a situation where dual mining numbers you have detected are "30, 0" because ETH was initialized first and these values are stored in file.
After that, when dual mining actually kicks in, the values are "25, 100", for example
so, 25 is never higher than 30, and never overwrites the values in the benchmark.txt which causes the benchmark to run forever
Show Posts
