Quote from: sundownz on October 25, 2017, 09:50:06 PM

Quote from: minerx117 on October 25, 2017, 09:24:13 PM

try: Reset Profit.bat then re run see if that fixes problem

v2.2 uses different profit api request than all other versions of Nemosminer..

it doesn't switch nearly as much now its meant to be like that,

here is my gaming pc with a single 1070 been running for over 24hour straight..
https://imgur.com/a/w1NYg

make sure your running latest commits i have done a lot of changes even since v2.2 was released
https://github.com/nemosminer/NemosMiner-v2.2/archive/master.zip

Regards
Nemo

ResetProfit.bat does not fix it.

I will try the newest revision of 2.2

I will having workers sitting on an algo for days that is clearly extremely low on profit when it sticks -- unless I restart the program.

Newer version of 2.2 does seem to fix the issue I was having.

-----

On another topic... is there a way to make the NEMO software use the "estimate_current" data instead of the "actual_last24h" data ?

I tried changing both reference to "actual_last24h" in the Zpool.ps1 file but when I do so it won't show the list of algos.

The reason I ask... a huge amount of my hash power has been sitting on "sib" for over 2 hours since the "actual_last24h" figure is 0.027 (making it look like a good choice) -- but the "estimate_current" is 0.0044 -- the "estimate_current" seems more like reality as I have literally made nothing in 2 hours from my workers on sib (20 machines right now with 80 GPUs).

Before I updated to the newer 2.2 none of my PCs would work on "sib" -- wasn't even on my list. I thought about disabling it... but I imagine the same problem could happen again with a different algo.