Support Board
Date/Time: Mon, 02 Nov 2026 23:01:29 +0000
Intermittent blank/disappearing value in the Bid Market Depth Pulling/Stacking column
View Count: 352
| [2026-09-17 11:41:45] |
| SidN313 - Posts: 8 |
|
Hi John, On NQZ6.CME, the Bid Market Depth Pulling/Stacking column values and volume bars intermittently go blank and reappear at price levels throughout the depth (not just the best bid), independent of best bid/ask price changes. Reproducible with no combine increment set. The Ask Market Depth Pulling/Stacking column on the same DOM does not show this exact behavior but a slightly different one. The volume bars on ask, shrink to a smaller size and then back to the correct size. Now I know this is very plausible as the size of the volume bars are relative, but I have noticed this even when the values/numbers on the ask pull/stack are not changing for some time The same behavior is not present on ES on the same install/version. I have attached an image for your reference, snapshot at that exact moment when the bid values disappear. Install version: 2931 Data/Trade service: Rithmic DTC |
 NQ DOM.PNG / V - Attached On 2026-09-17 11:35:32 UTC - Size: 107.3 KB - 65 views |
| [2026-09-17 15:20:42] |
| John - SC Support - Posts: 48388 |
|
We are aware of an issue with Rithmic Market Depth data related to changes that we have made to the DTC Protocol. Rithmic has been informed of this, and they have asked us questions, so we know they are working on it. We do not know their status on resolving it. You would need to ask them about this. But, we are a bit surprised that you are seeing this issue on version 2931, as it was our understanding that this particular version did not have this issue. The only thing we can suggest is to try a previous version until you find one that does not have this issue. We do not know when the issue was introduced, so we can not give you a specific version. Other customers have said that 2931 works for them, which is why we are surprised by this. Refer to the following for how to rollback to another version: Software Download: Full Control Rollback Procedure And, of course, we recommend contacting Rithmic and pushing them to resolve this so you can update to the latest release. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-09-17 16:47:18] |
| SidN313 - Posts: 8 |
|
Hi John, Thanks for your response. I will get in touch with Rithmic and push them. Just a follow up question I had raised another support request regarding market depth freeze. Here is the the link for the thread: Rithmic Market depth data streaming freeze Though that is also a market depth related issue but it is of a very different nature. And it affected all instruments across the board. From that thread's discussion I had rolled back to 2931. The market depth related issue (pulling/stacking) I have described in this thread is of a very different nature and is not seen across the board for all instruments. It is only specific to NQ. ES is working fine. Here I am receiving market depth. Just the pull stack is behaving wierdly So between these two threads, is the source of the issue same? The reason I am asking this is if it is not, then a rollback to a previous version may not fix it. Thank you for your patience |
| [2026-09-17 17:04:11] |
| John - SC Support - Posts: 48388 |
|
We really do not know the cause of the issue. It is possible that it is something related to the Rithmic implementation. We are not hearing of other issues with the Pulling/Stacking, which is why we would tend to believe it is a data related issue. Are you, by any chance, using a non-standard tick size for the chart that is having the issue? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-09-17 18:02:02] |
| SidN313 - Posts: 8 |
|
The tick size is the default. I think I have found out what is triggering it. I reconstructed the DOM from scratch. It is combine tick increment (Aplogies for the incorrect information I gave regarding this at the start). The moment I do combine tick increment this "blinking" issue starts with the pull stack. Otherwise, the pull stack works fine. Even a combine tick increment of 1 causes it to break. I have set: Apply combine increment in ticks to other market data columns >> Yes Chart DOM volume bars fill combined price level >> yes |
| [2026-09-17 18:10:37] |
| John - SC Support - Posts: 48388 |
|
It sounds like version 2931 happens to be in the middle of a couple of different issues. On the one hand, the Rithmic issue with the Market Depth is not occurring, but it sounds like it has an issue with the Pulling/Stacking calculations. There have been some changes to the Pulling/Stacking around that time, so most likely this is the issue. Normally, we would ask you to update to the latest release to ensure the issue is resolved, but you can not do that due to the Rithmic issue. We apologize for the situation, but unfortunately, until Rithmic solves their issue with the current releases, we just do not see a solution. Apart from changing to using our Denali data - but that requires that you have a live, funded, futures trading account. You can try going backwards through the releases and see if you can find one that doesn't have the issue. But we really do not know when exactly the changes occurred, so we can not give a definitive release to go to. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-09-17 18:52:09] |
| SidN313 - Posts: 8 |
|
No problem at all. I will be reaching out to Rithmic today. I can play around with different versions and see which one works best for me. Just want to check with you if going up or down multiple versions(ie reinstalling multiple times) is safe? Thanks again for taking out the time. |
| [2026-09-17 19:36:02] |
| John - SC Support - Posts: 48388 |
|
Generally it is not an issue to change versions. We did go through a period with the changes to the MDI windows (the windows attached to the main Sierra Chart window) that made switching between versions a little more difficult. But as long as you do not go too far down into the 2800s you should be fine (try to stay about 2880). And, worst case, you can always recover your chartbooks and configuration from the backups that are made. Refer to the following: Chartbooks (Workspaces): Accessing a Backup Chartbook File Resetting Sierra Chart to a Default State / Restoring Backup Global Configuration File: Restoring Backup Global Configuration File For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: