Quote from: xChackOx on July 23, 2017, 05:15:27 PM

Hello!

Thanks for the work with AM. I've been trying it for a couple of days and I'm impressed with it. I'm using it to emulate the NHM client because AM offers way more flexibility and more algorithms than the official NHM client.

Thanks for your feedback. I'm providing comments of some of the items below. In general I use this kind of feedback to prioritize the future development of Awesome Miner.

Quote from: xChackOx on July 23, 2017, 05:15:27 PM

From what I empirically understand, the hash rate of the Profit Profiles is the sum of the hash rates of all GPUs (or profiles if using group profiles). So, if I have 2 GTX1060 my effective hash rate is 40.6 MH/s (instead of the default 20.3 MH/s). I did some quick calculations comparing the NHM benchmarks and it seems that this is the case. From these calculations I've noticed that the way AM calculates Dual Mining profitability seems incorrect. I say this because there's no place to write down the custom hash rate for the dual mining (ETH+DCR / ETH+PASC / ETH+LBC / ETH+SC), only the hash rate for ETH and the other coins separately. The problem with this is that ClaymoreDual will never run the second coin at full speed, but only at a fraction of the speed without sacrificing ETH speed (adjusted by the -dcri value), so simply adding the ETH profitability plus other coin profitability will place dual mining higher than it really is.

To confirm this I wrote down the speed of the second coin benchmarks from the NHM client in the coin speed in AM. After doing this the profitability values of both clients were pretty close and dual mining in AM started to reflect the actual speed of the ClaymoreDual miner. So, my suggestion is to define the speeds for dual mining separately from the rest of the algorithms and make the profit calculations for dual mining based on these speeds. The speed of the other coins is now too low just to make dual mining calculations work correctly.

The dual mining hashrate configuration is a bit limited. I agree that this area could be improved.

Quote from: xChackOx on July 23, 2017, 05:15:27 PM

On another topic, it would be nice if we could had the option to hide the console for the managed profit miners. I've seen this option is available for the normal managed miners.

At the moment the configuration available for the Managed Profit Miners is a bit limited, because the original idea was that the profit switching feature should be as simple as possible. I might be adding more features in an Advanced section in the future.

Quote from: xChackOx on July 23, 2017, 05:15:27 PM

I also found an issue with Nist5 algo, every time it runs I get an "Invalid GPU parameters" or something like that. I tried it with CcMiner SP-mod and CcMiner-Alexis. While this happened, I noticed the miner restarting several times until it finally stopped but didn't start again. It would be better if AM switched to the next profitable algorithm and try again in a few minutes instead of completely stopping.

I actually don't know how to get Nist5 to work with ccminer in these scenarios, and I've had similar reports for other users. A workaround is to simply disable Nist5 algorithm in Awesome Miner. Maybe ccminer 2.x solves this?

Quote from: xChackOx on July 23, 2017, 05:15:27 PM

Another issue I found is with grouping profiles. I made a profile with the hash rates for 1 GTX1060. This profile have SHA-256 disabled (and other difficult algos too). Then I made a group, added this profile and chose 2 (for my 2 GTX1060). Everything works as it should, except in the Coins and Online Services tab. If I choose the GTX1060 profile in this tab, all the services update correctly and make calculations based on 1 GTX1060, but if I choose the group I made early (2 GTXT1060) then the SHA-256 goes to the top with a high profit. Remember that I disabled this algorithm and even put its hash rate at 0 MH/s. (screenshots)

This might be a display bug - I will take a look.