Home >> Support Board

Support Board

Date/Time: Tue, 23 Dec 2025 04:19:15 +0000

How to Post a Message for Support

Open GL + Quadro Drivers later than 572.60 + Chart Trade Mode = chart black out glitches

View Count: 775

[2025-12-11 13:10:14] #25 [Go To First Post]
Mike456039 - Posts: 41
regrettably 2828 or 2829 didnt make any difference for me.

[2025-12-11 15:59:51] #26 [Go To First Post]
Sierra_Chart Engineering - Posts: 21947
There is a lot in this thread, and we lose track of what exactly the current problem is. Briefly restate the problem, and copy and paste here any error messages you see in the Message Log. Is it the same problem, described in the first post? If so, then we need more time on this. We will need to duplicate the current set up you are using. Regarding the video hardware, and driver. We are working on this. There is a significant investment we are making in computer hardware. We are currently assembling a server, which we are use for development, and will be running Windows 10 on it, in a virtual machine, and using an Nvidia Quadro graphics accelerator. 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-11 16:02:29

[2025-12-11 18:33:11] #27 [Go To First Post]
Sébastien - Posts: 110
Hi, With V2813 and earlier, when SierraChart was launch on more than 1 physical CPU core, with OpenGL enable, the problem was : - Blinking black of DOM ladders when the mouse pointer is moving over it https://www.youtube.com/watch?v=FS0pGP56Y_M - CPU utilization increasing with time, leading to poor performance - RAM utilization increasing with time - OpenGL Error messages were : 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. 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. Now, with V2829, when SierraChart is launch on more than 1 physical CPU core, with OpenGL enable : - Blinking black of DOM ladders still happening - CPU and RAM utilization aren't increasing anymore. Performances are good. - The error messages of V2813 are gone. - But there are new error messages : 2025-12-11 08:20:30.573 \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-11 08:20:30.573 \| OpenGL: cannot allocate texture 2025-12-11 08:25:42.404 \| OpenGL error in BindFrameBufferObjectAndViewport returns error: INVALID VALUE Number in queue: 0 \| Number times message added: 39 - Also, texts of all DOM columns (Recent, Current, Bid/Ask Depth, Pull Stack...) are invisible. Only the Price column text are visible. - Same problem with the study Market Depth Historical Graph, when Show Quantity Numbers is activated, the text don't show up. Date Time Of Last Edit: 2025-12-11 20:00:44

[2025-12-11 19:53:06] #28 [Go To First Post]
Mike456039 - Posts: 41
thank you Sébastien for doing this, my problems are as I described in the first post. I wont have time until weekend to mess around reinsall drivers etc, but I;ll try and get the error logs cut and paste then. it wont be as comprehensive as Sébastien though :)

[2025-12-14 19:53:43] #29 [Go To First Post]
Mike456039 - Posts: 41
2829 and decided to install latest quadro 582.08 It all went a bit odd, with blue boaders around window, and when I maximised a window I lost the minimise/restore/close icons on the top right. OPengL - checked Compatible Open GL Profile - checked Enable OPen GL Debug - checked I'm looking in message log? found these OPENGL errors - only these no others 2025-12-14 14:20:23.469 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.469 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.482 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.482 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.494 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.494 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.507 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.507 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.519 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.519 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.531 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.531 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.543 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.543 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.556 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.556 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.568 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.568 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.582 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.582 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.594 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.594 \| Graphics \| OpenGL: cannot allocate texture * 2025-12-14 14:20:23.604 \| Graphics \| OpenGL error in allocate Bitmap/glTexImage2D from raw returns error: INVALID VALUE Number in queue: 0 2025-12-14 14:20:23.604 \| Graphics \| OpenGL: cannot allocate texture *

[2025-12-14 20:06:39] #30 [Go To First Post]
Mike456039 - Posts: 41
And going back to 2813 current version - everything is normal again (no bright blue borders around windows) i dont loose the window control icons from top right if I maximise a window. Found these: this seems a appear without doing anything, just loading up the chartbook 2025-12-14 14:55:28.892 \| Graphics \| OpenGL CALLBACK: ERROR type = 33356 (API), severity = 37190, message = GL_INVALID_VALUE error generated. Size and/or offset out of range. this tirggers when the screen goes black 2025-12-14 14:55:56.321 \| Graphics \| 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. Hope this helps?

[2025-12-14 20:25:51] #31 [Go To First Post]
Sierra_Chart Engineering - Posts: 21947
Post #29 is not helpful to us since the version is out of date. 2829 was a pre-release and that is now out of date. The latest prerelease is 2833. You need to use that version. It all went a bit odd, with blue boaders around window, and when I maximised a window I lost the minimise/restore/close icons on the top right. everything is normal again (no bright blue borders around windows) i dont loose the window control icons from top right if I maximise a window. We need to prepare documentation for the changes related to MDI Windows. Colors are fully customizable, unlike in Windows, and the MDI child window commands are now menu commands and can be customized. 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-14 20:31:14

[2025-12-14 20:50:28] #32 [Go To First Post]
Mike456039 - Posts: 41
2813 and latest quadro 582.08, this is all without chart trade mode enabled: On my heavier graphics/studies chartbook: without touching or moving mouse lots of these errors: 2025-12-14 15:42:25.716 \| Graphics \| OpenGL CALLBACK: ERROR type = 33356 (API), severity = 37190, message = GL_INVALID_VALUE error generated. Size and/or offset out of range. once I move a rectangle the screen goes black (attached file) and then this error triggers 2025-12-14 15:45:22.152 \| Graphics \| 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.


Screenshot 2025-12-14 204029.jpg / V - Attached On 2025-12-14 20:48:29 UTC - Size: 163.51 KB - 4 views

[2025-12-14 21:08:14] #33 [Go To First Post]
Mike456039 - Posts: 41
ok sorry, ignoring the new MDI windows stuff then: 2833 and 582.08 OPengL - checked Compatible Open GL Profile - checked Enable OPen GL Debug - checked- chart trade disabled doing nothing no OPEN GL errors moving mouse around and panning charts around -no visible erros blinking black etc but movement is very laggy -no OPEN GL errors rezising a rectangle/moving a text box -screen goes black (attached file) -but no OPENGL erros in log. if chart trade mode enabled: -Screen can be made to blink black -(exactly same as attached screenshot ) just by moving the mouse/cross hairs around -but no OPENGL errors Date Time Of Last Edit: 2025-12-14 21:17:05


Screenshot 2025-12-14 205855.jpg / V - Attached On 2025-12-14 20:59:15 UTC - Size: 196.91 KB - 6 views

[2025-12-14 21:39:23] #34 [Go To First Post]
Mike456039 - Posts: 41
hang fire! I changed some things in nvidia control panel 3d settings and got rid of the problem error whenever I installed the quadro drivers, I did a clean install with full reset. The default setup on 572.60 must be different from the default on every driver going forward. I need some more time to find out exactly what will trigger, as I changed a lot a things in one go, such as: Threaded optimisation > Off Vertical Sync > On Triple BUffering > ON Shader Cache size > 1GB Ill keep testing and update:

[2025-12-14 21:49:03] #35 [Go To First Post]
Sierra_Chart Engineering - Posts: 21947
Let us know the particular settings you are using that causes the issues, and do not cause the issues. 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-14 21:53:44] #36 [Go To First Post]
Mike456039 - Posts: 41
BINGO!!!! It is Threaded Optimisation in the Nvidia Quadro Control Panel 3d Settings Default is AUTO But when set to OFF - all the problems with blinking black screen are gone. With threaded optimisation off, I cannot trigger the blinking/black screen problem no matter what I do, chart trade enabled, moving rectangles, loads of studies ete etc, nothing triggers the fault. Problem totally solved, and its a configuration setting withing Nvidia Drivers/Control Panel. I'm assuming they changed default configuration after 572.60 - I will go check this now.

[2025-12-14 22:43:12] #37 [Go To First Post]
Mike456039 - Posts: 41
so, with threaded optimisation set to OFF in Nvidia Control Panel the problem is gone/solved, also dont need Compatible OpenGL Profile checked. -if I set threaded optimisation back to auto then all the original problems come back, all other settings are default from a clean Nvidia driver install. for prerelease 2833 no visual errors at all, no blinking/blacking no OPENGL errors in the log the lag I noticed has completely gone for current 2813 no visual errors at all, no blinking/blacking do get these errors in the log: 2025-12-14 17:26:39.804 \| Graphics \| OpenGL CALLBACK: ERROR type = 33356 (API), severity = 37190, message = GL_INVALID_VALUE error generated. Size and/or offset out of range. I checked 572.60 and the default Global settings for a clean install of Nvidia drivers seems identical to 582.08, they both certainly have Threaded Optimisation set as Auto. Perhaps something else changed after 572.60 or the Auto meant something different?? I am so sorry if I wasted time, as it was the change made in Nvidia Drivers all along. Date Time Of Last Edit: 2025-12-14 22:52:14


Screenshot 2025-12-14 223428.jpg / V - Attached On 2025-12-14 22:34:55 UTC - Size: 148.88 KB - 13 views

[2025-12-14 23:11:09] #38 [Go To First Post]
Sébastien - Posts: 110
V2833 here. I can confirm what Mike said. Turning off the Threaded Optimisation made the blinking black bug disappear. CPU and RAM utilization are lower. Also, performances are huge now. Huge thanks Mike !

[2025-12-14 23:11:33] #39 [Go To First Post]
Sierra_Chart Engineering - Posts: 21947
We want to comment on the Threaded Optimization setting in the screenshot. It says: "This setting should be turned off for most older applications" Sierra Chart would not be considered an older application regarding OpenGL because it uses core-profile OpenGL version 3.3. Refer to: https://learnopengl.com/Getting-started/OpenGL An old application would be using: In the old days, using OpenGL meant developing in immediate mode (often referred to as the fixed function pipeline) which was an easy-to-use method for drawing graphics. We have to think about why that setting is causing a problem. We will do 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-14 23:12:35

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