indicator numerical value accuracy issue compared to other platforms

sodastodas

There is a difference in the indicator's values between cTrader and Tradingview for the same indicator when compared on each platform for Gold (XAUUSD) but not as much for Nasdaq 100 (#USNDAQ100) taking into consideration that the price differences for gold between each platform is negligible , as you can see in the following photos :
1- the value of the indicator = 0.0074 on ctrader for gold , but the value at the same candlestick on the same timeframe for gold on tradingview = 2.3646 which is a large difference for gold

2- the value of the indicator = 38.7609 on ctrader for NASDAQ100 , but the value at the same candlestick on the same timeframe for NASDAQ100 on tradingview = 39.5133 , which is a small difference for NASDAQ100

why is it different for gold but not for NASDAQ100 ? And how can i make the difference in gold as small as possible ?

This is the cTrader indicator code : 
`using System;
using cAlgo.API;
using cAlgo.API.Collections;
using cAlgo.API.Indicators;
using cAlgo.API.Internals;

namespace cAlgo
{
    [Indicator(AccessRights = AccessRights.None , ScalePrecision = 4)]
    public class bullbearpowerupdatedcode : Indicator
    {
        [Parameter(DefaultValue = 9)]
        public int Periods { get; set; }

        [Output("BBPhisto", LineColor = "Gray", PlotType = PlotType.Histogram)]
        public IndicatorDataSeries BBPhisto { get; set; }
        
        [Output("BBP Green histo", LineColor = "Green", PlotType = PlotType.Histogram)]
        public IndicatorDataSeries BBPGreenhisto { get; set; }
        
        [Output("BBP Red histo", LineColor = "Red", PlotType = PlotType.Histogram)]
        public IndicatorDataSeries BBPRedhisto { get; set; }
        
        private MovingAverage Hullopen;
        private MovingAverage HullHigh;
        private MovingAverage HullLow;
 
 
        protected override void Initialize()
        {

             Hullopen = Indicators.MovingAverage(Bars.OpenPrices, Periods, MovingAverageType.Hull);
             HullHigh = Indicators.MovingAverage(Bars.HighPrices, Periods, MovingAverageType.Hull);
             HullLow = Indicators.MovingAverage(Bars.LowPrices, Periods, MovingAverageType.Hull);
        }

        public override void Calculate(int index)
        {
     var bullpower = HullHigh.Result[index] - Hullopen.Result[index];
        var bearpower = HullLow.Result[index] - Hullopen.Result[index];

            BBPhisto[index] = bullpower + bearpower ; 

            if (BBPhisto[index] > 0)
            {
                BBPGreenhisto[index] = BBPhisto[index];
                BBPRedhisto[index] = 0;
            }
            else
            {
                BBPGreenhisto[index] = 0;
                BBPRedhisto[index] = BBPhisto[index];
        }
    }
}
}`

algoman

Even if the price is “negligibly” different, small variations in tick data or spread can cause compounded differences in some indicators (especially those relying on historical price patterns like RSI or Bollinger Bands). Gold is more sensitive to such discrepancies due to its volatility and pricing structure (often quoted to more decimal places).

Different Data Granularity

TradingView may use aggregated or synthetic feeds (e.g., OANDA, FXCM) for Gold, while cTrader uses your broker’s raw data feed. This affects how bars form, especially on lower timeframes like 1-minute or 5-minute charts.

Time Zones / Session Handling

If your indicator uses daily candles or is session-based, differences in session times or chart time zones (e.g., UTC in cTrader vs. New York time in TradingView) can impact results.

Symbol Mapping Issues

On TradingView, “XAUUSD” may point to various broker feeds, each with unique liquidity and tick data. In contrast, cTrader’s XAUUSD is tied to your broker’s feed. Even a small 0.01 difference over multiple candles can significantly affect indicators.

Why the Difference is Less for Nasdaq 100

Index CFDs like the Nasdaq 100 are more consistently priced across brokers and platforms.
They're less sensitive to minor spread or tick differences.
Typically use fewer decimal places, which reduces compounding errors in calculations.

How to Reduce the Difference

Match Timeframe and Price Source
Use the exact same chart timeframe and ensure both indicators use the same price source (e.g., Close, Typical).

Align Time Zones
Set your cTrader chart time zone to match TradingView’s (usually New York time for US markets).

Ensure Equal Historical Depth
Indicators like moving averages or RSI require a consistent number of historical bars. Load the same candle history on both platforms.

Use the Same Broker on Both Platforms
If TradingView supports your cTrader broker, use the same account feed for consistency.

Start with Simple Indicators for Comparison
Begin testing with basic indicators (like SMA(14)) to confirm raw data alignment before comparing more complex indicators.

I hope that helps, if you have additional questions, I suggest to reach out to the creators of the trading platforms, Spotware & Tradingview or your broker.