Account-wide option to disable/enable WebGL in Lucid

Hi ​@Wildcart 

Lucidchart does not currently offer a global account-level setting to disable WebGL across all documents. WebGL is controlled per document.

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

Hi ​@Wildcart, thanks for your post and thank you ​@Humas1985 for chiming in!

Unfortunately, this indeed isn’t currently supported in Lucid, but we’re very interested in your feedback and committed to continually improving our products. If you’re willing to share, we’d love to hear more details about your use case or what you’d like to see in this experience within this thread. I’ve also converted this post to an idea so that it’s visible to others within the Product Feedback section of the community - from here, they can upvote it and add details of their own.

Finally, for more information on how Lucid manages feedback via this community, take a look at this post:

Cheers!

Hi ​@Zuzia S, thanks for your reply.

"More details about my use case:"

As I’ve indicated in my initial post I am exclusively using Lucid Chart on Linux systems, mostly using Chromium (currently version 145.0.7632.75). When I go to https://get.webgl.org/ or https://webglsamples.org/ to test whether Chromium supports WebGL, all examples run just fine and my system monitor shows 100% GPU utilization and 1~2% CPU utilization. This lets me assume that WebGL is supported, in general. 

Enabling WebGL rendering in a Lucid Chart document, however, causes massive performance problems: 

• opening menus and sub menus takes 40 seconds to one minute, each
• selecting a shape takes 20 to 30 seconds
  • selection boxes around selected shapes are not shown
  • arrows to rotate the shape, however, are shown
• switching from/to/between browser tabs showing Lucid Chart documents, takes about 20 to 30 seconds
• witching between browser tabs showing external Web sites works just fine (tabs are in the same chromium window as are the Lucid Chart tabs).

"What I like to see in this experience within this thread:" 

• Add the shortcut to disabled WebGL to the "Turn off WebGL" section on the Basic troubleshooting page. 

I think adding the shortcut to the documentation is important as it mitigates the performance issues in case WebGL is not working correctly. Without knowing the shortcut one has to be very(!) patient to open the menu(s) to disable WebGL.

• Add a global/account option to enable/disable WebGL for all documents 

Since WebGL is something that I would assume to either work or not work, I would have expected to find a global/account setting to enable/disable WebGL rendering for all documents. As you’ve confirmed this option does not exist. Also, having the option to enable/disable WebGL, or any other feature for that matter, on a page that requires WebGL to function (performance wise), seems to be problematic as it becomes difficult for the user to disable WebGL, especially if not knowing the shortcut. 

Cheers

  Chriss.
 

​@Wildcart thank you so much for leaving these additional details and feedback, along with your examples! And I am sorry for the inconvenience caused. Your comments here are helpful to our product teams as they continue to research new product features and enhancements.