Hull Moving Average MT5 — What Traders Usually Need Beyond the Default MA

Direct answer

When traders search for a Hull Moving Average in MT5, they usually do not just want another moving average line. They want something smoother than a fast EMA but quicker than a slower trend filter, without turning the chart into noise.

That matters because the HMA is only useful when the role is clear. If it is a trend filter, it should stay readable. If it is an entry trigger, it needs a much stricter workflow around confirmation and exits. Most bad HMA builds fail because the line is asked to do three jobs at once.

Where people usually get this wrong

The usual mistake is copying the formula, then assuming the line is automatically useful in live trading or on MT5 execution workflows.

• using the same HMA settings on every symbol and timeframe
• treating a slope change like a full trade system without other structure
• coding the line cleanly but never defining how it interacts with entries and stops
• forgetting that a custom MT5 HMA usually needs clearer testing than a built-in MA setup

Copyable example

This is the kind of base pattern I prefer to start from before adding more filters, styling, or automation layers.

// MQL5 skeleton for a Hull Moving Average style line
int OnInit()
{
    SetIndexBuffer(0, HullBuffer, INDICATOR_DATA);
    return(INIT_SUCCEEDED);
}

int OnCalculate(
    const int rates_total,
    const int prev_calculated,
    const datetime &time[],
    const double &open[],
    const double &high[],
    const double &low[],
    const double &close[],
    const long &tick_volume[],
    const long &volume[],
    const int &spread[]
)
{
    int period = 55;
    int half = period / 2;
    int sqrtPeriod = (int)MathSqrt(period);

    for(int i = 0; i < rates_total; i++)
    {
        double wmaHalf = iMA(NULL, 0, half, 0, MODE_LWMA, PRICE_CLOSE, i);
        double wmaFull = iMA(NULL, 0, period, 0, MODE_LWMA, PRICE_CLOSE, i);
        double raw = 2.0 * wmaHalf - wmaFull;
        HullBuffer[i] = iMAOnArray(RawBuffer, rates_total, sqrtPeriod, 0, MODE_LWMA, i);
        RawBuffer[i] = raw;
    }
    return(rates_total);
}

How I would handle it in a real build

In real projects, I define whether the HMA is a trend map, a pullback filter, or part of a crossover model before I write the rest of the logic. That keeps the MT5 side maintainable and makes later EA or alert work much easier to test.

What to read next

If this topic is part of a bigger TradingView or Pine Script workflow for you, these are the most useful follow-up guides on the site.

• What is an Expert Advisor (EA)? MT4 vs MT5
• Pine Script indicator to strategy best practices
• Pine Script Backtesting Guide

Frequently asked questions