Hacker News Reader

Comment by daeken | Hacker News Reader

If that's the case, then you don't have WebGL enabled, or your GPU is being blacklisted by your browser.

I have the same issue in Chrome on OSX, and WebGL is enabled for me. I've played some of the WebGL demo games, so I doubt it's due to my GPU being blacklisted.

Hmm, unusual. Can you see http://demoseen.com/windowpane/magister.test.html ?

I cannot, although all of the demos I've tried here work: http://www.khronos.org/webgl/wiki/Demo_Repository

Only thing I can think of at this point is that you have an extension inserting something into the body before the canvas. While on Magister, drop javascript:alert(document.body.firstChild) into the address bar and see if you get the canvas -- if not, that's the problem.

The tab crashes after a while when I try that. Weird. Even with all extensions disabled, it hangs without ever finishing loading.

Old version of chrome perhaps? Works fine on my chrome on osx here. 12.0.742.122 here. (I'm technically out of date too, mostly because I haven't restarted chrome in a while)

Nope, I'm on the same version as you, although it tells me that's the latest version.

It does not work for me either - blank white screen. Same setup, Mac OS X and Chrome. I do get the canvas when pasting that snippet, though.

Same situation as the rest of this thread - I just get cpu usage and a white screen, in Chrome stable/beta/dev. OSX on a MBP, only thing I can think that might be shared with others having problems is my GPU: GeForce 8600M GT. I haven't heard of problems with this card before, but OSX + GPU ≠ consistent results, at times.

Though interestingly, the behavior in all three Chromes is wildly different: Dev runs 60% CPU use in the rendering process, Beta sometimes uses nothing, sometimes 60%, and Stable uses the same 60% + 120% on "google chrome helper". The alert test works (shows a canvas element) in both Dev and Beta, Stable shows me a "page unresponsive" after a couple seconds and never alerts anything.

Other GL tests work just fine in all 3. I'll be happy to test other things if you can come up with them :)

Nope. You have a js error somewhere:

Uncaught ReferenceError: S is not defined

That's not a JS error. 'S' is a function defined in WebGL, which gets pulled out and names are passed through a regex that filters out certain characters. So it's not getting a WebGL context, and thus that function never ends up being pulled into the global namespace.

For whatever it's worth, I'm on the same build of Chrome (12.0.742.122) on OSX 10.6.8 and the demo is working fine for me.

Reply on news.ycombinator.com