max123 Posted November 16, 2016 Share Posted November 16, 2016 Error on PG: Compilation error Your browser does not support WebGL Chrome v. 54.0.2840.98, OS X 10.9.5 Any PG results in this error with the above version of Chrome; Safari and Firefox are OK. Bummer! Quote Link to comment Share on other sites More sharing options...
max123 Posted November 17, 2016 Author Share Posted November 17, 2016 For anyone experiencing the same issue: it's Google's fault, not BJS. A lot of people are reporting the bug. On my macbook pro, if graphics cards are in dynamic switching, Chrome 54 disables WebGL on Intel. If you force your mac to switch to the dedicated graphics card, all works as expected. F***ing Chrome https://productforums.google.com/forum/#!msg/chrome/3xhOQtapY5o/iTKHdJ82BQAJ RaananW 1 Quote Link to comment Share on other sites More sharing options...
RaananW Posted November 17, 2016 Share Posted November 17, 2016 I can only assume that it happens when trying to use the WebVR camera? or is it happening when using babylon in general? Quote Link to comment Share on other sites More sharing options...
max123 Posted November 17, 2016 Author Share Posted November 17, 2016 It has nothing to do with babylon or any other 3D framework. WebGL context itself is disabled on the browser level! Quote Link to comment Share on other sites More sharing options...
RaananW Posted November 17, 2016 Share Posted November 17, 2016 Man, I read it "WebVR" and not "WebGL".... Yep, sorry, forget it, ignore my last message. Not enough coffee. Or too much of it. GameMonetize 1 Quote Link to comment Share on other sites More sharing options...
max123 Posted November 17, 2016 Author Share Posted November 17, 2016 I'm on my 3rd mug, and it's only 11am Quote Link to comment Share on other sites More sharing options...
JCPalmer Posted November 17, 2016 Share Posted November 17, 2016 Thanks for the heads up. Ubuntu is a couple of days later. Got notice new version was available this morning. Said no. Quote Link to comment Share on other sites More sharing options...
max123 Posted November 17, 2016 Author Share Posted November 17, 2016 @JCPalmer, the problem is with certain chipsets, or, rather, how the new Chrome treats certain chipsets. You might not even experience the issue Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.