Posts made by chance4373

Another way to accomplish this is to have only one indicator be the "trigger" utilizing the cross criteria (x>, x<) and let the others "pass" if they are above or below your condition (ex. RSI > 50 AND fast MA x> slow MA).

I always look at Profit factor, profit, drawdown, and number of trades as a starting point to evaluating any of my EAs. Typically a high profit factor with low drawdown is more consistent at making money. However, profit factor and drawdown on their own can be misleading which is why I also look at the number of trades. You could have a really high profit factor and low drawdown but the EA only made a few trades. On the flip side, I personally would also not want my EA making too many trades unless it had a nearly straight equity curve. Just my personal opinion but everyone has their own preferences.

I know this has been talked about before but considering the recent update to the optimization criteria in Strategy Tester for MT5 I figured I'd share an easy way to add custom max criteria to your EAs.

Open MetaQuotes Language Editor (or hit F4) then click crtl + F to find the words "custom functions" in the code. Past your OnTester() function in this section under the header. For instance I prefer to optimize to max balance multiplied by max profit factor. The code I use looks like this:

Now all you need to do is select "custom max" as your optimization criteria and it will optimize your EA according to this function.

Re: onTester()

Something like this I assume

https://fxdreema.com/shared/Im5UPtphb

@zinho

You can speed this up considerably if you use the "Once per bar" block before the calculations. https://fxdreema.com/shared/jLyXfD5Ed

Here is what I would expect the zigzag to look like over the same time period.

I've run into an issue with the zigzag indicator in my EA's during backtests in MT5 where the indicator connects 2 highs or 2 lows. https://fxdreema.com/shared/XZ19rldze

The issue seems to be related to the value set for Depth. Depth values higher than 20 present this calculation error during the backtest. Does anyone know what could be causing this problem?

Many thanks in advance.