Quote from: lebuawu2 on June 06, 2018, 10:49:55 PM

Quote from: henri2018 on June 06, 2018, 08:41:07 PM

Quote from: lebuawu2 on June 06, 2018, 02:53:31 PM

Quote from: doktor83 on June 06, 2018, 02:06:39 PM

Quote from: lebuawu2 on June 06, 2018, 02:01:57 PM

Quote from: doktor83 on June 06, 2018, 12:16:15 PM

V1.5.9

- Added "max_difficulty" parameter in pools, if reached miner will reconnect to pool
- Better logging on miner crash
- Kernels are now built in Cache directory
- Probably fixed situation when miner crashes on pool switch
- Fixed .srb file creation on every miner run
- Hopefully reduced nicehash duplicate share errors
- Changed the way devfee pools are used

+ Now you can define a "max_difficulty" for every pool you have in pools config. Sometimes it happens that pool sends abnormally high difficulty, and miner can't find a share for a long time. In this case, by setting "max_difficulty", when ever pool difficulty is higher than the value you set, miner disconnects and reconnects to the pool.

+ There is now a Cache directory where the miner creates cached versions of OpenCL kernels

+ Some reported miner crash after multiple pool disconnect/reconnects , not able to log in etc.. I hope i found the cause of it and fixed it

+ Learned from the previous big mistake with devfee pools hardcoded in the miner, now miner gets the list of devfee pools from http://srbminer.com, so please allow/don't block it on your firewall

wow many thanks dok, will try now mining on nicehash with max_difficulty.

ok, and report is it working like it should

You can define max_difficulty for every pool like :

{"pool" : "lotsofcoinspool1", "wallet" : "", "password" : "x", "max_difficulty" : 150000},
{"pool" : "lotsofcoinspool2", "wallet" : "", "password" : "x", "max_difficulty" : 400000}

yes I already define max_difficulty, will monitoring for a while.
just to let you know I can confirm hash rate drop after reconnecting to pool for RX Vega.

SRBMiner 1.5.9 AMD Driver 18.5.2.

First running.
https://imgur.com/a/pVgDVlp

After reconnect because of network error.
https://imgur.com/a/g4GC6xz

Edit :
Reconnecting due to high diff work perfectly.
https://imgur.com/a/8icbdsL

Bro, in my case, after reconnecting, the hashrate was drop. But after waiting a few minutes, it's back normal.
May be you were too quick to observe?

I checked now, after more than 7 hours my hash rate still drop from initial running.

This happened to me as well(vega miner got disconnected from pool 1-2 minutes) 5 mins hashrate watchdog got triggered , then continue mining for less 20h/s ave. 2nd trigger continue mining again less 30 h/s ave. I have logs: https://mega.nz/#!OaYRVJTI!Z5dsgQTfMxlVrn9fNdqdNvG36eIAx4smfpagUxMiM2U
I'll try your trick UnclWish. Tnx!