Version 6.3.2.0

There has been an update to MF Pro. Read here:

http://www.marketfeederpro.com/blog/18-03-update/

Please especially note the changes in the Auto-Greenup function and in the trigger protection procedure.

Oxa,

Thank you that's brilliant - I will try it tonight. 

Have you managed to test my suggestion here ?

http://community.marketfeederpro.com/troubleshooting-8/going-slowly-mad-!/


Alfaman

Alfaman, I have, and have already fixed it, as well as some other issues you reported.

This version keeps crashing on me. Had to reinstall the old version. Anyone else with problems?

Seems to happen when I want to spread profit in one of my triggers!!

Yes, Nick, unfortunately you are right and I'm glad you've reported it so soon. I've corrected version 6.3.2.

Hi OXA

Please dont take this as any sort of criticism.

I am just wondering, seeing as I have more than one lifetime license of MFPro, and as I am sure others do as well. Is it possible to be on some sort of mailing list advising of new releases along with the changes in said release.

The last release caused no end of problems for me the least being that I had to re-code all of my clients triggers as the coding algorithm had changed - would have been nice to have been given some warning on that.

secondly there has been so many crashes of the new version as already mentioned, along with it seemingly getting stuck and not deleting finished markets anymore. Also not updating the statement file even sometimes seeming to loose the info in the statement file.

All of which means that I havent been able to trust it to run unattended again and have now gone back to an earlier version.

I am sure you will fix all of these things of course and as I said it is not meant to be criticism, but if we wer on a mailing list perhaps we could have some early warning sometimes.

Cheers

Hi Turbo,

I'm sorry to hear all of that, and don't worry about the criticism, it should be accepted if it is constructive.
But before I answer to your suggestions, can you please specify:

- Are you referring to version 6.2.3 or 6.2.3.1 that was released yesterday, shortly after the Nick reported the problems on the forum?

- You are supposed to be getting a message telling you about the new version of the program after you have logged in. Does this message ever come up?

I’ve been using the latest version 6.2.3.1 released on the 19th. The auto update message does appear btw.
Left running last night checked this morning to find “Abnormal operation. Too many storage threads” or something similar. Memory usage was over 800mb. Clicked OK and  thought it was monitoring the markets again but it wasn’t downloading the list of bets.  Gone back to last stable version for now.

I like what you've done with the ladder.
Cheers

Left running last night checked this morning to find “Abnormal operation. Too many storage threads” or something similar.

How many markets did you have on your list, and at what refresh rate?

Just 2 markets @ 2 second refresh, running with excel.

Maddox, I don't believe this has to do with the newest version.

The error message (Thread creation error) indicates that the program can't open any more threads to process "slow operations", such as requests to the Internet or to Excel.

In the combination MF Pro + Excel the bottleneck is Excel, being too slow to pass the required info through the OLE channel at necessary speed.

This is a long-time problem, and it didn't appear after yesterday's update.

I agree that this isn’t a new problem but it’s happened once on both versions released on the 18th and 19th.  Using the latest stable version now on five markets @ 2 seconds refresh with no problems, as it’s been all month. I’ll give it another try and let you know.

Currently running both versions on two markets each @ 2 sec refresh. Same trigger and spreadsheet.

The memory usage for the new version is 180mb and rising. The old one is hovering at 27mb.  So it seems likely that the new version is going to crash soon.

Maddox, it looks like this version is unlucky, but anyway I have to make it work, so am trying to be constructive.
I've just identified the reason of that memory usage and uploaded the fixed file to the server.  You can try it or you can stick to the older version if you want.

Quick fix 6.3.2.1 has a problem with MINV and MAXV function.

In Version 6.2.3.1

MINV( -1, 2 ) =  -1
MAXV( -1, 2 ) =  -1   wrong !!!!

MINV( 2, -1 ) =  2  wrong !!!!
MAXV( 2, -1  ) =  -1 

It seems to me as if the result is always first parameter