Quote from: joblo on March 22, 2016, 09:24:10 PM

Quote from: tbearhere on March 22, 2016, 08:27:10 PM

Quote from: semajjames on March 22, 2016, 08:08:49 PM

Quote from: tbearhere on March 22, 2016, 07:28:05 PM

Quote from: crackfoo on December 16, 2015, 10:59:09 PM

The profit switch is based off the 24h estimate not the actual which is listed on the page. Not much hash has been on lyra the past couple days for some reason so the actual profitability ended up lower than the estimate.

If you want to tweak you profit scale, making the number higher will increase the probability.

Why do you hide the real time profits ? ? ? hmmmmmmmmmm
Please show the real time paying.....
That means I can't setup a multipool switching app. You don't know the real price.

they are not hidden they are on the pool page ,, these figures are linked to zpool switching normalization ,,, every user will have different normalisation according to their own gpu clock speeds and therefore have different profits

just put your algos Mh/s into your password like this and it will work best for your miner settings

c=BTC,neoscrypt=0,x11=30.4,x13=22.6,x15=18,,qubit=25,quark=0

Ok so what we see is the real time paying ...thank you

And here is one of my bat files showing the actual hashrate I get and the pool should recognize based on one algo to the other.

:start
:loop

ccminer.exe -r 0 -a quark -C --cpu-priority 1 -o stratum+tcp://mine.zpool.ca:4033 -u wallet -p x11=6.5,quark=14,lyra2v2=10.4,neoscrypt=.396,qubit=9.2,x13=5.1,x15=4.5 -d 0,1
timeout /t 3

ccminer.exe -r 0 -a lyra2v2 -C --cpu-priority 1 -o stratum+tcp://mine.zpool.ca:4533 -u wallet -p x11=6.5,quark=14,lyra2v2=10.4,neoscrypt=.396,qubit=9.2,x13=5.1,x15=4.5 -d 0,1
timeout /t 3

ccminer.exe -r 0 -a neoscrypt -C --cpu-priority 1 -o stratum+tcp://mine.zpool.ca:4233 -u wallet -p x11=6.5,quark=14,lyra2v2=10.4,neoscrypt=.396,qubit=9.2,x13=5.1,x15=4.5 -d 0,1
timeout /t 3

ccminer.exe -r 0 -a qubit -C --cpu-priority 1 -o stratum+tcp://mine.zpool.ca:4733 -u wallet -p x11=6.5,quark=14,lyra2v2=10.4,neoscrypt=.396,qubit=9.2,x13=5.1,x15=4.5 -d 0,1
timeout /t 3

ccminer.exe -r 0 -a x11 -C --cpu-priority 1 -o stratum+tcp://mine.zpool.ca:3533 -u wallet -p x11=6.5,quark=14,lyra2v2=10.4,neoscrypt=.396,qubit=9.2,x13=5.1,x15=4.5 -d 0,1
timeout /t 3

ccminer.exe -r 0 -a x13 -C --cpu-priority 1 -o stratum+tcp://mine.zpool.ca:3633 -u wallet -p x11=6.5,quark=14,lyra2v2=10.4,neoscrypt=.396,qubit=9.2,x13=5.1,x15=4.5 -d 0,1
timeout /t 3

ccminer.exe -r 0 -a x15 -C --cpu-priority 1 -o stratum+tcp://mine.zpool.ca:3733 -u wallet -p x11=6.5,quark=14,lyra2v2=10.4,neoscrypt=.396,qubit=9.2,x13=5.1,x15=4.5 -d 0,1
timeout /t 3

goto loop

You can remove the timeouts as there are no synchronization issues to worry about. The next command can't start until the previous
one has fully exited. The only time I use a timeout is when I'm killing a background ccminer process from a bat process:

start ccminer.exe ...
loop:
monitor mining
if not time to switch goto loop
taskkill /f /im ccminer.exe
timeout /t 2
start ccminer.exe ...

They need that t3 on some rigs...or they crash.
I can't put a timer into the bat file....but I have one in the same folder running at 2 hour task kill and restart encase the miner crashes.