Home >> Support Board

Support Board

Date/Time: Thu, 02 May 2024 19:16:32 +0000

How to Post a Message for Support

Out of bounds array error

View Count: 1216

[2020-05-01 08:40:30] #1 [Go To First Post]
User GDAC - Posts: 62
Appears to relate to the "Current Bid/Ask Lines" study. Software version: 2098 64-bit \| 2020-05-01 03:34:27.078 Primary Thread ID: 6848 \| 2020-05-01 03:34:27.078 Usage end date: 2020-06-15 \| 2020-05-01 03:34:27.078 Enabled for: Advanced Features 2. \| 2020-05-01 03:34:27.078 Enabled for: Sierra Chart Historical Data Service. \| 2020-05-01 03:34:27.078 Enabled for: Sierra Chart Real-Time Exchange Data Feed. \| 2020-05-01 03:34:27.078 Enabled for: Denali Real-Time Exchange Data Feed. \| 2020-05-01 03:34:27.078 Enabled for: Delayed Denali Real-Time Exchange Data Feed. \| 2020-05-01 03:34:27.078 Enabled for exchange: INDEXES_DATA_BARCHART \| 2020-05-01 03:34:27.078 Enabled for exchange: Eurex with Market Depth \| 2020-05-01 03:34:27.078 Enabled for exchange2: CBOT \| 2020-05-01 03:34:27.078 Received 1 data feed usernames. \| 2020-05-01 03:34:27.078 Allow Support for Sierra Chart Data Feeds is enabled. \| 2020-05-01 03:34:27.078 Current selected Data/Trading service: SC Data - All Services \| 2020-05-01 03:34:27.078 Custom symbol settings values: enabled \| 2020-05-01 03:34:27.078 Chart Update Interval: 500 \| 2020-05-01 03:34:27.078 Intraday Data Storage Time Unit: 0 \| 2020-05-01 03:34:27.078 Time Zone: -05:00:00 (CST-06CDT+01,M3.2.0/02:00,M11.1.0/02:00) \| 2020-05-01 03:34:27.078 2020-05-01 10:34:27 Local computer time \| 2020-05-01 03:34:27.078 2020-05-01 08:34:27 Local computer time in UTC \| 2020-05-01 03:34:27.078 2020-05-01 03:34:27 Local computer time in SC Time Zone \| 2020-05-01 03:34:27.078 2020-05-01 08:19:09 Server time in UTC \| 2020-05-01 03:34:27.078 Local computer UTC time and Server UTC time difference: 1 seconds. \| 2020-05-01 03:34:27.078 Program path: C:\SierraChart\ \| 2020-05-01 03:34:27.078 Data Files path: C:\SierraChart\Data\ \| 2020-05-01 03:34:27.078 OS Version Number: 10.0 \| 2020-05-01 03:34:27.078 Locale Setting: C \| 2020-05-01 03:34:27.078 Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Chart #4 \| Current Bid Ask Lines ID: 0 SubGraphData Array0: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Array message repeat count limit reached. \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Current Bid Ask Lines. SubGraphData Index: 1: Out of bounds array error at Index 3256 \| 2020-05-01 03:34:57.638 * Array message repeat count limit reached. \| 2020-05-01 03:34:57.638 *

[2020-05-01 18:18:31] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Can you provide chart #4, by following these instructions: Support Board Posting Information: Providing Chartbook with Only a Single Chart 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, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2020-05-01 18:35:32] #3 [Go To First Post]
User GDAC - Posts: 62
File attached


Attachment Deleted. Chart#4 for support.Cht - Attached On 2020-05-01 18:34:03 UTC - Size: 33.72 KB - 204 views

[2020-05-02 08:37:02] #4 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We have been unable to reproduce this. So not sure at this point what the problem is. 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, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2020-05-02 08:50:25] #5 [Go To First Post]
User GDAC - Posts: 62
I have several Study Collections I switch between during the day (via Control-bar shortcuts) and one of the constant studies in each collection is the current(bid/ask) line. When I switch study collections I get the error message above and then as the market continues the current (bid/ask) lines do not develop properly (they leave a 'footprint' of each tick after the next bar forms, rather than only updating in the forwarded projected fill space.I cannot reproduce it visually with Replay, it seems to happen only with live data.

[2020-05-02 08:51:24] #6 [Go To First Post]
User GDAC - Posts: 62
If it helps this began to happen after I updated to the latest pre release.

[2020-05-04 04:50:24] #7 [Go To First Post]
User GDAC - Posts: 62
I have attached images of the error with the current price and how it should look normally.


Current Price Normal.png / V - Attached On 2020-05-04 04:50:05 UTC - Size: 110.64 KB - 239 views Current Price Error.png / V - Attached On 2020-05-04 04:50:11 UTC - Size: 113.75 KB - 230 views

[2020-05-04 20:14:56] #8 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
The next release has some changes to that study which should resolve the problem but we are not sure about what the cause of the out of bounds array error is. That is not reproducible. 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, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2020-05-05 10:21:08] #9 [Go To First Post]
User GDAC - Posts: 62
When is the next release due? Are there any other steps we can take to address it? It is somewhat of an obstacle to ones focus. Thank you for your help.

[2020-05-05 10:54:39] #10 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
The new release will come out later this evening or tomorrow. 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, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2020-05-06 18:53:37] #11 [Go To First Post]
User GDAC - Posts: 62
I am now on Version 2100 64 bit and unfortunately the issue persists. It occurs on all charts with a current price indicator. The only solution I have found is to remove the current price indicator which is not ideal. I added an additional study yesterday (custom study) and it resulted in the same error message, so i do not believe it is related solely to the current price study. Are there any further steps we can take to resolve? Many thanks.

[2020-05-06 20:47:47] #12 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Are you referring to the out of bounds array error message? That message is harmless. And it only occurs displays so many times. It does not cause a problem. Yes we should try to resolve it if we can but we cannot reproduce it. Or what specifically is the issue? 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, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-05-06 20:48:22

[2020-05-06 20:52:32] #13 [Go To First Post]
User GDAC - Posts: 62
Yes I am referring to the out of bounds array message. Harmless or not every time I switch (frequently) study collections the error log pops up and as in my earlier post (with images attached) the current price line does not update correctly, leaving behind a footprint of where it has been rather then tracking the last price. What info can I share with you to help you resolve?

[2020-05-07 15:32:13] #14 [Go To First Post]
User GDAC - Posts: 62
I have reworked my charts today and whilst the issue isn't fixed it is no longer an obstruction, so you can leave this for a quieter day if necessary.

[2020-05-07 19:12:26] #15 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
The Chartbook you previously provided did not use the Current Price Line study. It was using the Current Bid Ask Lines study. That is the study that we worked on. However, we are not aware of any problem with Current Price Line. 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, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2020-05-07 19:34:16] #16 [Go To First Post]
User GDAC - Posts: 62
Both current price and current bid ask lines studies resulted in the same error message, hence I do not believe it is an issue with either study, but something else within Sierra. I also got the same error message with a non linear custom study.

[2020-05-08 20:26:14] #17 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Do you have this error message when not using any custom studies on the chart? 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, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2020-05-08 21:03:13] #18 [Go To First Post]
User GDAC - Posts: 62
Yes. the error began before any custom studies were added.

[2020-06-01 03:30:17] #19 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We apologize for the long delay with this. We were still not able to reproduce this. We have a similar report from another user and we now have determined the underlying reason for this problem. We are going to be putting out a new release in about an hour. And we also see, that the Message Log was being opened due to these errors. It should not have been. Not sure when an issue like that began. But we understand how that is an interference to have it opening up. 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, change to 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: