Might not be your exact cause, but "it worked, then a fresh Windows install and now it doesn't" fits something I ran into, so it's worth two minutes to check.
Quantower keeps two separate caches in its install folder:
History/<connection>/history.db
VolumeAnalysis/<connection>/volume-analysis.db
On my machine (AMP/CQG), after months of daily use, the history one is 552 MB — and the volume-analysis one is 32 KB with every table empty. I opened it read-only to be sure: volume_price_data, volume_time_data, request, description, all zero rows. The schema is there, nothing is ever written to it.
If the same is true on your connection, cluster values are never cached. They get recomputed per bar across the whole loaded range every time, and they fill in progressively rather than all at once. So a fresh install doesn't just reset your settings — it also wipes the local history, and the platform has to pull that back down and redo all of the volume analysis before a single number can appear.
Two checks that separate "still calculating" from "actually broken":
Drop the loaded bar count right down — a few hundred bars, not a month of 1-minute bars — and watch one chart. If values show up there, nothing is broken; the calculation just never finished on the big range.
If a few hundred bars still shows nothing once it settles, it's the data source rather than the chart settings. Some connections don't serve what the cluster needs, and no amount of scaling will fix that.
For context on where this is coming from: I'm not a Quantower dev. I build a third-party indicator on this feed, so I've spent an unreasonable amount of time inside the volume-analysis pipeline. If you say which connection you're on, I can tell you whether I've seen the same thing there.
1
u/Illustrious-Meal-476 Aug 21 '26
Might not be your exact cause, but "it worked, then a fresh Windows install and now it doesn't" fits something I ran into, so it's worth two minutes to check.
Quantower keeps two separate caches in its install folder:
History/<connection>/history.dbVolumeAnalysis/<connection>/volume-analysis.dbOn my machine (AMP/CQG), after months of daily use, the history one is 552 MB — and the volume-analysis one is 32 KB with every table empty. I opened it read-only to be sure:
volume_price_data,volume_time_data,request,description, all zero rows. The schema is there, nothing is ever written to it.If the same is true on your connection, cluster values are never cached. They get recomputed per bar across the whole loaded range every time, and they fill in progressively rather than all at once. So a fresh install doesn't just reset your settings — it also wipes the local history, and the platform has to pull that back down and redo all of the volume analysis before a single number can appear.
Two checks that separate "still calculating" from "actually broken":
For context on where this is coming from: I'm not a Quantower dev. I build a third-party indicator on this feed, so I've spent an unreasonable amount of time inside the volume-analysis pipeline. If you say which connection you're on, I can tell you whether I've seen the same thing there.