Macos Big Sur 11.6
Processor: 2 GHz Quad-Core Intel Core i5
Graphics: Intel Iris Plus Graphics 1536 MB
When I was running the example on playground, the page show that error message.
After some research, I was aware that it’s because chrome disabled webGL feature for compatibility issue. So I followed this guide and enabled the feature, everything seems to be normal.
I checked the output of chrome://gpu/ on chrome.
However, as I ran the example again, the same issue happened (but not every time as last time I ran it.) every time this error happen, the webGL config was set automatically back to original config, that is say browser disabled webGL feature automatically after the error for some reason.
on the on the contrary, all examples can run nicely and smoothly on safari at a FR of 60😁
Is there anybody encountered the same problems? any help will be appreciated!
Actually, It happened on my personal macbook
This is my chrome config. I’m wandering if this will happen on users computer, as I’m building my app on babylon and chrome is used by lots of people, so I worry about they perhaps have no patience to solve this problem if users encounter this.
Nope, never had this. I’m using default config to test for my clients (on a range of mac and win rigs) and it looks like the defaults do not create this sort of thing. However, using a fancy config in the browser or a fancy app for ‘protection’ (i.e. antivirus or rig configured for ‘security’, such as a laptop for ‘banking’) could eventually enable these ridiculeous settings (and prevent webGL enabled apps). I’m afraid this is not on the side of Babylon.js (and nothing that can be done to prevent this)
I get the same thing with every playground on my macbook. Refreshing the page fixes it and loads the second time. Always figured it was just me since never heard it from coworkers or anyone else
