Author Topic: Not greening up after crash  (Read 1599 times)

Tags:
  • All members
  • Posts: 28
Not greening up after crash
« on: 18 Oct 2015, 00:58 »
I'm loving MFP so far but seem to be getting quite a few crashes. Increasing refresh times has helped a bit but still crashing quite a bit.

I've noticed whilst trying the program in test mode that when I restart the program after a crash, even though markers are running and triggers are active, the program does not seem to be greening up (backing)  lay bets made before the crash (when the odds are appropriate).  

I'm guessing it's not recognising that triggers before the crash have run (ie the  "laying on the draw in match odds" block's "number of runs per selection is greater than 0).

If this is the case it's a bit concerning as it would make any kind of triggered trading risky if crashes occur.  I fear greenup triggers not activating if the program doesn't recognise that a previous trigger to place the original bet has run.

  • All members
  • Posts: 905
Re: Not greening up after crash
« Reply #1 on: 18 Oct 2015, 09:49 »
MFPro is not usually prone to crashing.  I have managed weeks of continuous use with no crashes.   There are usually external factors  that cause them.

1.  Betfair API faulty or down (like at present)
2.  Not running program feeder8.exe as administrator.
3.  The program not being allowed full access by firewall and anti-virus applications.
4.  Low system memory/processor reserves due to high refresh rates and/or non-essential data useage. 

There may be some settings in your profile that could be disabled.  Always load the program with a new profile if crashing is frequent.

  • All members
  • Posts: 28
Re: Not greening up after crash
« Reply #2 on: 18 Oct 2015, 12:24 »
I'm running the prog as administrator.  I've just now allowed it full access through Windows Firewall.  Also found a "Request data from betfair in zipped format" setting which I've unticked to reduce processor usage.  Hoping this may help.  

I do see some mentions of crashes here in the forum though and think it would be a good idea if the prog could keep text files of triggers activated and variable values so that if crashes do occur (or even accidental program closure) it can read them and pick back up from where it was when it restarts, and recognise which triggers have already run and values of any variable set etc prior to the crash.

  • Administrator
  • Posts: 8821
  • Gender: Female
*
Re: Not greening up after crash
« Reply #3 on: 18 Oct 2015, 12:40 »
Hi RunGeeGeeRun,

We believe the crashings will reduce after we use a different code protection software, which we'll testing at the moment.

It is true that if you restart the program or reload the triggers, their states will be reset. But you can use two workarounds for such situations:

1. For those constants that need to keep their values in between program sessions, you can set "remember last value" instead of "start with initial value".

2. You can prevent triggers from placing double bets by actually checking if there is already a bet in the market:

Market's Number of Matched/Unmatched Back/Lay bets is equal to 0

or use a similar condition that will return false if the trigger has already placed some bet. Of course it does not apply to the situations where you use conditions starting with "Trigger XY number of runs".
Always try your triggers in Test Mode before switching to real money!

Follow us on Twitter.

Join our WhatsApp chat!

Присоединяйтесь к официальному Telegram-каналу!

  • All members
  • Posts: 28
Re: Not greening up after crash
« Reply #4 on: 18 Oct 2015, 16:34 »
Thanks for those workaround tips, Oxa.  Great to know that there's likely to be a reduction in crashings too.

 

Please note, BetFair is seems to be currently OFFLINE