FAQ

FAQ

These are the ten questions that come up most often — drawn from the kinds of confusion, fear, and misuse the indicator's architecture makes easy to fall into. Each answer aims to resolve the question directly, then points you to the relevant page for the full picture.

1. Why do the bands only update every N bars?

Because On Bar Close is on (the default), and the slot's timeframe is higher than your chart timeframe.

When On Bar Close is on, the bands reflect the last completed higher-timeframe candle. They do not update while the next HTF candle is building. On a 1-minute chart with a 60-minute slot, this means the bands update once per hour and sit flat for the 59 bars in between.

This is the stability guarantee, not a bug. The flat bands are confirmed values — what you see is what was true when the last HTF candle closed. If you need the bands to update mid-candle, you can turn On Bar Close off, but you should understand the tradeoff first.

Full explanation: MTF & Repainting

2. Why does the blended band not match what I see with the individual slots?

Most likely, a hidden slot is contributing to the blend.

The blended band includes every enabled slot with weight greater than zero — including slots whose plot is hidden. If you hid Slot 3's lines to reduce clutter but left it enabled with weight 33.3, it is still pulling the blend. The visible slots suggest one position, but the hidden slot shifts the average.

To check: open settings and look at all slots, not just the visible ones. Either set the hidden slot's weight to 0 (to exclude it from the blend) or disable the slot entirely.

The other possibility is unequal weights. The blend is averaging the raw upper, basis, and lower values from each contributing slot, so even equal weights will not always look like a hand-drawn midpoint between the envelopes. It reflects the actual plotted values, not a visual center line.

Full explanation: Visuals & Logic — Blended band behavior

3. If I hide a slot, does it still affect the blend?

Yes. Hiding a slot removes its lines from the chart. It does not remove it from the blend calculation. If the slot is enabled and has weight > 0, it contributes to the blended band exactly as if it were visible.

This is by design. It lets you run "background" slots that shape the blend without cluttering the chart. But it means you need to remember which hidden slots are active and contributing.

To confirm: show the hidden slot. The blend should not change (because the slot was contributing all along). Then set its weight to 0. The blend should shift — proving that visibility and blending are independent controls.

Related settings: Settings — Hide Plot

4. Can I use this indicator for backtesting?

You can use its values in backtesting or strategy work, but only if On Bar Close is on for every slot you reference.

With On Bar Close on, the band values on historical bars match what was visible during live trading. No future information is embedded in those indicator readings.

With On Bar Close off, the historical bars show the settled HTF value, not the provisional values that were visible mid-candle. Backtests under this setting overstate what was actually knowable at the time. Concretely: if the hourly candle closed with a sharp sell-off in the final ten minutes, the bands on historical bars reflect that sell-off for the entire hour — as if you knew it was coming. In real time, the bands were somewhere else for most of that hour. The backtest sees the settled version and credits you with knowledge you did not have.

The degree of overstatement depends on how volatile the HTF candles were — calm candles barely change, volatile candles can change significantly. There is no way to retroactively see the provisional values. TradingView does not store them. The only way to evaluate On Bar Close = false behavior is to watch it live.

Full explanation: MTF & Repainting and Limitations & Trust Boundaries

5. What happens if I set all weights to 0?

The blended band has no contributors. The weighted average produces zero for upper, basis, and lower. The blend effectively disappears — it may draw at the bottom of the chart or not draw meaningfully at all.

This is not a bug. If no slot is contributing weight, there is nothing to blend. Set at least one enabled slot's weight to a value greater than zero if you want the blend to function.

6. Why do the cross-ticker bands shift unexpectedly?

The cross-ticker bands are scaled by a close ratio between the chart symbol and the reference symbol. When that ratio changes — because one symbol moved while the other did not, or they moved in opposite directions — the scaling multiplier shifts, and the projected bands shift with it.

This means the cross-ticker bands can move even when the reference symbol's actual BB did not change. The movement comes from the mapping, not from the underlying structure.

The scaling works best when the two symbols have a relatively stable proportional relationship. It gets less reliable during sharp divergences, sector rotations, or when one symbol is in a very different regime than the other.

Full explanation: For the Geeks — Cross-ticker scaling

