Home >> Support Board

Support Board

Date/Time: Sat, 04 May 2024 21:07:40 +0000

How to Post a Message for Support

OpenGL support Now Ready for Initial Testing

View Count: 29271

[2020-02-05 22:14:42] #125 [Go To First Post]
AlexPereira - Posts: 197
his is what I have found w/ respect to OpenGL, besides all other things have reported here before: Moving cursor on RX580 will render all text background to the same text foreground color until cursor stops. is it the same I posted on #87 ?

[2020-02-05 22:41:15] #126 [Go To First Post]
Sierra_Chart Engineering - Posts: 14224
We have released version 2045 with a resolution to the Open GL problems reported. 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 10:54:30] #127 [Go To First Post]
Acro - Posts: 436
I do not believe 2045 solves the problem with transparent fill described above

[2020-02-06 18:17:22] #128 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We will check on this. 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-06 23:32:06] #129 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Version 2045 did not resolve the issue with transparency. That has still yet to be done. It only resolved the issue with Chart Drawing tools. 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-06 23:51:48] #130 [Go To First Post]
User316362 - Posts: 210
Nice 2045 resolves the flickering when drawing. Thanks! Date Time Of Last Edit: 2020-02-06 23:52:22

[2020-02-13 02:09:06] #131 [Go To First Post]
Tooth Fairy - Posts: 79
This isn't sticky anymore. Does that mean it's no longer a sore thumb sticking out because SC has no resource to support or it's just a plainly oversight mistake?

[2020-02-13 03:52:58] #132 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Well the thread is just very long and the OpenGL development is considered complete other than this transparency issue. And also some performance improvements we are working 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-13 03:56:47] #133 [Go To First Post]
Acro - Posts: 436
Thanks I think there's a lot of us waiting on the transparency issue as once that's solved there is a massive reduction in CPU usage going to OpenGL For me, my CPU would go from 5% to 1% for my main chartbook

[2020-02-13 09:39:25] #134 [Go To First Post]
User138602 - Posts: 169
Greetings, could it be that OpenGL usage needs alot more system Ram. I dont use OpenGL because my PC is running out of its 16GB RAM. Date Time Of Last Edit: 2020-02-13 09:39:39

[2020-02-13 11:14:05] #135 [Go To First Post]
User907968 - Posts: 802
Re: chart drawings vs. UI performance degradation 80 OpenGL support Now Ready for Initial Testing \| Post: 195152 102 OpenGL support Now Ready for Initial Testing \| Post: 198080 This issue still persists in v2048. Once the chart area becomes more complicated (either by multiple drawing tools or subgraphs) the GPU is regularly saturated during UI interaction such as scrolling, drawing or moving the 'Chart Values Tool' crosshair. In addition to the above, chartbooks containing multiple charts can cause the GPU usage to be consistently high, despite only one chart being visible. I guess this means my that current GPUs are not sufficient for using SC with openGL in any meaningful way. Can you make any recommendations for GPU specification?

[2020-02-13 16:47:12] #136 [Go To First Post]
User316362 - Posts: 210
Post #134....I don't know about recommendations, however, I'm using an "NVIDIA GeForce GTX 1660 Ti" graphics card and it works great As one example

[2020-02-13 17:43:10] #137 [Go To First Post]
User907968 - Posts: 802
@User316362 Thanks for the info, I will have a look.

[2020-02-22 23:40:54] #138 [Go To First Post]
nosast - Posts: 290
The latest version fixes the transparency bugs with OpenGL. I would love to use OpenGL for live version as the load on one core gets minimzed a lot and transfered to the GPU (especially noticable on a MDH chart). But the implementation still has some graphic issues that doesn't make it anywhere near visually pleasing. - Fonts - Lines (stair step on close) - Overlays - Volume bars I attached some examples and how it looks when OpenGL is not used.


OpenGL_SNAG_ 2020-02-22 - 23.50.37.png / V - Attached On 2020-02-22 23:40:27 UTC - Size: 1.78 KB - 403 views OpenGL_SNAG_ 2020-02-22 - 23.52.01.png / V - Attached On 2020-02-22 23:40:33 UTC - Size: 1.11 KB - 393 views OpenGL_SNAG_ 2020-02-22 - 23.52.21.png / V - Attached On 2020-02-22 23:40:46 UTC - Size: 14.02 KB - 372 views

[2020-02-22 23:41:42] #139 [Go To First Post]
nosast - Posts: 290
File attached


OpenGL_SNAG_ 2020-02-23 - 00.03.09.png / V - Attached On 2020-02-22 23:41:04 UTC - Size: 10.53 KB - 373 views OpenGL_SNAG_ 2020-02-23 - 00.03.29.png / V - Attached On 2020-02-22 23:41:12 UTC - Size: 2.07 KB - 386 views no_OpenGL_SNAG_ 2020-02-23 - 00.06.52.png / V - Attached On 2020-02-22 23:41:36 UTC - Size: 1.08 KB - 343 views

[2020-02-22 23:42:04] #140 [Go To First Post]
nosast - Posts: 290
File attached


no_OpenGL_SNAG_ 2020-02-23 - 00.07.28.png / V - Attached On 2020-02-22 23:41:51 UTC - Size: 8.94 KB - 372 views no_OpenGL_SNAG_ 2020-02-23 - 00.05.00.png / V - Attached On 2020-02-22 23:41:55 UTC - Size: 1.41 KB - 339 views no_OpenGL_SNAG_ 2020-02-23 - 00.05.56.png / V - Attached On 2020-02-22 23:41:58 UTC - Size: 16.18 KB - 361 views

[2020-02-26 12:26:58] #141 [Go To First Post]
User462086 - Posts: 188
This is great, thank you. One question for the SC developers: GDI objects from a custom study (rectangles in this case) aren't displayed when using OpenGL. Is this to be expected or perhaps a graphics card issue? Thanks Using SC 2057. Edit: For clarification, the 'GDIExample.cpp' also doesn't print to a fresh chartbook after a restart of SC. Date Time Of Last Edit: 2020-02-26 14:40:01

[2020-02-26 13:24:15] #142 [Go To First Post]
Marmany - Posts: 303
For info, tried out Open GL on v2054 with one instance of my Trading chartbook running with following results Open GL inactive CPU = 3.0 % Mem = 23.5 GPU = 0 Open GL active CPU = 0.9% Mem = 106 GPU = 80 With open GL active cursor movement became very slugish. Graphics cards are 2GB PNY QUADRO NVS 510 DisPort, I guess these are not up to handling the load from Open GL. As CPU never becomes overloaded I have de-activated open GL.

[2020-02-27 09:45:24] #143 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Using the GDI is not supported in a chart when using OpenGL. In regards to post #142, you need to run 2056 for the latest performance improvements with OpenGL. Update and test again. 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-27 10:04:31] #144 [Go To First Post]
caligola - Posts: 116
In SC 2014 I found that a Study Draw Style Line, Line Style Dot, Size 1 looks like a normal Line at zoom 0, I can see the dots only increasing the zoom. Please look at the following screenshots http://www.sierrachart.com/image.php?Image=1574505608700.png http://www.sierrachart.com/image.php?Image=1574505648177.png It seems that zoom applies also to dots, it should not as per the not-OpenGL SC thanks it still happens in 2057

[2020-02-27 11:12:22] #145 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
In regards to post #144 there cannot be any further improvement with that. We have previously said that. 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-27 11:43:48] #146 [Go To First Post]
Marmany - Posts: 303
Updated to 2057 with no apparent change in values that appear in Task Manager. All I can say is that when Open GL is activated the reported GPU value is increased from a steady 0% to a number fluctuating between 20% and 80%. My knowledge regarding computer hardware is too limited to know the significance of this. The CPU values are reduced as reported in #142. Also noticed that some text created with Drawing Tool appeared in normal font whereas bold font is specified in the study. Changing Global Font from Tahoma to Arial rectified this situation.

[2020-02-27 16:16:41] #147 [Go To First Post]
Tooth Fairy - Posts: 79
Anyone has segmentation fault drawing on OpenGL or it's just me? It only happens during very fast market many times. My version is 2057. It didn't happen in version 2054. I can live w/ transparent issue but definitely cannot w/ segmentation fault. I'm back to non OpenGL.

[2020-02-27 18:37:09] #148 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Regarding the segmentation fault we would like to see if anyone else is encountering this before we invest more time in it. 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-28 18:19:12] #149 [Go To First Post]
Tooth Fairy - Posts: 79
Just some info even in post 148, u said not investing time for now ... HD Server \| Server thread ending. Closing socket. \| Username: XXXXXXX \| Thread:4984 \| 2020-02-28 13:12:46.336 HD Server Manager \| Current server count=0 \| 2020-02-28 13:12:46.336 Loaded depth data records for CLJ20_FUT_NYMEX 2020-02-27 from 2020-02-26 19:00:00 to 2020-02-27 13:56:33. \| 2020-02-28 13:12:49.544 Loaded depth data records for CLJ20_FUT_NYMEX 2020-02-28 from 2020-02-27 20:53:23 to 2020-02-28 13:12:10. \| 2020-02-28 13:12:53.340 CLJ20_FUT_NYMEX [CV][M] 10 Sec #1 \| StartDateTimeForLoadingOrderFills: 00:00:00 \| 2020-02-28 13:12:53.351 CLJ20_FUT_NYMEX [CV][M] 10 Sec #2 \| Caught exception in c_Chart::DrawStudyGraph. \| 2020-02-28 13:15:02.566 *

[2020-03-02 21:44:51] #150 [Go To First Post]
User486568 - Posts: 10
I'm using a Quadro Pro P2000 card and have OpenGL turned on. I've been experiencing SC crashing lately with OpenGL on. Let me know if there is a crash report anywhere else that might be useful in diagnosing the issue. Here is the Windows 10 Event Viewer error message: Faulting application name: SierraChart_64.exe, version: 0.0.0.0, time stamp: 0x5e5655bd Faulting module name: SierraChart_64.exe, version: 0.0.0.0, time stamp: 0x5e5655bd Exception code: 0xc0000005 Fault offset: 0x0000000000e653a5 Faulting process id: 0x2eb8 Faulting application start time: 0x01d5f0c594a61d8b Faulting application path: C:\SierraChart\SierraChart_64.exe Faulting module path: C:\SierraChart\SierraChart_64.exe Report Id: b9db7b66-8060-46f1-80e6-cf3d90edef16 Faulting package full name: Faulting package-relative application ID: I've also had this message: Faulting application name: SierraChart_64.exe, version: 0.0.0.0, time stamp: 0x5e5655bd Faulting module name: ntdll.dll, version: 10.0.18362.657, time stamp: 0x64d10ee0 Exception code: 0xc0000005 Fault offset: 0x000000000003b900 Faulting process id: 0x50a0 Faulting application start time: 0x01d5f0bc4fb4a877 Faulting application path: C:\SierraChart\SierraChart_64.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: b828bc93-e92f-485c-a484-693715c6baaa Faulting package full name: Faulting package-relative application ID:

To post a message in this thread, you need to log in with your Sierra Chart account: