Support Board
Date/Time: Fri, 28 Aug 2026 22:44:01 +0000
Sierra Chart Version Changelog
View Count: 38
| [2026-08-28 17:04:00] |
| User263526 - Posts: 5 |
|
One of the best parts of Sierra Chart is its documentation, which can be downloaded and worked with locally. A question for the Sierra Chart developers: on the Versions page, you do not provide detailed descriptions of the regular updates and instead refer users to the documentation and its updates. However, it is quite difficult to determine what exactly changed in each specific version. So the question is very simple: are there any technical update logs, changelogs, or release logs available that would make it possible to understand what changed in each version, especially when something changes in the API for custom studies? |
| [2026-08-28 17:15:14] |
| John - SC Support - Posts: 47697 |
|
So the question is very simple: are there any technical update logs, changelogs, or release logs available that would make it possible to understand what changed in each version
The answer to this is "no". The only place that this information exists is when we update the What's New information at the following link: https://www.sierrachart.com/index.php?page=doc/Whats_New.php especially when something changes in the API for custom studies?
Generally, if there is something that is going to break functionality between releases, a notice is made. If not in the "What's New", then at least as a Sticky in the Support Board. For example, note the information at the following link for the changes from floats to doubles: Upcoming Development and Internal Number Precision Improvement Project Also, for ACSIL, you can look at the "sierrachart.h" file and note the "SC_DLL_VERSION" at the top of that file. When that changes, then there are changes to ACSIL. Most of the time, this is new variables or functions which are then added at the bottom of that file. For example, in the current release (2945) the SC_DLL_VERSION is 2941 and the most recent change was a new function that shows near the bottom of that file as: int32_t (SCDLLCALL* GetOrderAllocationToTradeAccounts)(int32_t ChartNumber) This means that a new function that would be called as sc.GetOrderAllocationToTradeAccounts(int32_t ChartNumber) has been added and it returns an int32_t result. 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: