[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 226.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: moppidoo on January 14, 2019, 12:48:44 AM

Patrike,

Bit of a problem with exchange/volume filtering (sorry been away for the past few weeks, so didn't go through the posts thoroughly if it's been mentioned already).

Coins are grayed out in the following scenario when
-> Coin meets the minimum volume set in Options -> Statistics Providers
-> Exchange list in API is empty

in the below example is Espers (ESP), Statistics Providers Ordering (CC > WTM > CTM).

Use all exchanges (check), minimum exchange volume (0.002 BTC)

CMC's 24h volume matches the API of approx $196 USD

I know where the problem is, it's similar to previous scenario where price is set to 0 if no exchange is available in the API, except this time it affects the volume, is it something you could add to use global value even if calculator returns no supported exchanges?

Within a statistics provider, for example CC or WTM, Awesome Miner handle the concept of no exchange.

Awesome Miner do find the coin on CC in this case, and CC has highest priority, it will currently not even look at the same coin if provided by WTM or CTM. The result is that even if what CC provides doesn't match the volume filter, Awesome Miner will not look at the additional exchanges at CTM. Each provider is processed individually and coins already found will be ignored if found again.

I understand you point here, but I will have to redesign a few concepts before the scenario you describe can be supported. Thanks for the feedback on this!

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: fredeq on January 13, 2019, 04:57:33 PM

On wtm we treat all 144,5 coins as zhash.

Just makes more sense from miner perspective to aggregate them under single name, as all of them use same miner and hashrate values.

Many thanks for your comment on this.

What you do here makes sense so I will use the same concept in Awesome Miner - make it ZHash all the time to avoid confusion.

GEBucky

copper member

Activity: 127

Merit: 1

Quote from: baf28 on January 13, 2019, 10:52:22 PM

Quote from: citronick on January 13, 2019, 10:47:58 PM

Quote from: baf28 on January 13, 2019, 10:05:10 PM

Quote from: GEBucky on January 13, 2019, 06:16:13 PM

Hi @Patrik. Thanks for including the latest version of gminer!. I had been using 1.18 manually. Given the somewhat odd way that gminer accepts parameters, I just created a pool for Leafpool and left everything blank except us.leafpool.com. Then configured each managed miner and passed everything through command line:

--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]

I can't seem to get a "standard config" working with the new gminer. I would think I could pull port and put that in the pool definition as standard ":3333", and put wallet address there. On each miner profile then add worker name/email.

for some reason it wont start under that configuration. It attempts to start the miner but gets a connection timeout on us.leafpool.com:3333. I can just leave it manual for now but would like to move to using the standard download.

I there anything unique to the gminer setup other than what I outlined above?

Thanks

I apologize, I did everything in a standard way, but I do not know how to post images of screenshots, please follow my links, everything is shown there. Thank.

Bump for you.... and your images looks like not supported.

https://yadi.sk/i/F2NsXSwb4PSgqA
https://yadi.sk/i/t3SwW5soDaC1AA
https://yadi.sk/i/us4ZpKaNXeseqA

Those appear to just be screenshots of the working miner. I was looking for specifics on the configuration. Thanks though.

moppidoo

jr. member

Activity: 348

Merit: 5

Patrike,

Bit of a problem with exchange/volume filtering (sorry been away for the past few weeks, so didn't go through the posts thoroughly if it's been mentioned already).

Coins are grayed out in the following scenario when
-> Coin meets the minimum volume set in Options -> Statistics Providers
-> Exchange list in API is empty

in the below example is Espers (ESP), Statistics Providers Ordering (CC > WTM > CTM).

Use all exchanges (check), minimum exchange volume (0.002 BTC)

CMC's 24h volume matches the API of approx $196 USD

I know where the problem is, it's similar to previous scenario where price is set to 0 if no exchange is available in the API, except this time it affects the volume, is it something you could add to use global value even if calculator returns no supported exchanges?

baf28

newbie

Activity: 117

Merit: 0

Quote from: patrike on January 13, 2019, 04:13:08 PM

Quote from: trucobit on January 13, 2019, 02:49:37 PM

Barely visible. Watch the capture, arrina are ZEL and BTZ de cointomine, and just below you can see a little ZAL of coinscalcutor

What I do not know if it is the cointomine api problem that calls the coins in another way internally, or some change in this latest version of today.

I have updated and just after it has happened. I have the 4 aggregators activated at the same time, Cointomine with premium API due to my donation.

I'll tell you if it can be fixed in some way.

This is basically the same issue and the same workaround can be applied. As the same coin can exists multiple times with different algorithms (for example Digibyte and a few more), Awesome Miner can list each combination of unique coin and algorithm.

In this case we have a few coins that are listed with both Equihash 144.5 (from CoinToMine) and ZHash (from WhatToMine/CoinCalculators?). Both will show up as Awesome Miner see they have different algorithms.

I will try to re-map some of these coins to the correct algorithms in Awesome Miner itself.

Edit: It looks like WhatToMine and CoinCalculators lists a few coins differently as well. XSG is one example - making it show up twice - one for each algorithm. Right now I'm a bit unsure which one is correct and this goes for a few coins.

There is a solution.
Options - Statistics Providers and Overridd coin algoritm Configure
Set ZEL to Zhash
Set BTCZ to Zhash
Then apply the changes and click the update button on the coins tab

baf28

newbie

Activity: 117

Merit: 0

Quote from: citronick on January 13, 2019, 10:47:58 PM

Quote from: baf28 on January 13, 2019, 10:05:10 PM

Quote from: GEBucky on January 13, 2019, 06:16:13 PM

Hi @Patrik. Thanks for including the latest version of gminer!. I had been using 1.18 manually. Given the somewhat odd way that gminer accepts parameters, I just created a pool for Leafpool and left everything blank except us.leafpool.com. Then configured each managed miner and passed everything through command line:

--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]

I can't seem to get a "standard config" working with the new gminer. I would think I could pull port and put that in the pool definition as standard ":3333", and put wallet address there. On each miner profile then add worker name/email.

for some reason it wont start under that configuration. It attempts to start the miner but gets a connection timeout on us.leafpool.com:3333. I can just leave it manual for now but would like to move to using the standard download.

I there anything unique to the gminer setup other than what I outlined above?

Thanks

I apologize, I did everything in a standard way, but I do not know how to post images of screenshots, please follow my links, everything is shown there. Thank.

https://4.downloader.disk.yandex.ru/preview/9c45a443adbb8a03e0c755519b1221b5937cd16ed6852b4210cfe09b7f52d52a/inf/TAgBtPohBL13YBP3LaWDgSoF70rIklXMnCBi4fGEvpQiIWhiK0fC8JFMQQUZmQVrwNQyf09wIM8De5_blhVnZw%3D%3D?uid=159202907&filename=2019-01-14_08-57-09.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664

https://2.downloader.disk.yandex.ru/preview/fd23deb23bf3f9d40a13525d23ad28ce5b2c47330c349270ddd4aae12a82e572/inf/ndRxsj49Ua_ZkIWPj-5jgAqGeCYz1sL_RiYb4SECOiOFVBmQNqt1DnZkbWl1_47u1zakCqMFikUNvkqY3ZPgPQ%3D%3D?uid=159202907&filename=2019-01-14_08-57-18.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664

https://4.downloader.disk.yandex.ru/preview/d38037e9090a0aafb05c07790b2d2c23ab1b56168970bae711ef04c657ef93b7/inf/V6I8mr-AW0GAMaz7I_GgQLRBGvac8SbBwuYxD50QKgXsQ--MgSy9-rZvDBecnx2G9ztzu2bUZtWE2vqVBeFMNg%3D%3D?uid=159202907&filename=2019-01-14_08-57-40.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664

Bump for you.... and your images looks like not supported.

https://yadi.sk/i/F2NsXSwb4PSgqA
https://yadi.sk/i/t3SwW5soDaC1AA
https://yadi.sk/i/us4ZpKaNXeseqA

citronick

legendary

Activity: 1834

Merit: 1080

---- winter*juvia -----

Quote from: baf28 on January 13, 2019, 10:05:10 PM

Quote from: GEBucky on January 13, 2019, 06:16:13 PM

Hi @Patrik. Thanks for including the latest version of gminer!. I had been using 1.18 manually. Given the somewhat odd way that gminer accepts parameters, I just created a pool for Leafpool and left everything blank except us.leafpool.com. Then configured each managed miner and passed everything through command line:

--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]

I can't seem to get a "standard config" working with the new gminer. I would think I could pull port and put that in the pool definition as standard ":3333", and put wallet address there. On each miner profile then add worker name/email.

for some reason it wont start under that configuration. It attempts to start the miner but gets a connection timeout on us.leafpool.com:3333. I can just leave it manual for now but would like to move to using the standard download.

I there anything unique to the gminer setup other than what I outlined above?

Thanks

I apologize, I did everything in a standard way, but I do not know how to post images of screenshots, please follow my links, everything is shown there. Thank.

Bump for you.... and your images looks like not supported.

baf28

newbie

Activity: 117

Merit: 0

Quote from: GEBucky on January 13, 2019, 06:16:13 PM

Hi @Patrik. Thanks for including the latest version of gminer!. I had been using 1.18 manually. Given the somewhat odd way that gminer accepts parameters, I just created a pool for Leafpool and left everything blank except us.leafpool.com. Then configured each managed miner and passed everything through command line:

--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]

I can't seem to get a "standard config" working with the new gminer. I would think I could pull port and put that in the pool definition as standard ":3333", and put wallet address there. On each miner profile then add worker name/email.

for some reason it wont start under that configuration. It attempts to start the miner but gets a connection timeout on us.leafpool.com:3333. I can just leave it manual for now but would like to move to using the standard download.

I there anything unique to the gminer setup other than what I outlined above?

Thanks

I apologize, I did everything in a standard way, but I do not know how to post images of screenshots, please follow my links, everything is shown there. Thank.

https://4.downloader.disk.yandex.ru/preview/9c45a443adbb8a03e0c755519b1221b5937cd16ed6852b4210cfe09b7f52d52a/inf/TAgBtPohBL13YBP3LaWDgSoF70rIklXMnCBi4fGEvpQiIWhiK0fC8JFMQQUZmQVrwNQyf09wIM8De5_blhVnZw%3D%3D?uid=159202907&filename=2019-01-14_08-57-09.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664

https://2.downloader.disk.yandex.ru/preview/fd23deb23bf3f9d40a13525d23ad28ce5b2c47330c349270ddd4aae12a82e572/inf/ndRxsj49Ua_ZkIWPj-5jgAqGeCYz1sL_RiYb4SECOiOFVBmQNqt1DnZkbWl1_47u1zakCqMFikUNvkqY3ZPgPQ%3D%3D?uid=159202907&filename=2019-01-14_08-57-18.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664

https://4.downloader.disk.yandex.ru/preview/d38037e9090a0aafb05c07790b2d2c23ab1b56168970bae711ef04c657ef93b7/inf/V6I8mr-AW0GAMaz7I_GgQLRBGvac8SbBwuYxD50QKgXsQ--MgSy9-rZvDBecnx2G9ztzu2bUZtWE2vqVBeFMNg%3D%3D?uid=159202907&filename=2019-01-14_08-57-40.png&disposition=inline&hash=&limit=0&content_type=image%2Fpng&tknv=v2&size=1349x664

GEBucky

copper member

Activity: 127

Merit: 1

Hi @Patrik. Thanks for including the latest version of gminer!. I had been using 1.18 manually. Given the somewhat odd way that gminer accepts parameters, I just created a pool for Leafpool and left everything blank except us.leafpool.com. Then configured each managed miner and passed everything through command line:

--algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --api 10050 --user 228c0952842698bffd2b1bce30ad2c612b6fc6exxx2a4fc4559aa2209a6b1b211e9.rig1/[email protected]

I can't seem to get a "standard config" working with the new gminer. I would think I could pull port and put that in the pool definition as standard ":3333", and put wallet address there. On each miner profile then add worker name/email.

for some reason it wont start under that configuration. It attempts to start the miner but gets a connection timeout on us.leafpool.com:3333. I can just leave it manual for now but would like to move to using the standard download.

I there anything unique to the gminer setup other than what I outlined above?

Thanks

fredeq

legendary

Activity: 1537

Merit: 1005

On wtm we treat all 144,5 coins as zhash.

Just makes more sense from miner perspective to aggregate them under single name, as all of them use same miner and hashrate values.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on January 13, 2019, 02:49:37 PM

Barely visible. Watch the capture, arrina are ZEL and BTZ de cointomine, and just below you can see a little ZAL of coinscalcutor

What I do not know if it is the cointomine api problem that calls the coins in another way internally, or some change in this latest version of today.

I have updated and just after it has happened. I have the 4 aggregators activated at the same time, Cointomine with premium API due to my donation.

I'll tell you if it can be fixed in some way.

This is basically the same issue and the same workaround can be applied. As the same coin can exists multiple times with different algorithms (for example Digibyte and a few more), Awesome Miner can list each combination of unique coin and algorithm.

In this case we have a few coins that are listed with both Equihash 144.5 (from CoinToMine) and ZHash (from WhatToMine/CoinCalculators?). Both will show up as Awesome Miner see they have different algorithms.

I will try to re-map some of these coins to the correct algorithms in Awesome Miner itself.

Edit: It looks like WhatToMine and CoinCalculators lists a few coins differently as well. XSG is one example - making it show up twice - one for each algorithm. Right now I'm a bit unsure which one is correct and this goes for a few coins.

trucobit

jr. member

Activity: 756

Merit: 2

Barely visible. Watch the capture, arrina are ZEL and BTZ de cointomine, and just below you can see a little ZAL of coinscalcutor

What I do not know if it is the cointomine api problem that calls the coins in another way internally, or some change in this latest version of today.

I have updated and just after it has happened. I have the 4 aggregators activated at the same time, Cointomine with premium API due to my donation.

I'll tell you if it can be fixed in some way.

trucobit

jr. member

Activity: 756

Merit: 2

Quote from: patrike on January 13, 2019, 12:51:37 PM

Quote from: baf28 on January 13, 2019, 12:39:35 PM

Quote from: trucobit on January 13, 2019, 12:34:48 PM

Quote from: baf28 on January 13, 2019, 11:53:25 AM

Quote from: trucobit on January 13, 2019, 11:16:16 AM

Hello @Patrike, I have updated and even a bug. Suddenly two coins in equihash 144.5 have gone up to an incredible profit, even 1 btc per day. is doing the autoprofit wrong with this failure.

I do not know if you will have to correct it or I have any option in the program to correct this AM failure.

I'm waiting for someone's help. Thank you.

strange, I'm fine and there is no this bug

Well, I have not touched anything. I have only updated and it has come out that way, and it persists. I have the currencies deactivated so that I do not mine them. Let's see what @patrike says because just before the update it showed up well, and after today's update, that has come out ... I do not know what could have happened.

I think I know what the problem is.
Problem in Cointomine.today calculator
Try using CoinCalculator.io and move it to the very top. I think after that you will be fine.
If not, wait for Patrike .
I'm sorry, I just want to help you.

CoinToMine is considering BTCZ to be Equihash 144.5, which isn't fully correct as it's the ZHash version of Equihash 144.5. Equihash 144.5 typically have a different exponential factor when calculating number of coins per day.

This is the reason why you only see this if CoinToMine is your primary coin source and not WhatToMine or CoinCalculators as they report it as the algorithm ZHash.

The workaround for the moment would be to go to the Options dialog, Statistics Provider section, and use "Override coin algorithm" to set "BTCZ" to the ZHash algorithm. Then Awesome Miner will apply the correct calculations.

The reason why it worked better with the previous version of Awesome Miner was that Equihash 144.5 coins wasn't loaded at all from CoinToMine - so you only got BTCZ from CoinCalculators/WhatToMine.

I see the error, in the coins tab I have 2 times BTCZ and 2 times ZEL, one of cointomine that is the one that is wrong and others of Coinscalculator that is correct. They change the difficulty and hash.

What I do not understand is because AM allows two equal currencies to exist two ZEL and two BTCZ

If I deactivate Cointomine, the problem disappears. If I leave Cointomine activated, Zel and BTCZ appear in first place with the wrong data.

The truth that cointomine is giving many headaches.

but everything has happened after the update. Test PAtrike to activate all aggregators and see if it happens to you

baf28

newbie

Activity: 117

Merit: 0

Quote from: patrike on January 13, 2019, 01:37:08 PM

Quote from: baf28 on January 13, 2019, 01:15:41 PM

Quote from: patrike on January 13, 2019, 01:12:35 PM

Quote from: baf28 on January 13, 2019, 12:04:51 PM

Setup: Force nVidia CUDA mining software to order divices by PCI Bus ID - no longer available, return it please, it is very necessary, please help.

This settings for ver Version 6.0 (2018-11-28) - is available

Cur ver 6.1 2019-01-13 - not available

Please return this option back to mining settings

You will find this setting in the Options dialog, GPU settings now. There are a number of settings moved to this new section.

This new section starts with the premium version, and was earlier everywhere.

Or is it enabled by default?

Sorry - this is for sure a bug in 6.1. It's only supposed to be the MSI Afterburner settings that should be disabled unless you have Premium Edition or above.

The other settings like CUDA device order should of course be available for everyone. Thanks for finding this issue - I will correct it.

A workaround for the moment would be to exit Awesome Miner and manually modify ConfigData.xml (in %appdata%\AwesomeMiner\) and change the value of "CudaOrderByPciBusId" from False to True.

Thank.

I thought that I was picky)))
Good thing I could help, thank you.

true

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: baf28 on January 13, 2019, 01:15:41 PM

Quote from: patrike on January 13, 2019, 01:12:35 PM

Quote from: baf28 on January 13, 2019, 12:04:51 PM

Setup: Force nVidia CUDA mining software to order divices by PCI Bus ID - no longer available, return it please, it is very necessary, please help.

This settings for ver Version 6.0 (2018-11-28) - is available

Cur ver 6.1 2019-01-13 - not available

Please return this option back to mining settings

You will find this setting in the Options dialog, GPU settings now. There are a number of settings moved to this new section.

This new section starts with the premium version, and was earlier everywhere.

Or is it enabled by default?

Sorry - this is for sure a bug in 6.1. It's only supposed to be the MSI Afterburner settings that should be disabled unless you have Premium Edition or above.

The other settings like CUDA device order should of course be available for everyone. Thanks for finding this issue - I will correct it.

A workaround for the moment would be to exit Awesome Miner and manually modify ConfigData.xml (in %appdata%\AwesomeMiner\) and change the value of "CudaOrderByPciBusId" from False to True.

baf28

newbie

Activity: 117

Merit: 0

Quote from: patrike on January 13, 2019, 01:12:35 PM

Quote from: baf28 on January 13, 2019, 12:04:51 PM

Setup: Force nVidia CUDA mining software to order divices by PCI Bus ID - no longer available, return it please, it is very necessary, please help.

This settings for ver Version 6.0 (2018-11-28) - is available

Cur ver 6.1 2019-01-13 - not available

Please return this option back to mining settings

You will find this setting in the Options dialog, GPU settings now. There are a number of settings moved to this new section.

This new section starts with the premium version, and was earlier everywhere.

Or is it enabled by default?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: baf28 on January 13, 2019, 12:04:51 PM

Setup: Force nVidia CUDA mining software to order divices by PCI Bus ID - no longer available, return it please, it is very necessary, please help.

This settings for ver Version 6.0 (2018-11-28) - is available

Cur ver 6.1 2019-01-13 - not available

Please return this option back to mining settings

You will find this setting in the Options dialog, GPU settings now. There are a number of settings moved to this new section.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: baf28 on January 13, 2019, 11:48:47 AM

Quote from: patrike on January 13, 2019, 07:07:53 AM

Quote from: baf28 on January 12, 2019, 08:14:58 AM

I also noticed that when the internet disappears for 2 minutes, the awesome miner constantly restarts gminer
or if the authorization error "Authorization on Stratum Server Failed: Login failed" also awesome miner causes gminer to restart.
Can I fix this?

Quote

Initialize diagnostics (2)
Starting Diagnostics. Awesome Miner version: 6.0.11
OS: Microsoft Windows 10 Pro 64-bit
nVidia driver version: 416.34
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 2
Engine Type: 14, Auto Download: False, EnginePath: D:\Shara\Maйнинг\Miner Soft\gminer_1_17_windows64\miner.exe, Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: 14, IsProfitMiner: False)
====================================================================================================
D:\Shara\Maйнинг\Miner Soft\gminer_1_17_windows64\miner.exe --ssl 1 -a 150_5 -d 1 2 -s eu-ru01.miningrigrentals.com -n 3322 -u baf.115445 -p x --pers auto -w 0 --api 4029
====================================================================================================
Mining Engine Process started, PID: 10388
> +----------------------------------------------------------------+
> | GMiner Equihash Miner v1.17 |
> +----------------------------------------------------------------+
> Algorithm: Equihash 150,5
> Stratum server:
> host: stratum+ssl://eu-ru01.miningrigrentals.com:3322
> user: baf.115445
> password: x
> Power calculator: on
> Color output: on
> Watchdog: off
> API: http://127.0.0.1:4029
> Log to file: off
> Selected devices: GPU1 GPU2
> Temperature limits: 90C 90C
> ------------------------------------------------------------------
> 18:44:24 Connected to eu-ru01.miningrigrentals.com:3322
> 18:44:26 Authorization on Stratum Server Failed: Login failed
> 18:44:26 All user mining pools are unavailable

