Support Board
Date/Time: Sun, 24 Nov 2024 12:09:22 +0000
very low precedence with incorrect calc order?
View Count: 164
| [2024-06-07 03:37:32] |
| User133994 - Posts: 80 |
|
Support, Good day. Great platform as always--thanks! I have a custom study DLL with VERY LOW PRECEDENCE set. This custom study depends on 10+ other studies some of which are also VERY LOW PRECEDENCE. When I install it on my chart at the very bottom of the list (already has >200 studies) it is assigned a calc precedence of 35? When I check the calc precedence of one of the study inputs to the DLL it has a calc order of 192. How can my custom study have calc order of 35 when a study input on that DLL has a calc order of 192? Yes, I've read this: Chart Studies: How Calculation Order of Studies Is Determined and yes, this is also set (because I do use an overlay): General Settings Window: Use Controlled Order Chart Updating (Global Settings >> General Settings >> Charts >> Charts) . And, yes, the reason I found this issue was because some of the data isn't correctly being updated when I have faster bars on the chart (i.e. less than 1 second for 3+ bars in a row)--even though the chart is displaying (I should say back-correcting) the correct information. Side note: when I 'duplicate' my custom DLL study, the calc precedence changes to 204 for the duplicated study, while keeping calc order of 35 for the original. 205 aligns more with what it should be. However, if I remove the 1st study and only use the duplicated study, I have issues with the custom study's GDI not working right...but that is for another thread. Sounds like a catch 22 scenario. Has anyone else experienced this and found a solution? Side note #2: The calc order of 35 only occurs when I install it with ID1 even though it is still at the bottom of the list. I reserve the ID1 for this study. Thanks in advance. |
| [2024-06-07 13:08:10] |
| User133994 - Posts: 80 |
|
Resolved... I don't know why it worked or what the problem was, but I did 3 things which apparently fixed it: 1) created a duplicate chart 2) removed most unused studies (likely >50) 3) removed unused inputs for my custom study DLL after these things apparently the issue is gone. hmmm... |
To post a message in this thread, you need to log in with your Sierra Chart account: