🔺 MT5 XARD - Simple Trend Following Trading System

raffus wrote: Wed Sep 30, 2026 6:23 pm dear @Pelle,
many time your Sema indi loses the dots on chart and don't update the situation on colours on dashboard.
see my red arrows on charts M15 and H1

I think is it a problem of recalculation after X seconds

Please can you solve my issue?
thanks a lot

**Subject / Title:** Update: XU SEMAPHORE-X (v2.14) – Fixed Disappearing Dots & MTF Dashboard Refresh Issue

Here is an update addressing the reported issue regarding missing dots on the chart and delayed/frozen MTF dashboard colors.

### What was fixed & improved in v2.14:

1. **Fixed Disappearing Dots / ZigZag State Sync:**
- Rebuilt the ZigZag calculation engine with a clean two-pass algorithm (Pass 1 for extremes + Pass 2 for alternating high/low cleanup).
- Removed unstable cached state variables that previously caused historical dots and arrows to disappear or get erased on bar shifts.

2. **Real-Time Intra-Candle Updates:**
- Removed the early exit on same-bar ticks. New highs and lows forming in real-time now immediately update the semaphore glyphs and current timeframe bias without waiting for the candle to close.

3. **Smooth MTF Dashboard Refresh via Timer:**
- Fixed the MTF update logic in `OnTimer()`. Multi-timeframe biases (M15, H1, H4) now recalculate smoothly every second. The dashboard colors will no longer freeze or wait for higher timeframe candles to complete.

4. **Multi-Timeframe ZigZag Accuracy:**
- Added full two-pass cleanup to `GetMTFBias()` so higher timeframe direction is consistently accurate and aligned with chart visuals.

5. **100% Native MQL5:**
- Clean native MT5 code, fully compatible with 64-bit MT5 builds (compiles with 0 errors / 0 warnings).

Pelle wrote: Wed Sep 30, 2026 10:18 pm **Subject / Title:** Update: XU SEMAPHORE-X (v2.14) – Fixed Disappearing Dots & MTF Dashboard Refresh Issue

Here is an update addressing the reported issue regarding missing dots on the chart and delayed/frozen MTF dashboard colors.

### What was fixed & improved in v2.14:

1. **Fixed Disappearing Dots / ZigZag State Sync:**
- Rebuilt the ZigZag calculation engine with a clean two-pass algorithm (Pass 1 for extremes + Pass 2 for alternating high/low cleanup).
- Removed unstable cached state variables that previously caused historical dots and arrows to disappear or get erased on bar shifts.

2. **Real-Time Intra-Candle Updates:**
- Removed the early exit on same-bar ticks. New highs and lows forming in real-time now immediately update the semaphore glyphs and current timeframe bias without waiting for the candle to close.

3. **Smooth MTF Dashboard Refresh via Timer:**
- Fixed the MTF update logic in `OnTimer()`. Multi-timeframe biases (M15, H1, H4) now recalculate smoothly every second. The dashboard colors will no longer freeze or wait for higher timeframe candles to complete.

4. **Multi-Timeframe ZigZag Accuracy:**
- Added full two-pass cleanup to `GetMTFBias()` so higher timeframe direction is consistently accurate and aligned with chart visuals.

5. **100% Native MQL5:**
- Clean native MT5 code, fully compatible with 64-bit MT5 builds (compiles with 0 errors / 0 warnings).

Hello Pelle
i have compiled the updated indi V_2.14 but attached on the charts doesn't show any Sema 4/3/2/1

please can you check why?
many thanks

The previous version actually works well for me—by toggling TF back and forth, which is something you really ought to do in good code.

I'm a vibe coder.
Try those

Pelle wrote: Thu Oct 01, 2026 1:02 am The previous version actually works well for me—by toggling TF back and forth, which is something you really ought to do in good code.

I'm a vibe coder.

XU SEMAPHORE-X.mq5XU SEMAPHORE-X_light.mq5

Try those

which difference between light and normal version?
PS both they work on chart.

thanks a lot mate

raffus wrote: Thu Oct 01, 2026 1:35 am which difference between light and normal version?
PS both they work on chart.

thanks a lot mate

The Light version is a lighter version of the previous version,
and the Normal version is the new version.

SOLESHOE wrote: Thu Oct 01, 2026 5:16 pmIt would be great to have a Scalp Stop option in the XARD EA which calls panic when SL is hit.

SOLESHOE, I would define the panic boundary before adding the switch. Does Scalp Stop mean A) close only this EA/symbol, or B) close every open position? Pending orders also need an explicit keep/cancel rule.

A useful dry-run case is: the stop is hit, the close is requested once, the next tick sees the same trigger, and no second close or fresh entry is submitted. If one close fails, it should remain visible as a failed action rather than being reported as complete. This is an acceptance case, not a claim about how the current XARD EA is coded.

Is the stop condition A) checked on each tick or B) only after a completed bar?