====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed

What happens here is the Gminer process is terminating. The diagnostics indicate this by printing the message "Unexpected exit of mining software".

When mining, Awesome Miner will react to the fact that Gminer no longer are running, consider it to be a crash or similar issue, and then restart Gminer again. I suppose this will happen until Gminer reconnect again and keep running and right now I don't think there are any good solutions to this.

I propose to add an option: do not restart the miner when there is no connection to the pool.

true

T-rex - not restart for internet los
Gminer - restart for internet los

As you noticed, this behavior is specific to which mining software you run. Awesome Miner doesn't really know that progress of the connection between the mining software and the mining pool. Most mining software will keep trying to connect. If they never connect Awesome Miner will then detect this by the fact that no Accepted shares are being produced.

In this case, Gminer itself terminate itself and Awesome Miner isn't part of that decision and cannot do anything about it. Awesome Miner will just react to the fact that Gminer no longer are running and will restart it.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: baf28 on January 13, 2019, 12:39:35 PM

Quote from: trucobit on January 13, 2019, 12:34:48 PM

Quote from: baf28 on January 13, 2019, 11:53:25 AM

Quote from: trucobit on January 13, 2019, 11:16:16 AM

Hello @Patrike, I have updated and even a bug. Suddenly two coins in equihash 144.5 have gone up to an incredible profit, even 1 btc per day. is doing the autoprofit wrong with this failure.

I do not know if you will have to correct it or I have any option in the program to correct this AM failure.

I'm waiting for someone's help. Thank you.

strange, I'm fine and there is no this bug

Well, I have not touched anything. I have only updated and it has come out that way, and it persists. I have the currencies deactivated so that I do not mine them. Let's see what @patrike says because just before the update it showed up well, and after today's update, that has come out ... I do not know what could have happened.

I think I know what the problem is.
Problem in Cointomine.today calculator
Try using CoinCalculator.io and move it to the very top. I think after that you will be fine.
If not, wait for Patrike .
I'm sorry, I just want to help you.

CoinToMine is considering BTCZ to be Equihash 144.5, which isn't fully correct as it's the ZHash version of Equihash 144.5. Equihash 144.5 typically have a different exponential factor when calculating number of coins per day.

This is the reason why you only see this if CoinToMine is your primary coin source and not WhatToMine or CoinCalculators as they report it as the algorithm ZHash.

The workaround for the moment would be to go to the Options dialog, Statistics Provider section, and use "Override coin algorithm" to set "BTCZ" to the ZHash algorithm. Then Awesome Miner will apply the correct calculations.

The reason why it worked better with the previous version of Awesome Miner was that Equihash 144.5 coins wasn't loaded at all from CoinToMine - so you only got BTCZ from CoinCalculators/WhatToMine.

baf28

newbie

Activity: 117

Merit: 0

Quote from: trucobit on January 13, 2019, 12:34:48 PM

Quote from: baf28 on January 13, 2019, 11:53:25 AM

Quote from: trucobit on January 13, 2019, 11:16:16 AM

https://dl.dropboxusercontent.com/s/qqbpqteayjtrx1z/Captura%20de%20pantalla%202019-01-13%20a%20las%2017.12.10.png

Hello @Patrike, I have updated and even a bug. Suddenly two coins in equihash 144.5 have gone up to an incredible profit, even 1 btc per day. is doing the autoprofit wrong with this failure.

I do not know if you will have to correct it or I have any option in the program to correct this AM failure.

I'm waiting for someone's help. Thank you.

strange, I'm fine and there is no this bug

Well, I have not touched anything. I have only updated and it has come out that way, and it persists. I have the currencies deactivated so that I do not mine them. Let's see what @patrike says because just before the update it showed up well, and after today's update, that has come out ... I do not know what could have happened.

I think I know what the problem is.
Problem in Cointomine.today calculator
Try using CoinCalculator.io and move it to the very top. I think after that you will be fine.
If not, wait for Patrike .
I'm sorry, I just want to help you.

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 226. (Read 703561 times)