Getestet #2 · observed signal comparison
DEPine and MT5: 16 signal differences in one month
I compared an owned SMA crossover example on OANDA:EURUSD H1 in TradingView and EURUSD H1 on HolaPrime-Server1 in MT5 for the full August 2026 history available in both feeds.
Check the rule sheet first →What the comparison found
Observed signal states matched on 491 of 507 shared hourly bars. Sixteen bars differed. This is not a general parity claim: the two feeds used different OHLC candles, and the mismatch log explains each affected bar.
Fixed rule and observed outputs
The rule was a strict SMA(3)/SMA(5) crossing on completed H1 bars. A bullish marker appears when the fast average crosses above the slow one; a bearish marker appears for the opposite crossing. TradingView showed 116 markers in its table view. A read-only MQL5 script exported 112 MT5 markers. I aligned the observed markers by UTC bar time without replacing either platform output with a local calculation.
Price and both sets of markers

Original platform captures and their dates
The TradingView chart capture is from a separate September sanity sample; the full August TradingView observations came from the 507-row table export below. The MT5 capture shows August. Neither image replaces the August CSV comparison.
Where the 16 bars differ
Twelve rows are six crossings that occurred one bar apart between the feeds. Four rows are two brief bearish-then-bullish crossings seen only on the TradingView feed. Small OHLC differences moved the averages across the strict threshold. The linked agreement table and discrepancy log show each bar, direction, close and SMA values.
What this does not show
This is one owned rule, one symbol, one timeframe and one calendar month. It does not establish parity for another script, broker, session or live bar. No order fills, P&L, equity curve, returns or future behaviour were compared. The first five TradingView bars lacked preceding warm-up history for the separate formula check; their observed markers still remain in the comparison.
The decision before a port
A buyer must decide whether acceptance requires identical input candles or permits a stated feed tolerance. A marker on a different bar can change the meaning of a rule even when the code follows the same formula.