5 ms·
"Sadly, we are unable to get Seriously.js to work on your computer. Sometimes WebGL gets a bit weird with certain graphics hardware and drivers. Please have a l
by danielweber 13y ago
"Sadly, we are unable to get Seriously.js to work on your computer. Sometimes WebGL gets a bit weird with certain graphics hardware and drivers. Please have a look here for more information."
- fierycatnet 13y agoSame here. Could it be because I am running Linux?
- matchu 13y agoI got it working in Linux on Firefox. Chrome didn't work, though.
- WatchDog 13y agoWorking on Ubuntu 12.04 Firefox 21 and Chrome 27, AMD drivers.
- aceperry 13y agoWorks for me on Ubuntu 13.04, Chrome 28(beta), Firefox 21, using Nvidia drivers.
- thefreeman 13y agoyou just need to enable it. it is disabled by default for most Linux OS / video card combos
- Flimm 13y agoIt failed here, but without an error message. I can only see the first frame.
- mindcrime 13y ago"Sadly, we are unable to get Seriously.js to work on your computer. Sometimes WebGL gets a bit weird with certain graphics hardware and drivers. Please have a look here for more information." Yeah, same here, running Ubuntu on a Dell Precision laptop. Guess WebGL doesn't like my setup.
- dualogy 13y agoI coded WebGL a little over a year ago on a Precision "laptop" under Suse Linux. What I needed: (A) up-to-date Nvidia proprietary drivers (B) "de-blacklist myself" somewhere deep in the browser's hidden WebGL config page (I think it was about:gpu or some such back then in Chromium, but I'm not really up to date).
- brianchirls 13y agoYeah, I run Chrome on Ubuntu on a pretty powerful Lenovo T-something with an NVIDIA whatever optimus pain in the neck. The only way I can get it to work is to add --ignore-gpu-blacklist to the Chrome command line. Check: /usr/share/applications/google-chrome.desktop (or something like that) You should see some lines that start with "Exec" where you can add that parameter to the end.
- sanarothe 13y agochrome://flags override software rendering list
- j-m-o 13y agoWorks great for me, using Chrome on Ubuntu 12.04 on a Dell Inspiron 15R (Radeon 7700M) with the latest fglrx drivers.
- ilamparithi 13y agoSame message here (Ubuntu, Dell, Chrome). But it worked on Firefox.
- mncolinlee 13y agoI had the same message in Firefox on Windows, but it worked fine in Google Chrome.
- FireBeyond 13y agoApparently with my Retina MacBook Pro with 10.8.4 and Safari 6.0.5, I "need to upgrade my video drivers", according to the site...
- pistacchioso 13y agoI can confirm this. On Chrome, though (same machine and same webkit, I guess) it runs smoothly.
- simonster 13y agoSadly, Safari still doesn't support WebGL by default, although you can enable the Develop menu in the prefs, and then enable it in the Develop menu.
- gilgoomesh 13y agoEven if you do: it runs super slow on my Mac Pro.
- Fomite 13y agoMac Pro running Mountain Lion with an ATI 5870 graphics card. Color me not terribly impressed.
- melvinmt 13y agoGot the same thing for in Chrome. Did work for me in Firefox though.
- 6ren 13y agoCould someone upload a video of the result? not the finished OKGO music video please :)
- rexreed 13y agoSame here - FF 22.0 on Windows XP
- mkolodny 13y agoI had the same deal with Chrome on my OSX Mountain Lion. Here's what fixed it for me: 1. Visiting chrome://flags 2. Scrolling down to Disable WebGL, hitting "Enable", and then "Relaunch now" 3. Repeating steps 1 and 2, but hitting "Disable" rather than "Enable".