Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 05 May 2024 15:05:21 +0000
Toolbar, DOM, and Tabs button Freeze
View Count: 1418
| [2020-02-01 21:59:25] |
| Trader&Hunter - Posts: 129 |
|
yes everything I have under Control bar Commands is visible on Control Bar. Only ones I ave checked now is Sim mode. the last 3 items on control bar if for the dom
|
Attachment Deleted.  Capture.PNG / V - Attached On 2020-02-01 21:58:36 UTC - Size: 15.5 KB - 218 views |
| [2020-02-01 22:39:45] |
| Trader&Hunter - Posts: 129 |
|
c_ControlCollectionBase::OnLButtonDown | Point = (95, 7) | ItemID = 4002 | 2020-02-01 16:35:45.786 c_ControlCollectionBase::OnLButtonUp | Point = (95, 7) | ItemID = 4002 | 2020-02-01 16:35:45.874 Loading market depth data. | 2020-02-01 16:35:46.353 c_ControlCollectionBase::OnLButtonDown | Point = (502, 13) | ItemID = 3 | 2020-02-01 16:35:46.530 c_ControlCollectionBase::OnLButtonUp | Point = (503, 13) | ItemID = 3 | 2020-02-01 16:35:46.571 c_ControlCollectionBase::OnLButtonDown | Point = (542, 13) | ItemID = 5 | 2020-02-01 16:35:48.634 c_ControlCollectionBase::OnLButtonUp | Point = (542, 13) | ItemID = 5 | 2020-02-01 16:35:48.682 ESH0-CME #3 | StartDateTimeForLoadingOrderFills: 00:00:00 | 2020-02-01 16:35:48.844 Loaded depth data records for ESH0-CME 2020-01-30 from 2020-01-30 00:00:00 to 2020-01-30 17:59:59. | 2020-02-01 16:35:48.845 Loaded depth data records for ESH0-CME 2020-01-31 from 2020-01-30 19:38:07 to 2020-01-31 15:59:58. | 2020-02-01 16:35:52.303 ESH0-CME 10 Sec #1 | StartDateTimeForLoadingOrderFills: 00:00:00 | 2020-02-01 16:35:52.305 Using SC exchange feed2. Symbol: ES?#-CME | 2020-02-01 16:35:52.412 ESH0-CME 10 Sec #1 | Reloading chart. | 2020-02-01 16:35:52.412 ESH0-CME Delta 500v #4 | StartDateTimeForLoadingOrderFills: 00:00:00 | 2020-02-01 16:35:52.682 Loading market depth data. | 2020-02-01 16:35:53.617 Loaded depth data records for ESH0-CME 2020-01-30 from 2020-01-30 00:00:00 to 2020-01-30 17:59:59. | 2020-02-01 16:35:56.181 Loaded depth data records for ESH0-CME 2020-01-31 from 2020-01-30 19:38:07 to 2020-01-31 15:59:58. | 2020-02-01 16:35:59.173 ESH0-CME 10 Sec #1 | StartDateTimeForLoadingOrderFills: 00:00:00 | 2020-02-01 16:35:59.174 c_ControlCollectionBase::OnLButtonDown | Point = (64, 11) | ItemID = 2001 | 2020-02-01 16:37:00.093 c_ControlCollectionBase::OnLButtonUp | Point = (64, 11) | ItemID = 2001 | 2020-02-01 16:37:00.208 c_ControlCollectionBase::OnLButtonUp | Point = (64, 11) | ItemID = 2001 | 2020-02-01 16:37:00.371 c_ControlCollectionBase::OnLButtonDown | Point = (563, 8) | ItemID = 5 | 2020-02-01 16:37:02.235 c_ControlCollectionBase::OnLButtonUp | Point = (563, 8) | ItemID = 5 | 2020-02-01 16:37:02.314 c_ControlCollectionBase::OnLButtonDown | Point = (683, 12) | ItemID = 23 | 2020-02-01 16:37:04.299 c_ControlCollectionBase::OnLButtonUp | Point = (683, 12) | ItemID = 23 | 2020-02-01 16:37:04.370 ESH0-CME 10 Sec #1 | StartDateTimeForLoadingOrderFills: 00:00:00 | 2020-02-01 16:37:06.331 ESH0-CME 10 Sec #1 | StartDateTimeForLoadingOrderFills: 00:00:00 | 2020-02-01 16:37:07.587 c_ControlCollectionBase::OnLButtonDown | Point = (863, 12) | ItemID = 95 | 2020-02-01 16:37:28.539 c_ControlCollectionBase::OnLButtonUp | Point = (863, 12) | ItemID = 95 | 2020-02-01 16:37:28.690 ESH0-CME 10 Sec #1 | StartDateTimeForLoadingOrderFills: 00:00:00 | 2020-02-01 16:37:48.326 c_ControlCollectionBase::OnLButtonDown | Point = (552, 6) | ItemID = 5 | 2020-02-01 16:39:11.751 c_ControlCollectionBase::OnLButtonUp | Point = (552, 6) | ItemID = 5 | 2020-02-01 16:39:11.860 c_ControlCollectionBase::OnLButtonDown | Point = (464, 2) | ItemID = -1 | 2020-02-01 16:39:13.330 c_ControlCollectionBase::OnLButtonDown | Point = (464, -7) | ItemID = -1 | 2020-02-01 16:39:13.722 c_ControlCollectionBase::OnLButtonDown | Point = (460, -35) | ItemID = -1 | 2020-02-01 16:39:16.258 c_ControlCollectionBase::OnLButtonDown | Point = (573, -44) | ItemID = -1 | 2020-02-01 16:39:16.637 c_ControlCollectionBase::OnLButtonDown | Point = (570, 1003) | ItemID = -1 | 2020-02-01 16:39:17.787 Date Time Of Last Edit: 2020-02-02 14:09:53
|
| [2020-02-02 03:12:00] |
| Trader&Hunter - Posts: 129 |
|
c_ControlCollectionBase::OnLButtonDown | Point = (524, 7) | ItemID = -1 | 2020-02-01 21:11:03.532 c_ControlCollectionBase::OnLButtonUp | Point = (525, 10) | ItemID = -1 | 2020-02-01 21:11:03.572 c_ControlCollectionBase::OnLButtonDown | Point = (568, 0) | ItemID = -1 | 2020-02-01 21:11:03.932 c_ControlCollectionBase::OnLButtonDown | Point = (580, -5) | ItemID = -1 | 2020-02-01 21:11:04.348 c_ControlCollectionBase::OnLButtonDown | Point = (581, -9) | ItemID = -1 | 2020-02-01 21:11:04.724 c_ControlCollectionBase::OnLButtonDown | Point = (546, -6) | ItemID = -1 | 2020-02-01 21:11:06.884 c_ControlCollectionBase::OnLButtonDown | Point = (593, -33) | ItemID = -1 | 2020-02-01 21:11:07.525 c_ControlCollectionBase::OnLButtonUp | Point = (594, -33) | ItemID = -1 | 2020-02-01 21:11:07.652 Date Time Of Last Edit: 2020-02-02 06:02:46
|
| [2020-02-02 06:02:31] |
| |
|
We only need to see the last 20 lines or so from the Message Log not the entire logs. If you could edit your posts to show only those control bar lines that would be appreciated (We are doing the last one now). And we have enough information right now. However, we would like to do a remote assistance session with you to do our own observations. 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-02-02 06:03:18
|
| [2020-02-02 14:10:11] |
| Trader&Hunter - Posts: 129 |
|
Ok, I am available anytime.
|
| [2020-02-03 16:40:18] |
| Trader&Hunter - Posts: 129 |
|
c_ControlCollectionBase::OnLButtonUp | Point = (606, 2) | ItemID = 2009 | 2020-02-03 10:36:55.618 c_ControlCollectionBase::OnLButtonDown | Point = (1866, 12) | ItemID = 1120 | 2020-02-03 10:37:43.507 c_ControlCollectionBase::OnLButtonUp | Point = (1866, 12) | ItemID = 1120 | 2020-02-03 10:37:43.532 c_ControlCollectionBase::OnLButtonDown | Point = (1834, 16) | ItemID = 59 | 2020-02-03 10:37:44.089 c_ControlCollectionBase::OnLButtonUp | Point = (1834, 16) | ItemID = 59 | 2020-02-03 10:37:44.089 c_ControlCollectionBase::OnLButtonDown | Point = (476, 12) | ItemID = 2007 | 2020-02-03 10:37:46.384 c_ControlCollectionBase::OnLButtonUp | Point = (476, 12) | ItemID = 2007 | 2020-02-03 10:37:46.505 c_ControlCollectionBase::OnLButtonDown | Point = (635, 14) | ItemID = -1 | 2020-02-03 10:37:50.502 c_ControlCollectionBase::OnLButtonDown | Point = (630, 16) | ItemID = -1 | 2020-02-03 10:37:50.934 c_ControlCollectionBase::OnLButtonDown | Point = (201, -939) | ItemID = -1 | 2020-02-03 10:37:52.170 c_ControlCollectionBase::OnLButtonDown | Point = (189, -937) | ItemID = -1 | 2020-02-03 10:37:54.249 c_ControlCollectionBase::OnLButtonDown | Point = (16, -940) | ItemID = -1 | 2020-02-03 10:37:55.790 c_ControlCollectionBase::OnLButtonDown | Point = (193, -933) | ItemID = -1 | 2020-02-03 10:37:56.592 c_ControlCollectionBase::OnLButtonDown | Point = (197, -937) | ItemID = -1 | 2020-02-03 10:38:00.080 c_ControlCollectionBase::OnLButtonDown | Point = (197, -937) | ItemID = -1 | 2020-02-03 10:38:02.017 c_ControlCollectionBase::OnLButtonDown | Point = (21, -933) | ItemID = -1 | 2020-02-03 10:38:04.942 c_ControlCollectionBase::OnLButtonDown | Point = (17, -978) | ItemID = -1 | 2020-02-03 10:38:05.546 c_ControlCollectionBase::OnLButtonDown | Point = (93, -1016) | ItemID = -1 | 2020-02-03 10:38:06.608 c_ControlCollectionBase::OnLButtonDown | Point = (1729, -390) | ItemID = -1 | 2020-02-03 10:38:09.396 c_ControlCollectionBase::OnLButtonDown | Point = (1729, -390) | ItemID = -1 | 2020-02-03 10:38:09.706 c_ControlCollectionBase::OnLButtonDown | Point = (1670, -988) | ItemID = -1 | 2020-02-03 10:38:11.492 c_ControlCollectionBase::OnLButtonDown | Point = (1876, 10) | ItemID = 1120 | 2020-02-03 10:38:16.156 c_ControlCollectionBase::OnLButtonUp | Point = (1876, 10) | ItemID = 1120 | 2020-02-03 10:38:16.303 |
| [2020-02-03 22:54:44] |
| |
|
We think this users problem is now resolved. We did a remote assistance session. We found that the chart update intervals were very low , sub 50 ms for many charts causing a heavy load on the primary thread and apparently the Windows message queue is just simply overflowing and there are dropped messages and the user interface becomes nonresponsive. And apparently this also causes a problem with coordinates that the operating system passes to Sierra Chart event messages. They are simply wrong at times. The user will report back tomorrow and let us know if the change resolved 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-02-03 22:54:57
|
| [2020-02-04 21:00:45] |
| Trader&Hunter - Posts: 129 |
|
Same issue today. Not sure what to do at this point.
|
| [2020-02-04 21:04:11] |
| |
|
Are you using a Chartbook other than that one ES Chartbook that we increased the chart update intervals on?
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-02-04 21:06:56] |
| Trader&Hunter - Posts: 129 |
|
Only ES chartbook. nothing else was opened.
|
| [2020-02-04 21:11:52] |
| |
|
Is the problem at least less ? If not, really only thing we can say is this is clearly an operating system level issue. We only have your report and you also said you know of some other users who have the same problem but we wonder if what they are experiencing is different. We do not have any other reports of this and in any case it is quite clear this is an operating system level 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-02-04 21:12:06
|
| [2020-02-04 21:13:38] |
| Trader&Hunter - Posts: 129 |
|
NO not really its been the same.
|
| [2020-02-04 21:25:32] |
| |
|
We want you to follow the instructions linked below and only use the main instance of Sierra Chart for trading or simple charts. And then use sub instances for the complex charts. Overview of Trading: Sierra Chart Configuration for Most Low Response Time Trading 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-02-04 21:25:57
|
| [2020-02-05 03:00:18] |
| Trader&Hunter - Posts: 129 |
|
That won't fix it. I had this issue before when I was using plain 15min chart with a dom. nothing else. no depth or anything
|
| [2020-02-05 14:11:19] |
| Trader&Hunter - Posts: 129 |
|
c_ControlCollectionBase::OnLButtonUp | Point = (1812, 17) | ItemID = 59 | 2020-02-05 08:06:45.996 c_ControlCollectionBase::OnLButtonDown | Point = (1738, 16) | ItemID = 751 | 2020-02-05 08:06:46.482 c_ControlCollectionBase::OnLButtonUp | Point = (1738, 16) | ItemID = 751 | 2020-02-05 08:06:46.482 c_ControlCollectionBase::OnLButtonDown | Point = (1880, 13) | ItemID = 1120 | 2020-02-05 08:07:40.198 c_ControlCollectionBase::OnLButtonUp | Point = (1880, 13) | ItemID = 1120 | 2020-02-05 08:07:40.260 c_ControlCollectionBase::OnLButtonDown | Point = (1802, 13) | ItemID = 59 | 2020-02-05 08:07:40.725 c_ControlCollectionBase::OnLButtonUp | Point = (1802, 13) | ItemID = 59 | 2020-02-05 08:07:40.868 c_ControlCollectionBase::OnLButtonDown | Point = (1757, 19) | ItemID = 59 | 2020-02-05 08:07:41.792 c_ControlCollectionBase::OnLButtonUp | Point = (1757, 19) | ItemID = 59 | 2020-02-05 08:07:41.870 c_ControlCollectionBase::OnLButtonDown | Point = (1726, 0) | ItemID = -1 | 2020-02-05 08:07:43.447 c_ControlCollectionBase::OnLButtonDown | Point = (1725, 588) | ItemID = -1 | 2020-02-05 08:07:45.396 c_ControlCollectionBase::OnLButtonDown | Point = (37, 951) | ItemID = -1 | 2020-02-05 08:09:21.585 c_ControlCollectionBase::OnLButtonDown | Point = (34, 962) | ItemID = -1 | 2020-02-05 08:09:23.413 c_ControlCollectionBase::OnLButtonDown | Point = (34, 962) | ItemID = -1 | 2020-02-05 08:09:25.202 c_ControlCollectionBase::OnLButtonDown | Point = (548, -40) | ItemID = -1 | 2020-02-05 08:09:27.182 c_ControlCollectionBase::OnLButtonDown | Point = (1716, 487) | ItemID = -1 | 2020-02-05 08:09:39.111 c_ControlCollectionBase::OnLButtonDown | Point = (607, 994) | ItemID = -1 | 2020-02-05 08:09:40.398 |
| [2020-02-05 18:48:31] |
| Sierra_Chart Engineering - Posts: 14234 |
|
There are two problems here. The coordinates are completely wrong when you have the problem and there is no Button Up event. There is just something wrong on your system that is causing this. We really do not know why you have this issue. If you could try another computer system that would be the best advice we have right now. 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 |
| [2020-02-06 13:18:12] |
| Trader&Hunter - Posts: 129 |
|
The only issue I see with that. I have no problem with anything else but in SC. No other platform or surfing the web. I can show you messages from another user that tells me the same thing.
|
| [2020-02-06 18:39:16] |
| |
|
The operating system is providing wrong coordinate data. That is quite clear. What Sierra Chart is logging is values straight from the operating system. And furthermore you are also having a problem even accessing the menu. And this is happening without any unusual load within Sierra Chart? When you have the problem check your Windows task manager and tell us the CPU usage of Sierra Chart. If you just simply have one chart open, without any studies, this is not going to cause hardly any load. The CPU usage of the Sierra Chart process should be at 0%. We have no other direct reports of a problem like this. Other users can show us the same messages but our response will be the same. Do you know what kind of video adapter the other user you are referring to is running? Not that it matters, we have no idea if it is related or not. We really do not know what we can do from our side. This is so clearly an operating system level issue. In the end it is clear this is something that is simply out of our control. Windows 10 is not a good operating system. It is very sad. 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-02-06 18:41:52
|
| [2020-02-06 19:00:41] |
| Trader&Hunter - Posts: 129 |
|
with a simple chart sierra is running at 3% cpu usuage. with my ES chartbook with market depth it is using 8% of cpu.i7-4790 cpu
|
| [2020-02-06 19:10:16] |
| |
|
With just one chart 3% is too much. We have about 8 charts open and we notice 0 to 1% with a 8 core system. Are you using the OpenGL option?: Graphics Settings: Use OpenGL for Chart Graphics (Global Settings >> Graphics Settings >> Other) Disable that option. 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-02-06 19:10:46
|
| [2020-02-06 19:15:01] |
| Trader&Hunter - Posts: 129 |
|
No.i am not using that option
|
| [2020-02-06 23:00:53] |
| |
|
We thought of a workaround which has a good chance of solving the problem with the Control Bar. We will release it tonight and then you can let us know if it resolves the problem with the Control Bar.
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-02-06 23:01:13
|
| [2020-02-07 02:35:19] |
| Sierra_Chart Engineering - Posts: 14234 |
|
We have released prerelease 2046. We want you to update with Help >> Download Prerelease. We think there is a better than 50% chance the problem is now resolved with the Control Bar, chart and Chartbook tabs. We have implemented a workaround which we think has a good chance of resolving the problem. Let us know. This will not solve the problem with the menus not reacting to when you click on them or with other buttons like on the Trade Window. You can access the menus by pressing the Alt key and then the letter that is underlined on the menu list you want to open and then when the menu displays, press the letter that is underlined for the command that you want. Make sure you continue to have Global Settings >> General Settings >> General 4 >> Control Bar Debug Logging enabled. This is necessary for the workaround we have implemented to actually get used. 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: 2020-02-07 02:37:06
|
| [2020-02-07 18:39:20] |
| Trader&Hunter - Posts: 129 |
|
This has been 100 times worse today. I could hardly do anything today
|
| [2020-02-07 18:55:59] |
| |
|
Ok we have been able to reproduce the problem. We will be working on the issue and see what is causing it and coming up with a solution. Disable Global Settings >> General Settings >> General 4 >> Control Bar Debug Logging.
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-02-07 19:02:32] |
| |
|
We think we know what the problem is related to and we will put out a new release later today.
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: