EA Studio vs Every Tick Based on Real Ticks: how to avoid mismatches?

thanks, but by applying Max Spread = 50 (always with SL 50 pips and no TP), the EA studio result remain almost the same, as the Open Price mode test in MT5.

The real tick backtest improves, as you forecasted, BUT, the trades are very few and the profit is just +100$ in 2025 vs around +900$ in Open Price.

Now, the big question: is Eastudio backtest more accurate than MT5 Real Tick backtest? I hope so.

https://i.ibb.co/LHwH9B7/GBPCHF-M30-EAs-vs-Open-P-vs-Real-Ticks-Max-Spread-50.png

EA Studio vs Every Tick Based on Real Ticks: how to avoid mismatches?

Try the Max Spread protection: https://forexsb.com/forum/topic/9992/ma … acktester/

https://image-holder.forexsb.com/store/ea-studio-editor-max-spread-protection-thumb.png

Set Max Spread between 30 and 50 points. It will eliminate the overestimated backtest results and may even make previously losing strategies profitable.

EA Studio vs Every Tick Based on Real Ticks: how to avoid mismatches?

There's always something to learn. So, if I understand, the real tick of Metrader in this case is the real backtest. No ea studio, no the open price mode of MT5.

But, the backtest was not only on Sunday night or Monday morning, but every day of the week. So it seems that only partially the negative real tick backtest is due to the gap, given that you say "usually on Sunday evening or on Monday morning":

https://i.ibb.co/G4ZrPcLf/Ea-Studio-vs-Open-Price-vs-Real-Ticks.png

EA Studio vs Every Tick Based on Real Ticks: how to avoid mismatches?

The issue is not with the indicator but with the way MetaTrader stores the spread.
MetaTrader (like other platforms) averages the spread during the bar and provides this averaged value in the historical data.

This is problematic on bar opening after a gap (usually on Sunday evening or on Monday morning). The spread can be high for a few seconds or minutes, but then lower later. It results in a low average spread for the bar. However, when we trade, we open a position at the Bar open with a high spread, which may ruin the position.

I have an idea to catch such cases by artificially increasing the spreads of bars after a gap.
I'll gather information on real spreads and gaps, and see what the RealSpread/AverageSpread ratio is for the different symbols and time frames.

The EA Studio backtest works perfectly with the data we feed it.

I'm also considering an advanced data feed with two spreads per bar—one at bar open and one averaged.

...

The spread you set in the Symbol Settings is valid for market data without a real spread. (Data you may import from MetaTrader 4.)

EA Studio vs Every Tick Based on Real Ticks: how to avoid mismatches?

ooooooook.

I had viewn 20 points from Custom Settings, so not clear what it is 20 points at this point, if in fact I see from the chart that real spreads also on EaStudio jumps from 20 points to 140 points 
https://i.ibb.co/SwYQBQr6/AUDNZD-spread-in-custom-settings.png.

To recap: at the beginning you meant that, even with this so high real Spreads on EAstudio, some indicators (like Bollinger Bands) change those 140 points spreads into very low ones?

Hope to read soon good news of having this fixed ;-) Bollinger Bands is one of my preferred indicators.

You're saying that this is the only reason why there's mismatches among EaStudio backtest results and Mt5? Please it would be good to have a complete list of these indicators that have this issue, so that we can avoid to use them while they get fixed as you say you're working on that.

EA Studio - News and updates

Expert Advisor Studio v25.10.30 is uploaded.

The MT5 Expert Advisors and the MT5 Portfolio Experts use native MQL5 commands to collect news events from the MetaTrader terminal.

These commands are available only in MT5.

The MT4 experts still need to connect to the forexsb.com server to load news data. The news data is the same because I load it from MetaQuotes.

The reason for this update is to make it easier for you to set up an Expert Advisor. You don't need to allow connection to "https://forexsb.com" in the Expert's options. It also reduces the robots' reliance on native MQL functionality only.

It is important to note that the News time is the Server time. It may be different from your local time.

https://image-holder.forexsb.com/store/mt5-news-filter-activated-thumb.png

Trade Safe!

MQLGen - change log

MQLGen v0.10.30 Beta is uploaded.

Fixed the indicator chart redraw when scrolling with the Home key.

EA Studio vs Every Tick Based on Real Ticks: how to avoid mismatches?

EA Studio uses real spreads from the historical data.

You can check that in the Indicator Chart.

https://image-holder.forexsb.com/store/eas-real-spread-indicator-chart-thumb.png

EA Studio vs Every Tick Based on Real Ticks: how to avoid mismatches?

Spread of brokers data loaded on EA Studio should be aligned with real spreads of the same broker on Mt5. If it's not, it's not realistic market condition in my opinion.
Example: AUDNZD with Darwinex has default 20 points fixed spread on EaStudio.

On Darwinex MT5, right after midnight (00:04) until 1:00, spreads jumps from 25 points to 143 and more:
https://i.ibb.co/TBGFf18D/AUDNZD-spread.png

If there are brokers with same spread right after midnight, well good to know but are they on EA-Studio? Darwinex should not have 20 pips spread always instead on EAstudio, if it's confirmed that it jumps its spreads between 00:04 and 01:00 included.

EA Studio vs Every Tick Based on Real Ticks: how to avoid mismatches?

> set by default Trading Session time from 01:01 to for example 10 minutes before closing time?

This is very opinionated. There are many brokers with normal spreads around midnight.

> It's important to avoid misleading strategies and false expectations on EA Studio under fake market conditions

How to decide if market conditions are real or "fake".
EA Studio calculates strategies based on the exact market data and the given spreads.

We can have better Monte Carlo simulations or other analytical tests to detect dangerous situations, but I think the backtest should be as precise as possible.