Hi, i wonder if anybody can explain to me please.
I have not used betangel for a monthbut before that i used it for 8 months solid so am very used to it.
however my first time back is on the 18:20 Kempton.
Historically the money where the back money meets the lay money and a tick or 2 either side will be changing rapidly in the pre 5 mins, but today all the money upwards and downwards are constantly changing about 2 times per seconds.
Journey was on 2.3 but all the tickes down to 1.8 that had money on it was rapidly changing and the same up to 4.3.
This has not happened before, wheta going on please?? Thanks
18:20 Kempton 12/11/14
betfair have shut down the old api so you must be on the latest version that as been written for the new api.mindiawl wrote:Yes on the ladder. Is this something that has changed recently. But no way are people moving money round on all steps of the ladder up and down and on all 10+ ladders at the same time it's impossible lol. Something is wrong here
last traded volume is a new "feature" that can be switched on/off in the ladder settings.
i think it was a maiden for fillies, if so you would not be surprised if the market was volatile/jumpy.(i rarely trade maidens on the all weather tracks)
if your refresh is set 200m/s it could make it seem that everything is jumpy about but, you might have a real problem?
it sounds similar to the problems some users were experiencing 2 weeks ago or so, when new api version was released.
if your refresh is set 200m/s it could make it seem that everything is jumpy about but, you might have a real problem?
it sounds similar to the problems some users were experiencing 2 weeks ago or so, when new api version was released.
Hmm, yes I updated to the new version last week but have not used it till now. Didn't like this at all, I never traded as I was screen to open a trade. Bet angel renewal is due soon, I'm not sure what to do now. Can't trade with software that behaves this way
the latest version is 1.37.4
make sure your on that version as there have been 1 or 2 updates since you uploaded last week - hopefully your not on the latest version and hence the problems your having.
personally i find nothing wrong with this version of bet angel, it works extremly well in my opinion
make sure your on that version as there have been 1 or 2 updates since you uploaded last week - hopefully your not on the latest version and hence the problems your having.
personally i find nothing wrong with this version of bet angel, it works extremly well in my opinion

Mindiawl, if you are still having the problems you decribed then try this. Go to settings then display and make sure the 'limit to best 3 prices only' is ticked. This should get rid of the constant changes you are seeing up and down the ladder away from the available price.
Also in the past if you have used the 'highlight last traded odds' (red,green,yellow flashes) this is now set to 300ms which can give the illusion of the movement on the ladders feeling very slightly slower. This can be set to 'clear on every update' by going to settings then ladder.
I hope that may help
Also in the past if you have used the 'highlight last traded odds' (red,green,yellow flashes) this is now set to 300ms which can give the illusion of the movement on the ladders feeling very slightly slower. This can be set to 'clear on every update' by going to settings then ladder.
I hope that may help
Hi thank for that will give it a go. However are we saying here that prices in all steps of the ladder constantly change not just the few up and down of where back meets lay? And I'm talking big moves on all steps on all horses. So people move money around this way? Surely not
I think it is something to do with the new API diplaying virtual bets up and down the whole ladder now so they added an option to have this limited to the best 3 prices only
I saw what you are describing when i first downloaded the new one and i think many others did as well. Ticking this box sorted the issue for me
I saw what you are describing when i first downloaded the new one and i think many others did as well. Ticking this box sorted the issue for me