You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Hmm... We both ran it in Build 6296. Interestingly, I ran it in an FX and you ran it in CME Futures. Confirmed. That is the issue
Sorry but I don't get it, how to reproduce this issue ?
Sorry but I don't get it, how to reproduce this issue ?
Did you test it on a real CME GCEZ26 Futures contract like I did? (See my 1st/upper chart image in Post #8).
I probably should've typed a better caption above that image instead of just jumping from a spot EURUSD chart image to a gold futures chart image─in retrospect, of course.🤔
Takeaway: When a unique tick size of an underlying CME Futures contract is not passed on to its corresponding custom chart, the price scale increments of the custom chart are improperly formatted. This thread jogged my memory. That is exactly what happened to me in the past. That was on CME NNQZ26 Futures having a tick size of 0.5.Did you test it on a real CME GCEZ26 Futures contract like I did? (See my 1st/upper chart image in Post #8).
I probably should've typed a better caption above that image instead of just jumping from a spot EURUSD chart image to a gold futures chart image─in retrospect, of course.🤔
Takeaway: When a unique tick size of an underlying CME Futures contract is not passed on to its corresponding custom chart, the price scale increments of the custom chart are improperly formatted. This thread jogged my memory. That is exactly what happened to me in the past. That was on CME NNQZ26 Futures having a tick size of 0.5.Using your code from #6, build 6314, I don't get any issue.
Using your code from #6, build 6314, I don't get any issue.
Interesting. My CME Futures broker-dealer's latest MT5 Release Build is 6230, and has been so for quite a while. In contrast thereto, my Metaquotes-direct latest Beta Build just updated to 6314, Although I'm not willing to use a Beta Build in my live CME Futures account (due to the broker-dealer's custom CME-MT5 gateway, etc.), perhaps the OP is willing to do so─the OP is already using Beta Build 6296 anyway.
(Truth be told, I run my own proprietary custom chart generator designed around 6230 without issue in 6230).
Interesting. My CME Futures broker-dealer's MT5 latest Release Build is 6230, and has been so for quite a while. In contrast thereto, my Metaquotes-direct latest Beta Build just updated to 6314, Although I'm not willing to use a Beta Build in my live CME Futures account (due to the broker-dealer's custom CME-MT5 gateway, etc.), perhaps the OP is willing to do so─the OP is already using Beta Build 6296 anyway.
You previously said you reproduced it with build 6296.
Forum on trading, automated trading systems and testing trading strategies
how to fix price cutting off on vertical scale?
Ryan L Johnson, 2026.11.05 19:43
Hmm... We both ran it in Build 6296. Interestingly, I ran it in an FX and you ran it in CME Futures. Confirmed. That is the issue:
In contrast thereto, the following Renko chart generator does not have that issue:
Therefore, both GoldSecondsMT5.mq5 and your code share the same issue in CME Futures while the fix exists somewhere in Stanislav Korotky's RenkoTicks package.
For whatever it's worth to you, the MT5-integrated AI Assistant could likely diagnose your code in a few seconds.
You previously said you reproduced it with build 6296.
That's where my aforementioned retroactive screenshot captions would've been edited-in, if that were possible:
Forum on trading, automated trading systems and testing trading strategies
how to fix price cutting off on vertical scale?
Ryan L Johnson, 2026.11.05 22:06
I probably should've typed a better caption above that image instead of just jumping from a spot EURUSD chart image to a gold futures chart image─in retrospect, of course.🤔
Just to recap:
That's where my aforementioned retroactive screenshot captions would've been edited-in, if that were possible:
Just to recap:
Ok but that doesn't matter, the issue is not clearly reproduced, as I said I tried all these builds.