7. What is the difference between this and running 3 separate BB indicators?

Three separate BB indicators give you three independent envelopes. You can read them visually, compare them yourself, and form your own conclusions. That works. The question is whether it works well enough given what you are trying to do.

Axiom BB Pro adds three things separate indicators cannot provide:

1. The blended band. A weighted-average synthesis across all active slots, computed and drawn automatically. You would otherwise have to estimate this visually, which is imprecise and breaks down when you have more than two or three overlapping bands.

2. Per-slot repaint control. Each slot has its own On Bar Close setting. Standard TradingView BBs do not offer this because they are not designed for multi-timeframe use. If you run three separate BBs and want to apply them at higher timeframes, you have no built-in way to control the repaint behavior per instance.

3. Cross-ticker scaling. A standard BB cannot pull data from a different symbol and project it into chart price space. Axiom BB Pro can, with each slot independently configurable.

Beyond the features, there is a practical difference in how you work with the indicator day to day. Three separate BBs mean three separate settings panels, three separate indicator instances consuming chart resources, and three sets of settings to keep synchronized when you change MA type, length, or multiplier. A single integrated indicator keeps those slot settings in one place, which makes synchronized experiments easier when you are actively comparing configurations.

8. Why did the indicator throw an error when I changed the chart timeframe?

The indicator enforces a rule: every slot's timeframe must be greater than or equal to the chart timeframe. If you switch from a 1-minute chart to a 15-minute chart without adjusting your slots, any slot set to a timeframe below 15 minutes (like the default 5-minute Slot 1) violates this rule.

The indicator catches this at runtime and throws an error rather than producing incorrect results. The error message names the offending slot.

To fix: Open settings and change the offending slot's timeframe to a value at or above the new chart timeframe, or set it to empty ("") to default to the chart timeframe. Setting a slot to the chart timeframe means it always adapts automatically, but you lose the MTF layering for that slot.

9. Which MA type should I use for the basis?

There is no universal answer, and the fact that there are many options does not mean you need to explore all of them. The MA type changes the character of the basis — how quickly it responds, how smooth it is, and how it behaves during trend-to-chop transitions — and the right choice depends on what you are using the BB for.

• SMA (the default) gives equal weight to every bar in the lookback. It is the most intuitive starting point and produces the BB behavior most traders have built intuition around. Start here unless you have a specific reason not to.

• EMA weights recent bars more heavily, producing a basis that tracks price more closely. The bands will be tighter and more reactive. Useful when you want the BB to respond faster to recent moves, but the tradeoff is more frequent basis crosses and noisier band edges.

• ALMA can produce a smooth basis with reduced lag. It is a good choice if you find SMA too sluggish but EMA too reactive — but it introduces two additional parameters (offset and sigma) that change its character significantly.

• KAMA and FRAMA adapt their smoothing based on market conditions — faster during trends, slower during chop. They can produce a basis that holds steady during noise and responds quickly during directional moves, but the adaptation itself can be surprising if you are not used to it.

• Other types (Jurik, Laguerre, VAMA, WMA, VWMA, etc.) each have their own response characteristics. They are there for users who have specific, informed reasons to use them.

If you are not sure, use SMA. You can always switch later once you understand what you want the basis to do differently. Switching MA types without understanding the change means the bands will start responding in ways you did not anticipate — and that is harder to diagnose than it is to prevent.

Changing the MA type also activates the Power User parameters for that type. See Settings — Tier 3 for what those parameters do.

10. Do the alerts work in real time or on bar close?

On bar close. Every alert condition is gated by barstate.isConfirmed. The alert evaluates its condition only after the chart bar has fully closed and confirmed. If the condition is true mid-bar but false at the close, the alert does not fire. If the condition is false mid-bar but becomes true at the close, the alert fires.

This means you can trust that when an alert fires, the condition was actually true on a confirmed bar — not a provisional spike that reversed.

One nuance: the alerts evaluate on the chart timeframe's bar close, not on the slot's higher-timeframe bar close. On a 1-minute chart with a 60-minute slot, the condition is true on each confirmed 1-minute bar where it still holds. Repeated alerts are possible, depending on the TradingView alert frequency you choose.

Full explanation: Alerts