I appreciate your effort. But this is actually a kind of volume of the ticks and not the actual volume of the contracts that have been traded. The cTrader has 'tick volume' or simply put 'number of ticks'. One can take a position with 10 contracts at a given price. Another can take 0.1 position on the same price. In reality it means 10.1 volume contracts at that particular price. But cTrader sees that as a single tick, because all the contracts were at the same price. If the first person with 10 contracts on price x had taken position and second person 0.1 contract on price x+1 had taken position. Then the tick volume on first price (of 10 contracts) was 1 and tick volume on second price (of 0.1 contract) was also 1.
Because tick is a price change and has nothing to do with number of contracts at a specific price. Because cTrader only has the number of ticks and no volume of contracts, this indicator or any other that does anything with volume is misleading.

I appreciate your effort. But this is actually a kind of volume of the ticks and not the actual volume of the contracts that have been traded. The cTrader has 'tick volume' or simply put 'number of ticks'. One can take a position with 10 contracts at a given price. Another can take 0.1 position on the same price. In reality it means 10.1 volume contracts at that particular price. But cTrader sees that as a single tick, because all the contracts were at the same price. If the first person with 10 contracts on price x had taken position and second person 0.1 contract on price x+1 had taken position. Then the tick volume on first price (of 10 contracts) was 1 and tick volume on second price (of 0.1 contract) was also 1.
Because tick is a price change and has nothing to do with number of contracts at a specific price. Because cTrader only has the number of ticks and no volume of contracts, this indicator or any other that does anything with volume is misleading.

Hi,

Do you happen to know which formula cTrader uses for VIDYA? Because that is very different from this VMO.

This is amazing. I truly appreciate your work on Renko bars and everything else you do on development.

I wanted to extend the output properties with StartTime and EndTime of the higher Renko timeframe but the chart got really funny. All bars were flat at the bottom of the chart.

I hope I can find a way to fix that and report it back here.

By the way I would take the bar color out. That doesn't add much and actually gets in the way a bit and creates confusion.

I looked at the result and compared it with the minute bar volumes. Every random sample I took were wrong!

Several times I took a bar at a random Renko bar within a chart that took several minutes to form. Then I compared the total minute volumes with those of the Renko. I even omitted the first and last minute volumes and yet the volumes on the Heat map were less than (sometimes half) the minute volumes.

I appreciate the efforts of the co-developers who make these kinds of ideas available to others. But I do find it a pity that little or no checks are made on the correctness of the result.

First of all I would like to thank the developer of this indicator and for making the code available.

But .... a very important but ....

There is a big issue in this indicator. The higher timeframe dots do not repaint on the lower timeframe!
If you put an hourly timeframe of this indicator on the M15 chart, you will see that the dots of hourly are up and down on the previous M15 bars.

No matter what timeframe, during the formation of the last bar, every indicator should repaint on that last bar. For the same reason on the MTF version of every indicator, the indicator should repaint on the last bar of the higher timeframe on lower charts.

So in case of above example, all of the dots of the hourly supertrend should repaint on the M15 chart for that hour. Until the hourly bar is closed.

In short, do not use this indicator until the repaint issue is resolved.

How can this be used in a cBot?

This indicator does not calculate correctly on Renko or Range charts.
Probably because there is no predefined time on those charts. In those cases the opentime of the current minute bar should be used to do the calculation.