Recent Posts

Pages: « 1 2 3 4 5 6 7 8 9 10 »
11
General discussion / Re: Support??????????????????????????
« Last post by Oxa (WellDoneSoft) on 17 Apr 2024, 12:20 »
Hello!

I have reviewed your settings and did not find anything that could cause repeated crashes. The only thing I noticed is that your Market Locator is set to search markets every 9 minutes. I recommend increasing that to at least 30 minutes, especially if your Market Locator search criteria are very broad. A market search is a very resource-consuming operation, so do not overwhelm your PC's CPU and memory by running it too often.

You will need to to have a closer look at your program setup:
For example:

- Test the program without running any triggers. Does it keep crashing? If not, then the problem is somewhere in your triggers. Check for special characters in the trigger names. 

- In the triggers check whether all the variables you are creating are resolving to valid values. If you are using an IF function anywhere in your triggers or an arithmetic expression with a trigger variable that was not resolved to any value, the triggers will eventually crash as the expression will grow endlessly.

- Try clearing up your logs: sometimes the old logs can be the problem. Go to this folder and remove it, then restart MF Pro:

c:\Users\%username%\MarketFeeder Pro 8\profiles\%profile name%\logs

- Check Program Log for any error messages that could give you a clue as to what is happening and why. 

Also, take a look at this article and try optimizing your program settings accordingly:

https://marketfeeder.co.uk/learn/articles/mf-pro-optimal-configuration/
13
Triggered betting / Re: Imported picks bettings
« Last post by Oxa (WellDoneSoft) on 17 Apr 2024, 10:56 »
Hello!

Judging from the screenshot, only one selection's name was imported successfully.

Check your import file and make sure all the selections' names are spelled correctly, exactly one name per line, and all of them have a Tab character between the name and the imported price.
14
Troubleshooting / Re: Green up trigger
« Last post by goodyflyer on 16 Apr 2024, 15:06 »
Cheers
15
Добрый день. У вас есть триггер

https://marketfeeder.ru/learn/triggers/fibonacci/

Помогите переписать его (или условие в триггере) чтобы он работал по последовательности 1, 1, 2, 3, 5, 8, 13, 21, 34, 55 ...., а не 1, 2, 3, 5, 8, 13, 21, 34, 55 ... , то есть начинался с 1 - 1 - 2, а не как сейчас 1 - 2.
16
Troubleshooting / Re: Problem with now_time_datestr
« Last post by MarkV on 16 Apr 2024, 13:10 »
Hi
Yes it does seem to be parsing the date forward slashes as division.

My suggestion here is to use INTEGER(now_time). The decimal part of now_time is hrs, mins, secs so if the decimal is removed then you can compare the date.

set user variable dateString value: INTEGER(now_time)
and then in the condition:
or favourite's trigger expression dateString is not equal to INTEGER(now_time)
    
17
Troubleshooting / Re: Green up trigger
« Last post by Tim (WellDoneSoft) on 15 Apr 2024, 18:26 »
18
Troubleshooting / Re: Problem with now_time_datestr
« Last post by andyock on 15 Apr 2024, 17:55 »
Sorry wrong attachment!! Attached here the two correct files apologies.
19
Troubleshooting / Problem with now_time_datestr
« Last post by andyock on 15 Apr 2024, 17:41 »
Hi. Not sure what I'm doing wrong here help would be appreciated.
I have a trigger which is checking in its condition the value of now_time_datestr against a user variable containing a previous assignation of said variable. basically I'm looking for a date change between the last market where the trigger was run and the current one.
I've attached the trigger and the log. The condition check is not working correctly because the previous value of the date stored in variable dateString is not being preserved as a string. The intermediate and final values are different namely:



Checking condition or Favourite's Trigger Expression dateString is not equal to now_time_datestr.
17:19:54Selection: Phoenix Passion, initial expr.: dateString, intermediate: 15/04/2024, final: 0.00185277.
My condition against this value with the current date is therefore always true which means I'm always detecting a date change.
Is this something I've done wrong ? I don't understand why the intermediate value is a string but the final value has changed to a floating point.
Trigger and log attached. Cheers in advance.
20
Hi
Try manually deleting the log files. See Item 3. here.
Pages: « 1 2 3 4 5 6 7 8 9 10 »
Please note, BetFair is seems to be currently OFFLINE