do the reports not show the error?

I will attempt to reproduce some as the day passes.

I had no idea you needed more

I will be glad to send a complete package when the errors appear

Thanks

I have another instance this morning wherein the optimizer went silly and the profit dropped by about 30 percent at the end of the run

Hello Dave,
I have also noticed that issue before. I'll try to solve the problem in the next update.
Thank you for the report.

In coming weeks, Popov will be making some revisions to the program.

We have to help him.

What we have to do is to report bugs.

Reason being is that the program is becoming more and more complex and he does not have time to be doing robust tests.

That is where we can be of great assistance.

Bug reports have to be submitted a certain way....

He needs to know what was happening before the crash, he needs pictures..... he needs complete details.... all of that so he can try to isolate the problem.

No sense reporting bugs without documentation as he does not have time to investigate unless he has specifics.

Please write a description and provide pics and as much information as possible.

This is not to do with requested program modifications, those can go on the 'wish list', this is to report things that are in the program and not functioning properly.

If we can do our part and fully document all the bugs that appear.... then we will be helping the development immensely and bringing new features closer.

Firstly, it's the magic number issue.  When I made some changes to my EA and re-export it, sometimes the magic number change (to a new default one) and sometimes it remain the same.  Please revert back to the past, whereby no new default each time we re-export, this isn't helpful at all, it's counter productive.

In the past, if I changed the TP, SL and BE and re-export and refresh it in MT4, (while the EA is already opened in the MT4 and running but no open trades yet), the new changes in take place (if I open the EA properties to check).  But now, if I made any changes, I have to replace the old EA on the chart, it's like I have to re-install my EA again.  That's fine if only a few.  But imagine when there is a new update, it means re setting up all my hundreds of EA over again (if I add in trailing features etc) or re-key in each magic number.

Secondly, Trailing Stop Limit isn't working properly (please take a look at 337015 EA for reference).

Thirdly, sometimes when I open the FSB programme, the "save" button is not highlighted for me to save the new changes I made to my EA.  I need to close and reopen the programme for it to work properly.  This issue is random so I can't re produce it because it just happened when I open the software without me doing any thing prior to it.

I have several minor issue fixed in my development release. However, I'm doing a rather deep overriding of the FSB code and cannot publish a public preview yet. Be sure I'm working every day on this project.

Your issue reports are very important.

Trade Safe!

As long a post contains vital info everything is good! Haven't had so much fun in this forum for a while, I'll clean this up after the dust has settled, I'm getting confused already at 4:30AM!

I received error massage “Overflow Error” in two EAs. When I sorted out Indicators one by one, I found that the erroneous one was OBOS MA Oscillator. I am attaching one of the strategies to help to pinpoint the problem. I think that this indicator is one of the build in, as I could not find this one in FSB Repository.

Leon

Hi Popov,

I downloaded the EA and tried to open the file via FSB and I immediately got the "Overflow Error" too.

FSB pop up a prompter for the error report to be sent.  I've attached my email and sent the error report.  Hope you check and see whether you can identify the bug via the report.

I tried several times and no errors.

This Strategy has four indicators including 2 custom ones. How you noted which of them causes the problem?
Can you leave only one indicator and reproduce the issue?

If you see the EmaPredictive has very strange periods with floating numbers. Is it possible this to be the source of the problem?

I should search it there. At least this bug must be fixed first.