Any word on a fix for the dozen or so coins that seem to show extremely high payouts even though they are the same as other pools? For example I tried using an exchange price on one of them to see if that would make a difference, but it doesn't seem too. Just seems odd that a few coins from multiple pools seem to have this issue.

Yes, a fix for this would be great.I have resorted to just turning off or removing those coins/algos with the super inflated numbers.

Any word on a fix for the dozen or so coins that seem to show extremely high payouts even though they are the same as other pools? For example I tried using an exchange price on one of them to see if that would make a difference, but it doesn't seem too. Just seems odd that a few coins from multiple pools seem to have this issue.

Yes, a fix for this would be great.I have resorted to just turning off or removing those coins/algos with the super inflated numbers.

There is a setting that you can set to ignore outliers, but not sure if it works or not.

I just tried to set nicehash eth/equil algo switch but in the console i just see starting row and no miner output in there is it normal? All my usewindow are true but still no separate command promt window?

do not work either, if they do what is expected by them, mining still would be possible, as price check is not banned, only checking ballance, speed and worker!

Version reloaded. Now disabled indeed. YIIMP became recently overloaded because of a lot of API requests, so balance and statistics were disabled by pool. So only profit calculation supported by them for a moment.

Ok, for some reason usewindow had top be changed in MinerControl.conf not in General.conf, is that bug or normal?

It is the same thing. Since ver 17. MC supports also separated into 4 parts config file (general, wallets, algorithms, pools). It is done to make easier config replication between rigs (basically you need to correct algorithms part only, others may be copied without changes).Usewindow can be set either globally in "general" part, in this case all miners will start in separate window, or for particular coin, applied for this coin only.

1) With only the latest versions, the General parameter 'minprice' no longer seems to work. Even if all Net values are negative, MC will mine regardless of the value of 'minprice' (be it 0 or some other positive value, even a value in the thousands).

2) A long-standing bug that might be related to bug 1: when the Net value is negative for the 'Running' algo, MC will not switch to other more positive Pending values, and will not stop the current job at all if there are no positive Net values. It will only switch after stopping the current job manually, or automatically via the General 'maxtime' setting.

MC doesn't handle negative Net Profit values well.

Another question: when will the latest source code be posted on Github? I don't think it's been been updated since 1.7.0.0

I have noticed some discrepancies between the numbers given by Miner Control and those calculated by WhatToMine.

For example (and to make things simpler), let's suppose I have a rig with the capacity of 1,000,000,000 hashes/sec for Equihash.If you input 1,000,000,000 into WhatToMine for Zencash, it will tell you that you could earn 9.252759 BTC per day.Your program says that for 1GH of Equihash, you would obtain 2,793.996 BTC

The same discrepancy happens when I input into WTM my actual hash rate and it spits out a number which is very very different to what MinerControl calculates.This is very serious as the program would be mining coins which are not as profitable as it says.

I have tried several coins with several different algorithms and the numbers are never even close and I verified that the exchange rate and the difficulty are the same for your program and WTM.Am I making a mistake somewhere? Could you please verify this?

EDIT:I think I found the reason.The "price" column will always be off, no matter what.The "Net_$" column will match WTM numbers as long as the BTC exchange rate and the difficulty are the same.So at least the calculations are only off for those coins without a difficulty value.

Which brings me to the next question:How can I make sure that the difficulty is pulled from WTM?I see some of them are empty even when the coin is listed at WTM.

1) With only the latest versions, the General parameter 'minprice' no longer seems to work. Even if all Net values are negative, MC will mine regardless of the value of 'minprice' (be it 0 or some other positive value, even a value in the thousands).

2) A long-standing bug that might be related to bug 1: when the Net value is negative for the 'Running' algo, MC will not switch to other more positive Pending values, and will not stop the current job at all if there are no positive Net values. It will only switch after stopping the current job manually, or automatically via the General 'maxtime' setting.

MC doesn't handle negative Net Profit values well.

Another question: when will the latest source code be posted on Github? I don't think it's been been updated since 1.7.0.0

As always: thanks!!

For the moment I am working on proxy mode for MC. One instance as mater, others slaves. I'll test how MC handles negative values soon.I don't post beta codes on GitHub, as far as there is huge amount of changes. Only stable releases will be there.

If you want to check the actual code, it is published in Visual Studio Team Services.Login: mc_developer@outlook.comPassword: MinercontrolEveryone having skills in C# and own ideas is welcomed.

I have noticed some discrepancies between the numbers given by Miner Control and those calculated by WhatToMine.

For example (and to make things simpler), let's suppose I have a rig with the capacity of 1,000,000,000 hashes/sec for Equihash.If you input 1,000,000,000 into WhatToMine for Zencash, it will tell you that you could earn 9.252759 BTC per day.Your program says that for 1GH of Equihash, you would obtain 2,793.996 BTC

The same discrepancy happens when I input into WTM my actual hash rate and it spits out a number which is very very different to what MinerControl calculates.This is very serious as the program would be mining coins which are not as profitable as it says.

I have tried several coins with several different algorithms and the numbers are never even close and I verified that the exchange rate and the difficulty are the same for your program and WTM.Am I making a mistake somewhere? Could you please verify this?

EDIT:I think I found the reason.The "price" column will always be off, no matter what.The "Net_$" column will match WTM numbers as long as the BTC exchange rate and the difficulty are the same.So at least the calculations are only off for those coins without a difficulty value.

Which brings me to the next question:How can I make sure that the difficulty is pulled from WTM?I see some of them are empty even when the coin is listed at WTM.

Daily profitability in BTC from WTM is calculated in MC by formula 86400 / blocktime * blockrate / nethash * exchangerate.If you check the basic list of top coins on WTM titke page, the results of MC correspond to 99,9%. Check that you define the same hashrates as in MC.

1) With only the latest versions, the General parameter 'minprice' no longer seems to work. Even if all Net values are negative, MC will mine regardless of the value of 'minprice' (be it 0 or some other positive value, even a value in the thousands).

2) A long-standing bug that might be related to bug 1: when the Net value is negative for the 'Running' algo, MC will not switch to other more positive Pending values, and will not stop the current job at all if there are no positive Net values. It will only switch after stopping the current job manually, or automatically via the General 'maxtime' setting.

MC doesn't handle negative Net Profit values well.

Another question: when will the latest source code be posted on Github? I don't think it's been been updated since 1.7.0.0

As always: thanks!!

For the moment I am working on proxy mode for MC. One instance as mater, others slaves. I'll test how MC handles negative values soon.I don't post beta codes on GitHub, as far as there is huge amount of changes. Only stable releases will be there.

If you want to check the actual code, it is published in Visual Studio Team Services.Login: mc_developer@outlook.comPassword: MinercontrolEveryone having skills in C# and own ideas is welcomed.

Thank you for this! I'll be taking a look soon, and will happily contribute where/when I can.

What is the point of this? It doesn't seem to affect anything. I would rather have another pricing feed since WTM sucks for coin support. CMC will let you do 10 queries per minute. Can it be implemented as backup to WTM?

how to setup different hashrate because DAG size is different but algo is same?

Create new string in algorithms with any other name, for example "exphash" or "nhethash" then in pools section use this name in "algo" description for particular coin

it works, thanks

I don't think it works with the BTC auto-converters Nicehash, Hashrefinery or Zpool. I think the algos are hard-coded in MC or at the pool. Zpool wouldn't recognize "skunk2" for instance. Can you confirm?