MT5 Backtest timeframe results differ from EA internal timeframe settings

[Ian Walsh]

When I set up an EA, I have specific timeframes that I want to be able to alter. When I switch timeframes in the backtest MT5 screen it gives me different results. Should it only give results based on the EA specifications?  Which one do I use?

[Eleni Anna Branou]

If the EA's inside timefame setting is coded correctly, you will not see different backtest results by changing the timeframe in the 'Settings' tab of the Strategy Tester.

Don't put 'Current' in the EA's timeframe settings, always configure your desired timeframe.

[Fernando Carreiro]

Ian Walsh: When I set up an EA, I have specific timeframes that I want to be able to alter. When I switch timeframes in the backtest MT5 screen it gives me different results. Should it only give results based on the EA specifications?  Which one do I use?

When asking a question, please explain in detail, and if relevant, also include screenshots, log output, example code, etc.

[Ian Walsh]

Eleni Anna Branou #:

If the EA's inside timefame setting is coded correctly, you will not see different backtest results by changing the timeframe in the 'Settings' tab of the Strategy Tester.

Don't put 'Current' in the EA's timeframe settings, always configure your desired timeframe.

I believe I set it up correctly in my EAs but when I switch the timeframe in the strategy tester, it gives different results.  I am posting pictures of the difference when I run the strategy drop down on a 4H vs Daily. I am also posting where you can see my DAILY is the strategy_1 in the inputs.

[Fernando Carreiro]

Ian Walsh #: I believe I set it up correctly in my EAs but when I switch the timeframe in the strategy tester, it gives different results.  I am posting pictures of the difference when I run the strategy drop down on a 4H vs Daily. I am also posting where you can see my DAILY is the strategy_1 in the inputs.

If your EA code is using "current period" for time-frame, then you will get different results. That is obvious!

The only way for an EA to not have different results on different time-frames, is if the EA uses an explicit time-frame reference when accessing OHLC bar data or indicator buffer data.

EDIT: I do see that the EA does have a time-frame parameter, but we have no way of knowing if that input is being properly applied in the code in possible cases of accessing OHLC bar data or indicator buffer data.

You have not shown your code, so we can only speculate.

[Conor Mcnamara]

Different timeframes are essentially different worlds when it comes to the current bars bars of price, as single-timeframe based indicators (set to current timeframe) are showing different trends on different timeframes. Different worlds -> different entries.

[Ian Walsh]

Fernando Carreiro #:

If your EA code is using "current period" for time-frame, then you will get different results. That is obvious!

The only way for an EA to not have different results on different time-frames, is if the EA uses an explicit time-frame reference when accessing OHLC bar data or indicator buffer data.

EDIT: I do see that the EA does have a time-frame parameter, but we have no way of knowing if that input is being properly applied in the code in possible cases of accessing OHLC bar data or indicator buffer data.

You have not shown your code, so we can only speculate.

Thanks. Code attached.

Attached executable file removed by moderator.

[Fernando Carreiro]

Ian Walsh #: Thanks. Code attached.

An executable file is not "Code". Source code is in the ".mq5" file, not a ".ex5" file.

[Ian Walsh]

Fernando Carreiro #:
An executable file is not "Code". Source code is in the ".mq5" file, not a ".ex5" file.

Let me know if this works.

[Fernando Carreiro]

Ian Walsh #: Let me know if this works.

That code was produced by a code generator, namely "fxDreema", not a human programmer. It produces low quality EAs with known bugs.

Either learn to code MQL5 properly yourself, or hire someone to code it for you.

Don't rely on code generators or A.I., because we will not be able to help you fix them.

Forum on trading, automated trading systems and testing trading strategies

Sma 14 based system (5 minutes)

William Roeder, 2025.03.14 18:50

ChatGPT (the worst), “Bots Builder”, “EA builder”, “EA Builder Pro”, EATree, “Etasoft forex generator”, “Forex Strategy Builder”, ForexEAdvisor (aka. ForexEAdvisor STRATEGY BUILDER, and Online Forex Expert Advisor Generator), ForexRobotAcademy.com, forexsb, “FX EA Builder”, fxDreema, Forex Generator, FxPro, “LP-MOBI”, Molanis, “Octa-FX Meta Editor”, Strategy Builder FX, “Strategy Quant”, “Visual Trader Studio”, “MQL5 Wizard”, etc., are all the same. You will get something quick, but then you will spend a much longer time trying to get it right, than if you learned the language up front, and then just wrote it.

Since you haven't learned MQL4/5, therefor there is no common language for us to communicate. If we tell you what you need, you can't code it. If we give you the code, you don't know how to integrate it into yours.

We are willing to HELP you when you post your attempt (using Code button) and state the nature of your problem, but we are not going to debug your hundreds of lines of code. You are essentially going to be on your own.

ChatGPT	Even it says do not use it for coding. *  Mixing MT4 and MT5 code together. Creating multiple OnCalculate/OnTick functions. OnCalculate returning a double. Filling buffers with zero in OnInit (they have no size yet). Setting buffer elements to zero but not setting Empty Value to correspond. Calling undefined functions. Calling MT4 functions in MT5 code. Sometimes, not using strict (MT4 code). Code that will not compile. Creating code outside of functions. *  Creating incomplete code. *  Initialization of Global variables with non-constants. *  Assigning a MT5 handle to a double or missing the buffer and bar indexes in a MT4 call. *  Useing MT4 Trade Functions without first selecting an order. *  Uses NULL in OrderSend (MT4). *
bot builder	Creating two OnInit() functions. *
EA builder	Counting up while closing multiple orders. Not useing time in new bar detection. Not adjusting for 4/5 digit brokers, TP/SL and slippage. *  Not checking return codes.
EATree	Uses objects on chart to save values — not persistent storage (files or GV+Flush.) No recovery (crash/power failure.)
ForexEAdvisor	Non-updateing global variables. Compilation errors. Not checking return codes. Not reporting errors.
FX EA Builder	Not checking return codes. Loosing open tickets on terminal restart. No recovery (crash/power failure.) Not adjusting stops for the spread. *  Using OrdersTotal directly. Using the old event handlers.