Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
May your rolls be chill this holiday season!
Create a free account

Chrome 54.x WebGL Issue Workaround

I hope this is the correct forum for this. If FX or 3D dice have stopped working for you, and you use Chrome, check <a href="https://get.webgl.org/" rel="nofollow">https://get.webgl.org/</a> (as Roll20's settings page suggests). If you don't get the spinning cube then try the below workaround. Credit to&nbsp;dubbekarl (reference to a bug report that gives details here):&nbsp; <a href="https://productforums.google.com/forum/#!topic/chrome/XIy6dtJY4uo" rel="nofollow">https://productforums.google.com/forum/#!topic/chrome/XIy6dtJY4uo</a> I first realized the issue with&nbsp;Chrome 54.0.2840.59 and still exists with the latest, 54.0.2840.87. Workaround in Windows&nbsp; (until it's fixed) Load Chrome with the following parameter: --disable_chromium_framebuffer_multisample An example if you want to edit the shortcut properties, you may want the Target filed to lool like this: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable_chromium_framebuffer_multisample Note : Not sure if it's relevant but dubbekarl and I both use an NVidia GTX260.
1478199320
Gold
Forum Champion
I experience the issue (Chrome crashes Roll20 tab whenever we use FX, tokens become unselectable and the map won't move, Chrome reports WebGL not working even though Roll20 + FX + WebGL was working on same computer for a year before.) Have had the issue ever since Chrome 54.x.x update came out on Mac. &nbsp;Although not on Windows, I plan to look into Mac Chrome hidden config parameters and see if I can find that parameter to disable and test your idea for a workaround. So far my only successful workaround has been: using Firefox instead of Chrome, for the past month or so.
I've had trouble for the past week, I just downloaded an older version of Chrome to get it to work for now.
FYI, looks like version 55.0.2883.75 fixed the issue.
I just bought a new video card to fix it ...