Support Board
Date/Time: Thu, 10 Sep 2026 06:43:54 +0000
OpenGL: multi-line DRAWING_TEXT drawn by an ACSIL study disappears past ~27 lines
View Count: 274
| [2026-07-26 13:52:15] |
| User549147 - Posts: 14 |
|
I have a custom ACSIL study that draws a multi-line text panel on the chart using sc.UseTool() with a DRAWING_TEXT drawing (a single Text string containing \n newlines, MultiLineLabel = 1). The drawing displays correctly until the text reaches a certain number of lines, at which point the entire drawing disappears — not clipped or truncated, the whole text label vanishes. I have isolated the cause to OpenGL chart rendering: With Use OpenGL = No (software rendering), the drawing displays correctly at any number of lines. With Use OpenGL = Yes (Global Settings >> Graphics Settings), the entire drawing disappears once the text exceeds approximately 27 lines. Below that threshold it renders normally. This is the same behavior on two installations, and the deciding factor is the OpenGL setting, not the version: Version 2930 64-bit (OpenGL enabled): fails past ~27 lines. Version 2882 64-bit (clean install): renders fine with OpenGL off, and reproduces the failure as soon as OpenGL is turned on. Setting MultiLineLabel = 1 does not change the behavior. Question: Is there a maximum size — number of lines, pixel height, or texture dimension — for a single DRAWING_TEXT drawing when OpenGL rendering is enabled? Is there a setting or an ACSIL option that avoids it, or is splitting the text across multiple stacked DRAWING_TEXT drawings (each kept under the limit) the recommended approach? |
| [2026-07-26 20:23:38] |
| Sierra_Chart Engineering - Posts: 24817 |
|
We will have to check on this, but use a separate drawing when using OpenGL, if it is exceeding the 27 lines. If there is a limitation, it is there for a good reason. OpenGL does not support text and it all has to be implemented by Sierra Chart: Graphics Settings: Text Display when using Open GL 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 |
| [2026-07-27 16:47:55] |
| User549147 - Posts: 14 |
|
Thanks, pls let me know if there is something I can do to help. Also, should I use sc.DrawText() instead of DRAWING_TEXT for a text dynamic display panel? Asking because if the ~27-line vanish is caused by a DRAWING_TEXT tool compositing its entire multi-line block to a single texture/buffer (which has a size cap), then sc.DrawText drawing character-by-character could sidestep it? Just a thought. Date Time Of Last Edit: 2026-07-27 16:58:35
|
| [2026-07-28 07:31:41] |
| Sierra_Chart Engineering - Posts: 24817 |
|
This is up to you what will work best. You just have to try. But it would be fine to use sc.Graphics.DrawText() for each 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, use 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: