2.2.2b1 had the highest potential, up to 3Mh/s with a 1070; all other versions do not even go above 2.2 so I think 2.2.2b1 had either a magic solver or was reporting hashrate wrong
was up from 16H/W efficiency to 25 I think there was an error in that one or if not, it was a genius build
Hi,
I guess you use an very high grid size? In that case the hashrate could be wrong if a kernel need more than 5 seconds to execute. Please use ALWAYS the reported hashrate of the pool as reference! But I think 2.2 MH/s for a 1070 on MTP isn't too bad?
I will release a new version soon that comes with more tolerance to higher grid sizes.
Anyway thanks for your report.