V1.6.1
- Changed IPBC/Bittube old algo to new BitTubeV2 algo (from block 110000)
- Max difficulty reconnecting mechanism is now triggering instantly
- Added 'worksize' option in config.txt, that is applied to every GPU (only if not set in gpu_conf)
- Hopefuly fixed a bug with job timeout reconnecting
- Hashrate watchdog now triggers even when user not connected to pool
+ BitTube (former IPBC) forks on block 110.000, and their new algo will be BitTube V2.
You can use the new algo only after they forked, use "cryptonight_type" : "bittubev2". The old IPBC algo has been removed, so until the fork please use the previous version of SRBMiner.
+ Added 'worksize' option in config.txt (use it on top of config.txt , where intensity and double_threads is). If set, it will be applied to every GPU that is found. Of course if you have a gpu_conf set, those settings will be used, insted of this global setting.
+ Some had app crash on job_timeout triggering, i hope i managed to fix it
+ Hashrate watchdog was set to trigger only if user is connected to the pool. Now this is changed, watchdog will monitor GPU'S all the time.
- Changed IPBC/Bittube old algo to new BitTubeV2 algo (from block 110000)
- Max difficulty reconnecting mechanism is now triggering instantly
- Added 'worksize' option in config.txt, that is applied to every GPU (only if not set in gpu_conf)
- Hopefuly fixed a bug with job timeout reconnecting
- Hashrate watchdog now triggers even when user not connected to pool
+ BitTube (former IPBC) forks on block 110.000, and their new algo will be BitTube V2.
You can use the new algo only after they forked, use "cryptonight_type" : "bittubev2". The old IPBC algo has been removed, so until the fork please use the previous version of SRBMiner.
+ Added 'worksize' option in config.txt (use it on top of config.txt , where intensity and double_threads is). If set, it will be applied to every GPU that is found. Of course if you have a gpu_conf set, those settings will be used, insted of this global setting.
+ Some had app crash on job_timeout triggering, i hope i managed to fix it
+ Hashrate watchdog was set to trigger only if user is connected to the pool. Now this is changed, watchdog will monitor GPU'S all the time.
Doktor can you improve one problem that happen if miner crashes and when windows restart if for an reason one gpu is not recognized and if we have set in gpu_conf: (9 gpus, but when restaring only recognizes
The miner wont start, and gives us an error. With that if happen in night when restart at least we hash with 8 gpus.
And when wake up we solve the problem. (restart again hehe)"gpu_conf" :
[
{ "id" : 0, "intensity" : 61, "worksize" : 8, "threads" : 2}, // Máximo que dá é 63 de intensity no heavy!! a partir de 62 perde performance!!
{ "id" : 1, "intensity" : 56, "worksize" : 8, "threads" : 2}, // Maximo vega 56 é 57
{ "id" : 2, "intensity" : 61, "worksize" : 8, "threads" : 2},
{ "id" : 3, "intensity" : 61, "worksize" : 8, "threads" : 2},
{ "id" : 4, "intensity" : 61, "worksize" : 8, "threads" : 2},
{ "id" : 5, "intensity" : 61, "worksize" : 8, "threads" : 2},
{ "id" : 6, "intensity" : 61, "worksize" : 8, "threads" : 2},
{ "id" : 7, "intensity" : 61, "worksize" : 8, "threads" : 2},
{ "id" : 8, "intensity" : 61, "worksize" : 8, "threads" : 2},
]
Regards
