Pages:
Actions
  • #331 by mcbee on 20 Nov 2014
  • hi oxa
    sorry if this has been fixed/covered before.
    but i still connot use the trigger editor (only from within the bot), i have tried everything to get it to work on it's own, but failed, i have to have mfp open, then use the editor from the open mfp, so it takes more time to look at triggers.

    sorry again if it has been covered before.
    mcbee
  • #332 by Oxa (WellDoneSoft) on 20 Nov 2014
  • Program Update

    Bugfix

    - In some markets runners could be marked as "Loser" before the end of a market, or indeed even before its start. This mostly happened in Australian Greyhound and various championships' and tournaments' "Winner" markets. This would cause MF Pro crash.

    - Some markets' start time was displayed as year 1899, this was especially the case with Time Machine markets.

    - In Betting Interface bet persistence options would be available after a market turned In-Play.

    - When downloading big data chunks (e.g. long horse races in Time Machine or huge account statement) from inside a virtual machine, the program could crash.

    - Transaction limit (bets per hour) was being applied incorrectly.

    - Trigger Editor sometimes would not open on its own.

    Improvements

    - Added date to the statement file (along with the time of each transaction).

    - Time Machine: introduced an option to turn off some features when running the program in Fastest mode, in order to increase the speed.
  • #333 by mcbee on 20 Nov 2014
  • hi oxa
    thanks, the editor now works on it's own.


    mcbee
  • #334 by pfc on 20 Nov 2014
  • Oxa,

    Thksalot for the update MFP8008 that fixed the bug that McBee just mentioned and the bug re "loser" that continually crashed MFP8.

    Both bugs were driving me nuts.

    pfc
  • #335 by armarni on 20 Nov 2014
  • And thanks from me Oxa for putting the date back into the statements, you've just saved me a ton of extra work...much appreciated
  • #336 by Oxa (WellDoneSoft) on 20 Nov 2014
  • Glad to hear some positive feedbacks.

    armarni, I haven't identified the non-settling markets bug yet, but I'm working on it.
  • #337 by whitey86 on 20 Nov 2014
  • Hi,

    Thanks for the updates and great software.

    Since version 8 I've had a problem where if I'm running a "live" profile the bets are being settled correctly but when I run a "test" profile at the same time that bets on the same markets, those markets don't get settled. I have to manually click "Reset" hours after and then it knows which selection won. This is on the UK/IRE horse markets.

    I will see if this update fixes it - but it wasn't on your list of fixes so I doubt it will.

    Thanks,

    Whitey :)
  • #338 by armarni on 20 Nov 2014

  • Since version 8 I've had a problem where if I'm running a "live" profile the bets are being settled correctly but when I run a "test" profile at the same time that bets on the same markets, those markets don't get settled. I have to manually click "Reset" hours after and then it knows which selection won. This is on the UK/IRE horse markets.


    Hi Whitey

    This is the non settling markets bug that Oxa just mentioned.  She knows about it and is looking into what might be causing it.  

    When you click the reset button, most of the time the winners are revealed, but if they aren't then right click on the settle button (which the reset button will have changed to) and then pick the option to select winners manually.  You can then move the winners to the top of the display to correctly settle the market.

    It's a workaround until Oxa can work out what's happening.
  • #339 by whitey86 on 20 Nov 2014
  • Hi armarni,

    I didn't see Oxa's post until after I posted mine.

    I knew how to settle markets manually but thank you. I've worked out that if I press "Reset" only a few minutes after the race has finished it doesn't always know the winner. However if I leave it longer (I just wait until the end of the day) it knows all the winners.

    Thanks,

    Whitey
  • #340 by pcal72 on 20 Nov 2014
  • Hi Oxa

    After install new 08 update i have for the first time problems whith editor.

    pcal72


    PROBLEM REPORT RESUMED:

    Problem signature:
      Problem Event Name:   APPCRASH
      Application Name:   teditor.exe
      Application Version:   1.0.0.19
      Application Timestamp:   00000000
      Fault Module Name:   KERNELBASE.dll
      Fault Module Version:   6.1.7601.18409
      Fault Module Timestamp:   53159a86
      Exception Code:   0eedfade
      Exception Offset:   0000c42d
      OS Version:   6.1.7601.2.1.0.272.7
      Locale ID:   2057
      Additional Information 1:   f27c
      Additional Information 2:   f27c2442c40df7a86ab779921d0bd214
      Additional Information 3:   0649
      Additional Information 4:   0649d151ebb6a92e6f5f57bd0117e6e0

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt
  • #341 by Oxa (WellDoneSoft) on 20 Nov 2014
  • Hi pcal72,

    I need to ask you some questions to clarify the editor issue, so could you please copy this message to the support, we'll move it there.
  • #342 by pcal72 on 20 Nov 2014
  • Hi pcal72,

    I need to ask you some questions to clarify the editor issue, so could you please copy this message to the support, we'll move it there.


    Hi Oxa

    Already send a mail to support whith subject "Problems to editor.exe"

    Have at your entirely disposal.

    Thanks
    pcal72
  • #343 by Ace on 20 Nov 2014
  • After the update there's something very wrong with time machine running UK horseraces. For every race, horse 3 (index 3) has a constant lay price of 1.10 ?
  • #344 by mcbee on 21 Nov 2014
  • hi
    just cinfirming that index 3 has a fixed 1.10 in ALL markets, in the time machine.


    mcbee
  • #345 by Oxa (WellDoneSoft) on 21 Nov 2014
  • Update
    mcbe, Ace et al: yes, the Time Machine glitch was present and it was fixed yesterday thanks to our Russian speaking auditory.

    Also, thanks to pcal72, I've identified one more reason why teditor could not be launched independently.

    Both fixes were applied to MF Pro yesterday at night, so anyone who has downloaded ver. 8.0.0.8 before that time, please update now.
Pages:
Actions