Hi Patricke,
I'm finally taking a moment to report a few bugs I've been running into over the past year with Awesome Miner. Please forgive me if anyone else has reported these issues.
1. For managed software like anything with sgminer compatibility, when I set the user defined command line argument to be like "mtp -I 20 -w 256" , you pass everything as the -a algo parameter to use which then causes the miner to fail because it can't find the "mtp -I20 -w256" algo. I instead have to set the -I 20 and -w 256 in the "additional command line arguments" in the algorithm specific settings in the profit profile section.
2. If I create a user defined online service and then later delete it, the deleted online service remains in the online services (dashboard/miners/coins/online services) page. I have to manually delete it from the configuration xml file to remove it from the list.
3. If I make changes to most settings like to the "execute additional commands before starting the mining software" to the miner properties and then restart my machine, the old settings are used one more time when first starting the miner. This applies to pretty much most settings in the software - like making changes to the "additional command line arguments" for the algo specific settings above. This is a problem when the current settings causes the pc to crash.
4. This is a systemwide issue - Awesome Miner tends to only mach pools/online services by their hostname/port, and not the full details. This leads to bugs/confusions. Examples:
a. for comining.co, you always mine to the same address/port but you use workers to set which coin you're mining. Once I have like 3-4 of these created for like eth/etc/egem/b2g/moac... , awesome miner will show the wrong coin being mined on the dashboard. See point c below for similar results. If I recall correctly, when I create enough of these pools for all the different ethhash coins, awesome miner gets too confused to mine at all from comining.co.
b. at miningdutch.com, I needed to mine to the lower difficulty port like for neoscrypt - 9991 instead of 9993 because the difficulty wasn't always being properly set. I couldn't change the port in the predefined services because awesome miner would reset it when I restarted the program I therefore created a user defined entry for mining dutch.com on port 9991. However, awesome miner only uses the profit calculations from the predefined neoscrypt service even when its disabled and the user defined is enabled. I still have to set the profit setting on the disabled one to the one I want to use.
c. The same issue happens if I try to mine a coin directly at a predefined online service port, like if I create a pools for a few neoscrypt coins (feathercoin, gobyte, iq cash, etc) set to zergpool's neoscrypt port. The dashboard will usually then show I'm mining the wrong coin with the wrong profit calculations.
5. If I set a coin to a particular exchange - like haven to tradeogre, it often forgets this and goes back to using all of the exchanges. This often screws up the mining profit calculations due to bad exchanges. Is there any way to keep the coins from not losing their exchange settings? The same goes for the coins I put in the hidden list. That list also gets wiped and they're back being visible on the coins page.
I can try and answer any questions or help repo any of these if you want. Thanks for all your work on this miner!
Hal
Thanks for taking your time to provide all this feedback.
1) I will correct this in the next release - it's related to how Awesome Miner generates the sgminer configuration file.
2) Is it not even cleared if you restart Awesome Miner once? I will have to investigate this scenario more.
3) I'm not able to reproduce this one. Is the case that you have quite a large number of Managed Miners? What if you wait for a little while between you make the configuration change and performing the restart operation - does that change the behavior in any way?
4) Right now it's mainly the pool URL incl. port that is used to identify a specific pool. I think this is what causes the confusion here where Awesome Miner cannot see the difference between some of the pools. I don't have a solution to this today as this have to be some future design changes to better handle the scenarios you describe
5) Sometimes coins are removed by the provider and later it's added again. Can you please go to the Options dialog, Statistics Provider section, and enable "Keep coins even when no longer listed by provider". This should force the coin to be kept together with all the exchange settings you made to it.
