You see how his "aparam1": is set. That is the directory where your miner is located. And "aparam2": is the actual name of the miner, in his case it's sgminer. Just in case you're still not sure, Miner Control is not a miner in and of itself. You have to use it in conjunction with sgminer or the nvidia miners. In Miner Control's config, you point to your miner. Does that help?

You see how his "aparam1": is set. That is the directory where your miner is located. And "aparam2": is the actual name of the miner, in his case it's sgminer. Just in case you're still not sure, Miner Control is not a miner in and of itself. You have to use it in conjunction with sgminer or the nvidia miners. In Miner Control's config, you point to your miner. Does that help?

You see how his "aparam1": is set. That is the directory where your miner is located. And "aparam2": is the actual name of the miner, in his case it's sgminer. Just in case you're still not sure, Miner Control is not a miner in and of itself. You have to use it in conjunction with sgminer or the nvidia miners. In Miner Control's config, you point to your miner. Does that help?

All hail & +1

I didn't mean to come off as sarcastic if I did. ha.

Just let us know if you need more help fenomenhaa, I'll def be needing it soon.

You see how his "aparam1": is set. That is the directory where your miner is located. And "aparam2": is the actual name of the miner, in his case it's sgminer. Just in case you're still not sure, Miner Control is not a miner in and of itself. You have to use it in conjunction with sgminer or the nvidia miners. In Miner Control's config, you point to your miner. Does that help?

@jch9678 just problem on wepaybtc config, it's about aparam1:: "ny" ,"am" etc.. cannot recognise from Miner Control, what should i do?

Wepaybtc is kind of a special situation. You can only use their miner, meaning you don't get to use your custom sgminer, and they don't support nvidia miners. You (or Miner Control) don't actually get to choose which algorithm is mined. They choose it on the server side and you never see it. They just provide profitability numbers.

This is the way I plan on implementing wepaybtc. So go here http://wepaybtc.com/start/ and download their miner, they are up to wepaybtcsgminer400. Place it in a different directory than your other sgminer. Change their provided config, wepaybtc.conf, to your liking, including which server is closest to you. Here is my Miner Control config:

Notice I've left the variables empty and input them in the body. Credit to Zels for this, it's actually how I'm going to provide details for every pool. This way when Miner Control sees that wepaybtc is reporting, for example, x13 is the most profitable, it goes to the folder C:\wepaybtcsgminer400 finds sgminer.exe and uses wepaybtc.conf. If wepaybtc x11 is the most profitable it finds the same config, because wepaybtc chooses the algorithm servers side. I'm not completely sure how this works in your situation because I don't use any variables, so I don't know what takes precedence, aparam1 or the code above.

But this brings me to a question I have for others, even though wepaybtc is reporting it's profitabilty correctly, we don't know what our hashrate is using their miner, so Miner Control can't make the best choice. For example my 290x hash x11 around 8.7 MH/s on any given pool but on wepaybtc I have no idea what it hashes at. Miner Control assumes it hashes at 8.7 but I know it's much less than that. How are people dealing with this problem, are you weighing wepaybtc less?

But this brings me to a question I have for others, even though wepaybtc is reporting it's profitabilty correctly, we don't know what our hashrate is using their miner, so Miner Control can't make the best choice. For example my 290x hash x11 around 8.7 MH/s on any given pool but on wepaybtc I have no idea what it hashes at. Miner Control assumes it hashes at 8.7 but I know it's much less than that. How are people dealing with this problem, are you weighing wepaybtc less?

You could add a new algo "x11wpb", use it as algo under the pool too betbut set "priceid" to "x11". But I think that just adding a weighting would be the easiest

But this brings me to a question I have for others, even though wepaybtc is reporting it's profitabilty correctly, we don't know what our hashrate is using their miner, so Miner Control can't make the best choice. For example my 290x hash x11 around 8.7 MH/s on any given pool but on wepaybtc I have no idea what it hashes at. Miner Control assumes it hashes at 8.7 but I know it's much less than that. How are people dealing with this problem, are you weighing wepaybtc less?

You could add a new algo "x11wpb", use it as algo under the pool too bet set "priceid" to "x11". But I think that just adding a weighting would be the easiest

That's a good idea especially if you want to get better control of each algorithm individually. If you just weight it according to x11, it could be like this. My 290x on x11 = 8.7 and after some experimentation with payouts I conclude my 290x hashes at 6 on wepaybtc. Then I would weight it 6/8.7 = .69 Right?, I think that's one way you could go about finding what the weight should be. But if you look at x13, the ratios could be different and the weight would have to be different. So you could use kbomba's idea for each algorithm.

This is just way too much work for one pool that for the majority of the time isn't going to pay as well as yaamp or westhash. Unless someone comes up with figures for wepaybtc, I'm just going to weight it 0 or .5

Now that sp's ccminer v42 has a working WhirlpoolX algo I've updated the examples in the first post to support it. I'm getting 152mh/s on my 2x750Ti setup which is making it very competitive. Just behind Quark at the moment.

I first thought you were mining by average, which would be normal, as it flattens out the prices and reduces switches. Do you have minprofit set too? That also reduces switches. Same for "ignoreoutliers".

Dynamic switching on the other hand speeds up switching.

What kind of miners do you have?

PS: Most of those settings can be handy but need finetuning to your taste. I do not know the ideal values