https://www.dropbox.com/s/yqubn6t08tkhht4/Captura%20de%20pantalla%202019-07-07%20a%20las%2016.17.25.png?dl=0As they say there is a problem when saving data with coins.
Zel has passed to 125.4 I have created the coin by hand from coins and also cointomine has already added it, but in both cases the least manual and dynamic data, (difficulty, nethash, price, etc.) but when I mine and give save hash, right button "save hasrate" if you save the HASH in the miner. I go to the miner I see 125.4 and save the hash. But the problem that the coins in COINS do not keep the hash, with which the auto profit is impossible.
There is some failure when saving the hash in the ALGO. As you will see in my capture, I have 3 zel, the old 144.5 and the two d 125.4, custom and cointomine. I have tried both, and in both I have saved the HASH, as I say in the miner I enter Equihash 125.4 and if the hash appears, but not in the coin as seen in the capture.
Please fix the problem.
Isn't it possible to cleanup the number of ZEL coins a bit to avoid any issues? Right now you probably have more than one coin with the same name and same algorithm, one (or two?) you have defined yourself and I suppose the other are from source like CoinToMine and similar. For a given pool based on ZEL, it will be quite difficult for Awesome Miner to figure out which coin to use. Awesome Miner doesn't have a way of automatically resolving these coin algorithm changes.
If you go to the Options dialog, Statistics Provider section, and use the Override algorithm feature to force the correct algorithm - and remove your user defined coin - isn't that giving you a single ZEL coin entry and it's starting to work better?
https://www.dropbox.com/s/widgqqmljfd5fhw/Captura%20de%20pantalla%202019-07-08%20a%20las%2015.48.41.png?dl=0I do not understand you completely Patrike.
Let's see, I AL-GO is only once in the list of algorithms, I did not add it, it was already 125.4 so it is not duplicated or tripled.
What I do have are 3 ZEL coins, old Zel 144.5, the manual added by me in 125.4 and the one that Cointomine added afterwards through its api.
It does not matter if you have 3 or 4 equal coins, if you are mining at 125.4 and I give save hashrate, do not record it, and I repeat as al-go there is only 1 that you added. I have no way to save the ZEL Hash
For me it is not a trauma, because ZEL with the new al-go that gives less hashrate and after measuring it 0.6 of profit, is a NOT PROFITABLE coin. But even so, I'm worried that the program will be full of small failures.
What do I have to do to erase the coins and leave only one ?, I have coins up to 4 times equal with 4 different wallets and I have not had any problems with them. As AL-GO, it is only once. so I do not understand the problem of not being able to save the Hashrate.
It does not make sense, no matter how many copies you have of the currency, you should keep your hashrate. I have already deleted all but one, the one that gives cointomine but with all the custom fields dynamically to have fresh data and not those of CTM that are late and now DO NOT WANT TO MIN.
It is the usual error, especially happens with Gminer in the machines, it remains as it is in the capture that I have put. Service offline, it stays what you see in the console, until it reboot the RIG. It is a problem that is making me very tired. Basically, it only happens with Gminer. has done reboot twice and the third has worked and is undermining. This is where we look more calmly because we still have problems
Now with only 1 ZEL if he has been able to save the HASH, but I see it as illogical. We continue with the problem of offline miner with Gminer, I'm pretty fed up.