Support Board
Date/Time: Thu, 15 Oct 2026 17:16:47 +0000
Post From: Subject: Renko bar High/Low showing zero range during Replay (ACSIL, AutoLoop=1)
| [2026-08-31 13:55:35] |
| User936721 - Posts: 32 |
|
I think I may have found the actual mechanism, and I’d really appreciate your confirmation either way. My hypothesis: when a new Renko bar/brick is created, its High, Low, and Open all legitimately equal the single price that triggered it — so there genuinely is zero range at the instant a bar starts, in both Live and Replay. In live trading, by the time a study happens to read the current bar, real time has passed and several more ticks have usually already arrived, so it naturally shows a non-zero range by then. In Replay — especially Every Tick mode at 10x — I suspect my AutoLoop=1 study is being invoked on every single tick, so a large share of my sc.High[sc.Index] - sc.Low[sc.Index] reads are landing on bars that have only just been created, with one tick in them so far. If that’s right, it isn’t a Replay reconstruction issue at all — it’s simply that I’m sampling the currently-forming bar rather than the last completed one. Could you confirm whether that’s what’s happening? Specifically: 1. During Replay (Every Tick mode), is the AutoLoop=1 study callback invoked on every incoming tick, including ticks that don’t complete a bar? 2. If so, would checking sc.Index - 1 instead of sc.Index, or gating the read with sc.GetBarHasClosedStatus(sc.Index), be the correct/recommended way to only ever read fully-completed Renko bars? I tried a quick version of this myself: if (sc.GetBarHasClosedStatus(sc.Index) == BHCS_BAR_HAS_CLOSED) { Diff[sc.Index] = sc.High[sc.Index] - sc.Low[sc.Index]; } If that’s the right fix, brilliant — I just want to make sure I’m not missing something else, and that this is genuinely the expected/documented behaviour during Replay rather than a quirk specific to Renko charts. Thanks again for your help — really appreciate the support team digging into this |