Topic: my experience with the demo
I have played with the demo now for several days and I'm quite impressed with the software but I have a few doubts.
I notice that it will save generated strategies into the collection even if the OOS fails.
It's disappointing to come back after a few hours, see all those beautiful charts in the repository, only to click it and watch the profit line drop like a rock when you load it and it shows the OOS results. Is there a way to have it only save the system if it passes the OOS testing?
I'm concerned that there are 2 different files for the indicators. It is my understanding that the software uses the .cs within FSB to find the strategies, but then uses the .mqh for the exported EA. The problem with this is it's possible that the code in the .mqh has bugs or doesn't work the same as the .cs. I think this might be why sometimes when I backtest in MT5 the results don't match what FSB shows. Sometimes it does, sometimes it doesn't. Either way I think having 2 separate codes can cause problems. I think there needs to be a way for the software to generate the .mqh from the .cs somehow. For example there is a new indicator called pivot points multi. I came up with a winning strategy in FSB, but then when I tried to export it to .mq5 it said the indicator was missing. That was confusing because how can it be missing if it used it already. But i realized that meant there wasn't a matching .mqh. What is the point of putting a new .cs indicator without the .mqh?
I realize if you export the systems but forgot to save the .xml you can never load that back into FSB ever again, at least that's how it appears. This also is not good.
I think the fact that this software uses .xml, .cs and .mqh is very confusing and causes too many problems. Or if it must be this way, include a tool that can generate the needed files. For example generate the .mqh from the .cs (and vice versa), generate the .xml from the .mq5 etc.
Lastly, do the generated EAs have to be so huge? they take forever to backtest within MT5 itself. It would be nice not to have to do that, but as I said earlier, sometimes when I backtest in MT5 a profitable system in FSB can tank and lose badly in backtesting in MT5 which can be dangerous. The exported .mq5 is thousands of lines of code, is all that really necessary?
I am new so maybe I am misunderstanding, but this is how it seems to be. Quite often developers focus so much on the technical aspects of the software that they forget the user experience part which is very important, because that's the part that gets people to buy your software. You could have the most technically advanced software in the world, but if the users find it too frustrating to work with it will not sell as good as it should. I have worked in the software industry at a gaming company and at microsoft so I know what I'm talking about.
I believe it should just all be in .mqh and things would be much simpler.
Thanks for your time.