Check chrome://gpu/ in Chrome. It should say whether WebGL is enabled. I have to run Chrome with --enable-webgl --ignore-gpu-blacklist to make it work.

I'd be very surprised if Chrome didn't blacklist nouveau; perhaps you're overriding this behavior with a command-line flag? Visit about:version to check.

Actually, this is the first webgl demo that I've ever had trouble with. Gallium seems to cover most of the common extensions and claims support for OpenGL 2.1, GLSL 1.2, which is recent enough for most applications.

And no, I'm not overriding anything, it's always just worked.

Edit: In fact, doing a quick grep through the shipviewer.js file, they're only using GL_ARB_texture_cube_map plus a bit of framebuffer drawing, both of which are fairly standard things and should be supported by gallium. No idea what the issue might be..

I have the same issue, in both Chrome and Firefox, using the nvidia binary driver.

The engine lights do look pretty though.

Why would Chrome blacklist Nouveau? I'm sure it's far less hacky than the official Nvidia binary blob.

We have no idea whether the nvidia driver is hacky or not, but it does actually work quite well, whereas nouveau is (or was the last time I checked) still known to have features/cards that aren't supported.

Actually this is what happened to me in Safari on Lion: most models showed up, but a few were not, only their engine plumes as you described.

Works great on my Ubuntu's Firefox with Intel integrated graphics.

Same here on Linux.

I can see the ship for a second, then it explodes and disappears. Firefox 12, Linux, Intel Mesa drivers

Same problem...