Support Board
Date/Time: Thu, 27 Feb 2025 09:13:22 +0000
Post From: v2275 Issue - Posted in forum but not answered
| [2021-06-23 22:00:53] |
| Sierra_Chart Engineering - Posts: 18584 |
|
This is definitively not at all an issue with newer versions of Sierra Chart with what is described in post #1. The developer needs to resolve the problem. This definitively absolutely is not a Sierra Chart issue at all. There is nothing changed which would be causing a problem. Can SC support let me know what changes (ACSIL functions, etc...) have been made since v2146 that could break the last 4 to 5 historical bars of a custom moving average indicator.
Absolutely nothing. Although we do not know what the study is doing. Any relevant changes are documented here:https://www.sierrachart.com/index.php?page=doc/Whats_New.php However, changes which require a change to the code would cause compiler errors and it is just a simple change to resolve the error. How do you come to this conclusion?: It looks like you have made changes to the way real-time data is updated which seems to be affecting historical bars (which shouldn't happen).
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2021-06-23 23:35:29
|