Quote from: flipflop.0 on February 06, 2018, 07:19:14 PM

Quote from: tutulfo on February 05, 2018, 10:16:42 AM

Quote from: celofan on February 04, 2018, 03:02:01 PM

Very unstable release for me.
1. ccminer alexis not working, but in release 5.2 alexis worrking stable.Copy ccminer alexis from 5.2 to 6.0b1 solve this problem.
2. Restarts intervals.I.e. miner starts and interval is 600sec. When 60-70-80-90sec ends, miner can restart with new interval count value.
3. Never ends benchmark (after closing MM and starts it again some miners can start benchmark again).
4. Excavator can't mine neoscrypt algo (when added in json file)."Cuda ERROR - Not enough of memory" message shown, but the same release of excavator separately works for me.
And how i can disable miningpoolhub for excavator only? It works for nicehash perfectly.
5. Can you add palgin hsr miner in next release? https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows , https://github.com/palginpav/hsrminer/tree/master/HSR%20algo/Windows
Excavator and palgin hsr miners are the best neoscrypt miners for Nvidia pascal based cards (compared with Klaust - about 10% difference).
Thank you!

Try master branch code from github, some problems are solved.

1. I think no changes for alexis, did you copy miner file or bin content?
2. I will set lower watchdog sensibility
3. I´m testing this now
4. Compare json entrance file pls to see differences.
5. It is in Additional miners, read changelog before, this miner is a little....

Hey tutulfo, first, thanks for the great miner and your developing.

I am having the same issues as celofan in 2. and 3., a new interval just starts too early. i have set benchmark and mining interval both to 600 in the config, but the new interval always starts after 1-3 minutes.

i did not have the issue in previous releases, so my guess is that a new or changed parameter is overriding the interval time from the config time.

another observation is that currently i am mining on 2 pools. one api is not responding, pool issue. but since the api is not responding, MM restarts the interval every few seconds. almost like an instant override of the interval time from the config