Quote from: DanGB on June 27, 2020, 02:03:11 PM

Quote from: Zminer777 on June 27, 2020, 09:49:58 AM

+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)

I just tested the newest gminer update. I pointed it to a test pool that is already past block 777777 (so on BeamHashIII) and got 18-19 Sol/s with my 1070ti's (using the same Afterburner settings as with BeamHashII). Now the interesting thing is that I then pointed it to my node (so still BeamHashII) to solo mine and I was getting 18-19 Sol/s on there too. I then ran against my node the previous gminer version that I had been running and it got 40+ Sol/s as I expected (again, no changes in Afterburner settings). Any idea why I am seeing very low hashrate while mining BeamHashII with this latest version?

We figured out what the issue is. If you test BeamHashIII on a test pool and it is past block 777777, gminer creates a 0k file in the miner folder. With this file there, gminer will continue to run on BeamHashIII even if you go back to a regular mainnet pool that has not yet hit block 777777. To get your hashrate back and to have it actually mine on BeamHashII again, you must delete that 0k file.