Version 6.4

Following observations regarding the refresh rate and considering the fact that 0.3 does not meet everybody's need for speed, we decided to let it refresh at 0.1 sec, and tested the software in these circumstances.

Here's the news on the web site.

Please attend to the disclaimer that will come up as soon as you set the rate below the default value.

Following observations regarding the refresh rate and considering the fact that 0.3 does not meet everybody's need for speed, we decided to let it refresh at 0.1 sec, and tested the software in these circumstances.

Here's the news on the web site.

Please attend to the disclaimer that will come up as soon as you set the rate below the default value.

Yeah!!! .. that awesome news ... Oxa I could ____ you.

I will try it out tomorrow during the evening racing.

Following observations regarding the refresh rate and considering the fact that 0.3 does not meet everybody's need for speed, we decided to let it refresh at 0.1 sec, and tested the software in these circumstances.

Here's the news on the web site.

Please attend to the disclaimer that will come up as soon as you set the rate below the default value.

Ohhhh era ora finalmente MF a 0,1 sec. I miei complimenti.per me adesso MF è Nr. 1!!!!

Ohhhh era ora finalmente MF a 0,1 sec. I miei complimenti.per me adesso MF è Nr. 1!!!!

Speriamo che tutto vada bene, ma per sicurezza imposta il limite richieste su 15 invece di 20.

Speriamo che tutto vada bene, ma per sicurezza imposta il limite richieste su 15 invece di 20.

Si questa è stata la prima cosa che ho fatto.Impostando il limite di sicurezza.La velocità è fondamentale,vediamo adesso come andranno i trigger.

I bet there was much partying in the smoke filled data rooms at BetFair the moment this was announced. I can hear those boys warming up their Data Request Charge till nicely on this news!
Having fallen foul of the DRC problem on so many occasions, I can only advise extreme caution at 0.1 refresh rate, before you inbox fills quicker from BetFair Data request people than if you had sent your email address to a company wanting to sell you Viagara!
 
That said what a brilliant improvement. As ever this initiative gives individuals the choice to decide their own boundaries. Well done once again the team at well done. 

There is nothing about some important changes of the requests calculation in our official announce.

The last version counts the silks requests as the general ones weighted 5.

So if you don't need the silks information please switch the "Download silks" option off.

The live scores requests are not counted at all.

It's also recommended to check your list of bets retrieving settings. These requests are weighted 5. Switch off updating unnecessary accounts (UK / AUS) and set the updating list of bets value as big as you can afford.

For example getting both UK and AUS accounts once per second "eats" 10 requests each second!

6.0.4.1 is insane!!!!!!!!!!!     

Running like a dream at 0.2 ... and yes I have a maximum request limit enabled.

Can someoone check and confirm please .. if you close and open(restart) 6.0.4.1 is your last trigger file loaded??

Interesting point 1oser
i shut down and opened up the platform and all the trigger block and disappeared.
There was not a trigger in sight .......NOTHING. .......It was a complete blank and extremely empty. The trigger block was devoid of all triggers that had previously been there merrily triggering away 10 minutes previously.
 
I thought i must have done something stupid again so ignored it. i only found out because horses were going off un hedged and i immediately knew there was a problem. When i saw right side of the action log empty it was clear what the problem was.
Was this what happened to you?

Just wait for the last market has been loaded. The triggers file is opened just after that (we need the list of markets to fill the "Markets" field for the triggers).

Because of the more accurate counting the requests it takes more time now.
We should disable the Triggers button until markets are loaded.

Just wait for the last market has been loaded. The triggers file is opened just after that (we need the list of markets to fill the "Markets" field for the triggers).

Because of the more accurate counting the requests it takes more time now.
We should disable the Triggers button until markets are loaded.

I am not sure this is the case ... but I will test again tonight during Kempton and confirm.

Yes, by my markets had been loaded for about 10 minutes and 1 race had already gone off with unhedged selections before i realised there was no triggers in the block.
I will do the same as 1oser today and try to re create what happened.

Ok .. had another try and definitely an issue on my side with remembering triggers.

When there are no markets loaded the last trigger file is remembered ...
as soon as I load UK/IRE racing win+place markets and restart the last trigger file is not remembered.

Yes, have to confirm that
Sorry. Will fix asap.

Yes, have to confirm that
Sorry. Will fix asap.

Awesome!