Support Board
Date/Time: Tue, 23 Dec 2025 04:23:36 +0000
Open GL + Quadro Drivers later than 572.60 + Chart Trade Mode = chart black out glitches
View Count: 776
| [2025-11-02 16:13:42] |
| Mike456039 - Posts: 41 |
|
Windows 10 Quadro p4000 Nvidia Quadro driver 572.60 Open GL enabled Any version of SC, including the latest 2807 -everything works perfectly- If I try to upgrade my Nvidia drivers above 572.6, then I get glitchy charts with Open GL (blacking out bars and studies as I move the mouse), only with chart trading mode enabled. I had stayed at 572.6 (FEB2025), but I decided to try again, hoping it would improve. However, the problem persists when I go above 572.6. It's no big deal, and I can work around it (disable OpenGL on my trading instance or stick with 572.6). However, is it a known problem, something I can easily fix or something that Nvidia Quadro drivers introduced after 572.60? Attached images to show the problem (incidentally, I dont actually trade off these uploaded charts full of graphics, I use a separate clean instance - but that has the same problem if I use OPen GL) |
Private File Private File Attachment Deleted. |
| [2025-11-03 19:36:42] |
| Sierra_Chart Engineering - Posts: 21947 |
|
We want you to open a new chart. Without any studies or anything. Enable Trade >> Chart Trade Mode. Do you still see this issue when using OpenGL? We made one small change which may or may not make a difference and will be out in the next release. 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: 2025-11-03 20:16:52
|
| [2025-11-03 19:38:01] |
| Sierra_Chart Engineering - Posts: 21947 |
|
Go to Global Settings >> Graphics Settings >> Other. Enable Use Compatible OpenGL Profile. Restart Sierra Chart. See if you still have 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-11-04 11:31:15] |
| Mike456039 - Posts: 41 |
|
New chart> new chart book>no studies>chart trade mode enabled = problem remains (albeit it's harder to trigger the fault) New chart>new chart book>no studies>chart trade mode disabled = no problems Toggling the Compatible OpenGL Profile on or off and restarting makes no difference to the above. Further info: I can also replicate the problem on my existing charts without chart mode enabled if I resize a rectangle on the charts that have numerous studies, overlays/colour bar studies, and this happens (almost) every time I resize a rectangle. It is more challenging to replicate the same issue on the new single test chart, but with studies added, it can occur after 4-6 attempts to resize a rectangle. I'm unable to replicate the problem with the new single chart without studies, regardless of how many times I resize the rectangle. |
 Screenshot 2025-11-04 113030.jpg / V - Attached On 2025-11-04 11:30:50 UTC - Size: 119.66 KB - 69 views |
| [2025-11-14 18:49:44] |
| Sierra_Chart Engineering - Posts: 21947 |
|
Try the very latest prerelease of Sierra Chart and see if it makes any difference . We are not sure it will. Instructions: Software Download: Fast Update 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 |
| [2025-11-15 16:31:41] |
| Mike456039 - Posts: 41 |
|
Tried 2811 and have the same issues. Tried with and without "Use OpenGL compatible profile" And with and without "enabled OpenGL debug" It's easy for me to stay on 572.60; in fact, I do not need to upgrade graphic drivers atm for any reason other than to "have the latest driver" Do you know what changed after 572.60 to cause the problem, and therefore, is it likely to ever change in the future, either via Nvidia or SC? I'm more than happy to come back and try again in 6 months. However, I'm also happy to help and check any new releases over weekends if you'd like me to, but please dont spend time fixing on my behalf as everything works perfectly for me and I can stay on 572.60. |
| [2025-11-17 12:57:52] |
| Sébastien - Posts: 110 |
|
I had a similar problem recently. I have a RTX 2000 with the 573.57 drivers, and 2807 version. With OpenGL activated, the liquidity on my BID/ASK DOM columns were blinking black when I overed my mouse on the columns. Also, my CPU utilization was increasing more and more with time, until using 100% of CPU utilization for the allocated cores. Deactivating OpenGL fixed the problem completely. I'm going to update my my drivers to 581.80 to see if it makes any difference. Date Time Of Last Edit: 2025-11-17 12:58:59
|
| [2025-11-17 14:27:11] |
| Sébastien - Posts: 110 |
|
I updated to 581.80, no change. I opened a blank DOM, no studies. The Bid/Ask columns are still blinking with OpenGL activated, and my CPU usage goes through the roof after a few minutes. Same problem with with the compatible OpenGL setting activated. The only solution for now is to deactivate OpenGL. |
| [2025-11-18 13:33:35] |
| Sébastien - Posts: 110 |
|
Hello, I updated to 2812 and activated OpenGL Debug output. In the message log I spotted some errors at launch : 2025-11-18 08:10:56.748 | OpenGL enabled (NVIDIA Corporation/NVIDIA RTX 2000 Ada Generation Laptop GPU/PCIe/SSE2) 2025-11-18 08:11:13.452 | OpenGL CALLBACK: PERFORMANCE type = 33360 (API), severity = 37191, message = Program/shader state performance warning: Vertex shader in program 20 is being recompiled based on GL state. 2025-11-18 08:11:11.624 | OpenGL CALLBACK: ERROR type = 33356 (API), severity = 37190, message = GL_INVALID_VALUE error generated. Size and/or offset out of range. Let me know if I can do anything more to help you diagnose the problem. |
| Screenshot 2025-11-18 142609.png / V - Attached On 2025-11-18 13:32:06 UTC - Size: 621.93 KB - 39 views |
| [2025-11-19 04:52:05] |
| Sierra_Chart Engineering - Posts: 21947 |
|
This is helpful. We are looking this over.
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 |
| [2025-11-19 17:42:02] |
| Sierra_Chart Engineering - Posts: 21947 |
|
Regarding post #9 can we get from you the Chartbook that you are using that is causing those, Performance and Error messages. Instructions to attach: Support Board Posting Information: Attaching a File (Optional) It will be privately attached by default. As soon as we get it you can then delete 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-11-19 17:42:23
|
| [2025-11-19 19:02:02] |
| Sébastien - Posts: 110 |
|
A blank chartbook is enough to trigger the bug. I attached a chartbook with 3 DOMs, 30ms refresh rate, without any studies. Here are 2 videos of this chartbook, one with OPEN GL activated, the other with OPEN GL deactivated. https://www.youtube.com/watch?v=c1uQ-ZSyb6Y https://www.youtube.com/watch?v=FS0pGP56Y_M When OPEN GL is activated, you can see blinking black on the DOM when I overed my mouse on them. RAM utilization increasing slowly but steadily with time. After a few minutes only SierraChart use over 250MB. CPU utilization, same story. At startup it is normal, but it keeps increasing with time. Without OPEN GL no problem at all. SierraChart uses 26MB of ram :) |
 DOM OPENGL.Cht - Attached On 2025-11-19 18:50:51 UTC - Size: 10.73 KB - 20 views |
| [2025-11-19 19:12:44] |
| Sébastien - Posts: 110 |
|
I can confirm the chartbook I just sent triggers the same errors in the Message Log. I also tried in Safe Mode : same problem I also tried to deactivate "Run the program as an administrator" (I use it for the NTP server) : same problem I also tried to force SierraChart to run on my Intel Integrated Graphic, or on my Nvidia RTX 2000 : same problem on both. I also tried to deactivate the Intel Integrated Graphic in my BIOS, to fully render my screen on the Nvidia chip : same problem. Date Time Of Last Edit: 2025-11-19 19:44:11
|
| [2025-11-20 19:51:13] |
| Sierra_Chart Engineering - Posts: 21947 |
|
Thank you for this. We are putting out a new version today. We want to know to what extent the issues are resolved.
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 |
| [2025-11-22 15:48:28] |
| Sébastien - Posts: 110 |
|
Hello, I did some tests with the prerelease version 2813. I deactivated the Integrated Intel Graphics in my BIOS. My computer only use the RTX 2000. Here are the results : OpenGL activated, without "Use Compatible OpenGL Profile" : - Error at chartbook launch : 2025-11-22 10:02:55.223 | OpenGL CALLBACK: ERROR type = 33356 (API), severity = 37190, message = GL_INVALID_VALUE error generated. Size and/or offset out of range. - Error later during Replay Mode : 2025-11-22 10:04:38.446 | OpenGL CALLBACK: PERFORMANCE type = 33360 (API), severity = 37191, message = Program/shader state performance warning: Vertex shader in program 20 is being recompiled based on GL state. - CPU utilization increasing with time - RAM utilization increasing with time (+-1MB/s) - DOMs are still blinking black while I over my mouse over them. In summary, same problems as before. No change at all. OpenGL activated, with "Use Compatible OpenGL Profile" : - Error at chartbook launch : 2025-11-22 10:02:55.223 | OpenGL CALLBACK: ERROR type = 33356 (API), severity = 37190, message = GL_INVALID_VALUE error generated. Size and/or offset out of range. - No more "OpenGL CALLBACK : PERFORMANCE type" message. - CPU utilization very low and stable - RAM utilization constant and not increasing - DOMs aren't blinking black anymore In summary, no more problem. Except the error messages in the log, Sierrachart is perfectly functional. Thank you for your work ! |
| [2025-11-22 17:39:14] |
| Sierra_Chart Engineering - Posts: 21947 |
|
Thank you for the feedback, we will continue working 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-11-22 17:39:19
|
| [2025-11-22 22:40:29] |
| Sébastien - Posts: 110 |
|
Hold on ! I drew the wrong conclusions with my previous tests. Sorry about that. I just did some more testing and I might have found what exactly trigger this bug. It has nothing to do with "Use Compatible OpenGL Profile" activated or not. To trigger the bug : - OpenGL must be activated - Sierrachart must be allowed to use multiple CPU PHYSICAL cores when the program is started. With HyperThreading DEACTIVATED : - If I use a script to force SierraChart to use only 1 core (core 0) : no bug at all. Never. Whatever "Use Compatible OpenGL Profile" is set to. - If I use a script to force SierraChart to use more than 1 core (core 0 and 1 for example) : the bug happens 100% of the time. - If I simply launch Sierrachart.exe without using a script (SierraChart is allowed to use all the cores) : the bug happens 100% of the time. With HyperThreading ACTIVATED : - If I use a script to force SierraChart to use only 1 logical core (core 0) : no bug at all. Never. Whatever "Use Compatible OpenGL Profile" is set to. - If I use a script to force SierraChart to use only 2 logical cores from the same physical core (logical core 0 and 1 for example) : no bug at all. Never. Whatever "Use Compatible OpenGL Profile" is set to. - If I use a script to force SierraChart to use only 2 logical cores from two different physical cores (logical core 0 and 2 for example) : the bug happens 100% of the time. In summary, OpenGL is bugging when SierraChart is running on more than one physical CPU core at startup. If I start Sierrachart with a script allowing only 1 physical core, but once launched, I modify the CPU affinity with Task Manager to allow more cores to be use, there is no bug. Hopefully it will help. |
| [2025-11-22 22:49:16] |
| Sierra_Chart Engineering - Posts: 21947 |
|
Thank you for the additional information. This is helpful.
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 |
| [2025-11-30 12:26:22] |
| Mike456039 - Posts: 41 |
|
I tried 2813 with the latest Qudro drivers, the problem is still the same, compatible on/off. I have hyperthreading off in the BIOS and two cores for each install; 2813 made no difference for me. I set an install to a single core and restarted - this made no difference for me. I then allowed all cores after launch - this made no difference I then restarted with all cores - this made no difference Also deactivated Process Lasso, so no control over cores, and that made no difference. My bug is blacking out the screen when moving the cursor with the chart trade mode "on" Or with chart trade mode "off", then moving the cursor around does not cause the same prob, but moving a drawing does cause blacking out. Date Time Of Last Edit: 2025-11-30 12:33:19
|
| [2025-12-03 21:11:51] |
| Sierra_Chart Engineering - Posts: 21947 |
|
What we are going to do regarding this, is set up similar hardware and operating system in order to see why these issues are happening. Otherwise, we do not know.
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 |
| [2025-12-05 13:03:32] |
| Mike456039 - Posts: 41 |
|
I can try at the weekend again, update quadro drivers and test if re-enabling hyperthreading just in case it makes any difference, as other post suggested a connection with cores. As Ive said before, staying on older quadro drivers works just fine, (or latest and disabling Open GL), so not a bid deal for me personally |
| [2025-12-05 22:05:42] |
| Sébastien - Posts: 110 |
|
Same for me, I don't mind using SierraChart without OpenGL as my CPU is powerful enough for what I do. I did some more testing today with v2813. I deactivated my RTX 2000 to render my screen only on the Intel Integrated Graphic. Result : no problem with OpenGL activated, even with more than 1 physical core used at launch. But the OpenGL error messages in the Message Log were still there. So my bug has to do with Nvidia hardware or drivers, in combination with CPU core allocation... very weird. I guess I might be alone to have this bug since nobody else is commenting on this thread for more than 2 weeks. No big deal. |
| [2025-12-06 12:44:22] |
| Mike456039 - Posts: 41 |
|
just to confirm, hyperthreading (smt) off/on in bios - no impact, process lasso activated/deactivate - no impact only thing that has impact for me is using open gl + quadro drivers later than 572.60, Then: chart trade enabled = random black when moving mouse, chart trade disabled = still happens when moving drawings AMD 5800XT Nvidia Quadro P4000 Windows 10 |
| [2025-12-10 19:21:43] |
| Sierra_Chart Engineering - Posts: 21947 |
|
We may have found the reason for the problem. We want you to try prerelease version 2828 when it is released later today or in the evening.
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: 2025-12-10 19:21:53
|
| [2025-12-11 13:10:14] |
| Mike456039 - Posts: 41 |
|
regrettably 2828 or 2829 didnt make any difference for me.
|
To post a message in this thread, you need to log in with your Sierra Chart account: