Recent Posts

Pages: 1 2 3 4 5 6 7 8 9 10
1
Quote
I hope in the next version you can solve the event_id issue i talked about in the support (my open ticket). 

It should be solved now (see the Problems Fixed section). Have you experienced it with the new version?
2
Quote
I am not sure if it's a betfair's issue or a new version's one, but the MFPro isn't deleting the football markets after they finish.
The preliminary testing did not reveal this problem, so I will need more time to reproduce it. Does it happen only with football markets or with any market?
Hi Oxa,
I am only using MFPro on football markets at the moment. So, i canĀ“t talk about the other markets.
It's strange because noone else is complaining, so, i start thinking why is it happening in my case?
Anyway, just for you to be sure:
in the general options tab of settings, it's checked the option "delete finished markets automatically" of market settings.
I downloaded the new version a couple of days ago, and since then it stopped deleting automatically the markets in all instances i am working with. I didn't change anything in the settings, so, it's in the minimum strange.
Thanks
3
Quote
Regarding the Invalid floating point error -- that's a pain! Will have to this of some other ways to catch it. But just to refresh my memory, does the below scenario match yours? 1. In the evening load all horse races for tomorrow. Leave MF Pro running. 2. Next day the error comes up straight away or after the first market starts refreshing. Is that correct?
Hi Oxa.
For me, the error occurs in different scenarios:

1: MFP loads loads the markets early in the morning and refreshes them every few minutes throughout the day.  That can produce the error.

2: MFP loads loads the markets early in the morning and does not refresh them until just before the off.  That can also produce the error, even when the market is just idle and not yet refreshing before the off.

In both cases, visually the error affects the name of the last selection, and the selections name reappears after the error is dismissed.  I have to dismiss the error 3 times before it goes away and the name of the last selection is restored to the screen.  

If I then mimimise this instance of mfp and then maximise it again, the error reoccurs.

The error does not occur on every market, but if it occurs on a market, then it will also occur on the same market in overy other instance of mfp I have running. eg if I have 3 instances of mfp with a 2pm horse racing market loaded, the error will occur in all 3 instances of mfp.  This is true if the market is refreshing or if it is idle.

For me the error mosly occurs on UK/IRE horse racing.  I do not load other countries horse racing so I can't comment on those.  I do load a lot of football markets, and the error does happen in those, but very rarely.

Hope that helps you find this needle in a haystack!
4
Quote
 I am not sure if it's a betfair's issue or a new version's one, but the MFPro isn't deleting the football markets after they finish.

The preliminary testing did not reveal this problem, so I will need more time to reproduce it. Does it happen only with football markets or with any market?

Regarding the Invalid floating point error -- that's a pain! Will have to this of some other ways to catch it. But just to refresh my memory, does the below scenario match yours?

1. In the evening load all horse races for tomorrow. Leave MF Pro running.

2. Next day the error comes up straight away or after the first market starts refreshing.

Is that correct?
5
Troubleshooting / Re: Invalid Floating Point Operation
« Last post by Yoda on Mon, 10 May, 2021, 17:35 »
Hi there, 

I have the same problem!! 

6
Triggers / Re: Lay book percent
« Last post by MarkV on Mon, 10 May, 2021, 14:49 »
for some reason your topic is in Portuguese forum and I can't move it.

I was also going to add:

To get the lay book % for all selections with lay prices:

selections lay price is between 1.01 and 1000
and selections trigger expression match_l_book is greater than x 
7
Triggers / Re: Lay book percent
« Last post by MarkV on Mon, 10 May, 2021, 14:41 »
Hi
Try: match_l_book which is the lay book % of matching selections that met all previous conditions.

e.g. as the last condition in your dutching trigger:
and selections trigger expression match_l_book is greater than x   
8
Hi Oxa, I can confirm the "Invalid" error above is still happening on UK/Ire horse racing markets Cheers, Rich
Hi Oxa

I'm afraid it's still happening with me as well. I have an Nvidia Graphics card. No idea if an AMD card would solve it, but I'll give it a go if you think it might be GPU related?

The reason (for me) that it's an issue is that sometimes it crashes that instance of mfp.  I can have open lay positions that will not be closed if I relaunch mfp, because the trigger has no idea that it has previously fired as the programme crashed after the lay bets were placed.

Other than that on-going issue, the new build is running very well.  In the previous build, the market locator would often miss a few markets in one instance of mfp, yet pick them up in another with the same market locator template running one minute later. (I run them one minute apart to avoid any possible conflict with them both trying to access the same market locator template at the same time.)  I don't know if you tweaked it at all, but so far (3 days) they are now all loading the same number of markets.

Thanks for all your hard work.
9
Triggers / Lay book percent
« Last post by COLING on Mon, 10 May, 2021, 12:08 »
hi, i have a trigger that dutch lays if the book percent goes over a certain percentage, i have( if market lay book percent is greater than), this is fine but some times there are not lay prices for all selections so no laybook percent, is there a condition i can use to work out the lay book percent for all selections when this happens so my bet will still fire .
cheers colin
10
Triggers / Re: lay over gols Martingale
« Last post by Yoda on Mon, 10 May, 2021, 11:12 »
Olha esse exemplo por favor!!
Pages: 1 2 3 4 5 6 7 8 9 10