#threeJS + chrome doesn't seem to work on any machine. Am I missing something?
10 messages · Page 1 of 1 (latest)
Chrome is almost all I use and it works fine for me.
From what I'm seeing through a few searches, the most plausible suspect would be that you have hardware acceleration turned off in Chrome somehow.
(There's also https://stackoverflow.com/questions/54232528/error-creating-webgl-context-three-js-chrome which suggests a couple more possibilities)
@woven totem hi thanks. Is that something that is on by default though? not something i remember touching. is it your understanding that its on by default?
Yeah, it should be on by default — but again, I'm not having any issues with Chrome in more-or-less its default configuration hitting up the THREE site, so I'm presuming that you've got something that's different about your config somewhere.
And prosaically, if the site were broken by default on what's by far the most common web browser, it would surely get noticed (and hopefully fixed) pretty quickly.
I got a similar error with Firefox yesterday, i closed the browser and re-opened it, and then it worked fine...
Fyi - it may not the the case here, but if you cause a lot of drastic WebGL errors (can easily happen when coding shaders for example), errors that cause your GPU to start flickering random pixels and reset entire browser view - Chrome will dispose all contexts immediately and prevent further context creations from that specific page / origin for safety reasons (until you restart the entire browser.)
thanks! im really not sure what happened - it was two unrelated machines with 2 different OS with unmodded versions of chrome. The only commonality was the internet connection. Today they're both working with the same default threeJS template. 