Dynamic Lighting Errors on Linux Chrome and Firefox - still

Hi there,&nbsp; I'm hoping to revive this thread:&nbsp; <a href="https://app.roll20.net/forum/post/9500414/dynamic-lighting-errors-on-linux-chrome-and-firefox#newtopic" rel="nofollow">https://app.roll20.net/forum/post/9500414/dynamic-lighting-errors-on-linux-chrome-and-firefox#newtopic</a> I'm running Linux Mint (Ubuntu) (Latest, just installed yesterday), running Firefox 89 (latest Available right now), as well as Chromium 91.&nbsp; I'm having the exact same issue reported the earlier thread, where the console shows WebGL errors when rendering pages with Dynamic Lighting turned on, causing the browser to sit at the loading screen indefinitely.&nbsp; I have a Windows machine that I can make do with, but I'd prefer to be able to run this from my Linux machine just as well.&nbsp; Any help is appreciated.&nbsp;

You should probably run through the troubleshooting steps and submit a bug report (which is step 4). <a href="https://wiki.roll20.net/Solving_Technical_Issues" rel="nofollow">https://wiki.roll20.net/Solving_Technical_Issues</a> I am running MX Linux (also debian based), and having no issues loading maps with dynamic lighting enabled. Edit: Actually, does webGL work for you if you go to the test page?&nbsp; <a href="https://get.webgl.org/" rel="nofollow">https://get.webgl.org/</a>

The WebGL test page does work for me. I looked through the troubleshooting steps. I have yet to try plugging directly into my modem to avoid anything my router may be doing, but given that others have been having a similar issue previously, I suspect that the issue is not related to my network setup.&nbsp; I will submit a bug report for this. Thanks.

I have also reviewed this post, as found in the help section: <a href="https://app.roll20.net/forum/post/8426341/stuck-on-loading-screen-dot-dot-dot/?pageforid=8514804#post-8514804" rel="nofollow">https://app.roll20.net/forum/post/8426341/stuck-on-loading-screen-dot-dot-dot/?pageforid=8514804#post-8514804</a> unfortunately whitelisting my drivers and changing the sandboxing level has not fixed the issue in firefox. Since the issue is happening in both browsers, I suspect the issue is not related to this post, but it was worth a try. A bug report was submitted for this.

Additional attempts to play with Firefox config settings and even install the vulkan drivers as suggested online have also not met with success. For the record, I have an integrated Intel Graphics card (Intel HD Graphics 3000), listed as using the i965 drivers on my system.

If you didn't submit that with your help center ticket, you might want to send another with that info.&nbsp; I know I have seen an issue on the forums before that happened only on mac and only on very specific hardware.

Hi Kraynic, &nbsp;This is the first time I've had to submit a bug report. Do you know how they usually communicate with the user? Is it via email, or through the roll20 interface? Hopefully it's not just one way only. I actually included a link to this thread in my report, so they should be able to see it. Assuming they reply back, I'll update with their reply. Thanks. BTW, I love your icon. Broadsword and the Beast was a good album.

You should receive an email, though it is possible to get a reply in-thread here. Depending on the nature and complexity of the problem, it may take a few days.

Just a quick update in case the devs are watching. The issue does not appear to be linked directly to OS version/browser version or graphics card. I just tried on a system running Linux Mint 18.3 with Firefox 88, using an entirely different graphics card, and the issue persists. I have a capture of the Web console during the error on this OS, for comparison, if needed, but it is much the same -&nbsp; WebGL warning: linkProgram: Must have an compiled fragment shader attached. app.js:587:17531 Uncaught Error: Must have an compiled fragment shader attached. &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Vertex shader debug info: &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 0:2(12): warning: extension `GL_ARB_gpu_shader5' unsupported in vertex shader 0:3(12): warning: extension `GL_EXT_gpu_shader5' unsupported in vertex shader When I have time to try this on a different (non-Ubuntu) OS, I'll update further.

Hi Everyone. &nbsp; So, I just built a new system, and decided to try loading Roll20 off it. It's a Ryzen5 system with an Asus Nvidia GTX1060Ti Graphics card. I loaded the same version of Linux Mint as above directly off of the USB stick, since I don't have a hard drive installed yet. To my amazement, it worked. This leads me to believe that the issue is actually that Roll20 is making a call to a graphics function that is not available on all graphics cards. It looks like there may be a minimum spec needed for Graphics cards to run Roll20. There really isn't much to see in the console logs, since everything loaded without any issue. I'm going to take the same USB stick and try it in the previously tested systems directly, without any installation, to see if there's a difference between installed and pre-install Linux Mint Ulyssa. If it fails to work, then that means the issue is definitely hardware related (although could also be related to the drivers being used by Linux Mint on those specific cards). I hope this will help anyone looking at it.

BTW, still no word from Roll20 devs&nbsp; or anyone about this issue. Wondering if my bug report ticket dropped into a black hole.

Tested with the Linux Mint 20.1 (Ulyssa) Live USB on the Windows system that was working with Roll20, and it works. Tested with the same USB stick on my Laptop (integrated Intel Graphics card (Intel HD Graphics 3000), listed as using the i965 driver) and it fails.&nbsp; I could try with the third system, which uses an older graphics card which also failed during testing, but I suspect we will see the same issue. I wonder how/if these systems that failed work with Roll20 under Windows? I doubt it, but it will take more time to check. So the good news is that this particular issue is likely hardware related when an unsupported graphics call is being made. Roll20 should be catching uncaught exceptions and either displaying an error message, or finding a way to render in software without relying on the GPU for this.