Quote from: TrailingStop on May 24, 2019, 07:32:32 AM

Quote from: dkmontague on May 24, 2019, 07:26:26 AM

Quote from: TrailingStop on May 24, 2019, 04:36:04 AM

Quote from: dkmontague on May 24, 2019, 03:25:14 AM

It looks like the 2.2.4 fixes the issues from 2.2.3 so I was able to upgrade from 2.2.2 - great work man! 2 Questions: what is the default intensity? And can you explain how the hash report to the pool works with -rate? What does that effectively do? Does that affect how much the rate attribution to the miner is?

Thanks
Dan

Hi,

happy to hear if things work

The default intensity is calculated and differs from card to card. You should see at start something like this:
06:26:58 Miner: GPU[0] use default intensity 12, Gridsize: 275
06:26:58 Miner: GPU[0] uses Gridsize: 275 and Blocksize: 448
so you get all information. The calculation is made after the algo is send to the gpu. For newer ProgPoW algos you can see this information whenever the algo changes. After 50 blocks.

-rate send the miner hashrate to the pool so that it can compare the hashrate from miner & from pool side. You can see this on ethermine.org - they support -rate!

Let me know if you have more questions - happy to help.

I thought it was fixed but unfortunately it looks like it still suffers from the same issues as 2.2.3 with slower speed and higher rejected shares Sad

2.2.0 is still the best for me. . I dont think I am the only one either, as zergpool shows most miners as using version 2.2.0. You must have changed something going forward from there man ....do you know what is causing this? If you went back to however it was structured back in 2.2.0 and then added your other fixes/features you'd probably get a lot more people using the miner (more dev fee for you)

I guess you are on MTP and zergpool?

Nah I just look at zergpool to see what everyone is using. I just mine XZC MTP at mintpond