News for hackers. Stuff that matters.
Re:Seriously.js by mindcrime on Wednesday June 05, 2013 @05:43PM (#5828825)
"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.

Re:Seriously.js by dualogy on Wednesday June 05, 2013 @06:04PM (#5828970)
I 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).
Re:Seriously.js by brianchirls on Wednesday June 05, 2013 @10:00PM (#5829927)
Yeah, 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.

Re:Seriously.js by sanarothe on Wednesday June 05, 2013 @10:08PM (#5829948)
chrome://flags

override software rendering list

Re:Seriously.js by j-m-o on Wednesday June 05, 2013 @08:26PM (#5829608)
Works great for me, using Chrome on Ubuntu 12.04 on a Dell Inspiron 15R (Radeon 7700M) with the latest fglrx drivers.
Re:Seriously.js by ilamparithi on Thursday June 06, 2013 @03:35AM (#5831021)
Same message here (Ubuntu, Dell, Chrome). But it worked on Firefox.