Support Board
Date/Time: Wed, 10 Sep 2025 05:24:30 +0000
Post From: Issues with v2712 vs v2700
| [2024-12-02 19:51:10] |
| John - SC Support - Posts: 41709 |
|
Hi John, thanks for the reply. I know you all are looking into all these things. You should add your Q1 answer to the What's New for v2713. Even with this documented there, I would guess many people will not know/discover this, nor realize that they are in such a predicament (especially if opening an older chart).
It is coming, the release was just put out this morning. Ideally, Sierra would detect this and post an alert/message that a chart cannot support the specified update time. Possibly auto-increasing the chart update time or something so an offending chart does not take down the whole thing..
We do not see issues when we use a lower Chart Update Interval, so we do not think that detecting a particular value would be a solution. How will this work if a given update time is fine 90% of the time, but other apps opening, loading, refreshing, put load on the system? Will Sierra just be slow (as expected I presume), but still WORK overall? Thinking the experience for short durations when cancelling/flattening a trade for example...will Sierra always be responsive to get the message, even with a mild delay?
There should not be any differences in how the software works now versus previously. We work hard to keep Sierra Chart as lean as possible so that system resources are available to do what needs to be done. If you worry about other apps causing issues with the responsiveness of your system, then we recommend using a computer to run Sierra Chart where you do not use any other applications. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |