Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In Chrome, all I see is lighting effects occluded by solid black (unshaded) shapes. This is similar to what I see in the BananaBread demo in Chrome.

Works fine in Firefox, but as is typical for WebGL demos in Firefox on my machine, looks like about 10 fps.



I'm on a dual GPU system running Linux + bumblebee. When using the Sandy Bridge GPU, I also see all black with only the lighting highlights visible. Just tried again with the nVidia GPU and it worked fine.

I really like WebGL, and I want it to succeed, but for this to happen developers are going to have to make sure that their code works on reasonably low end hardware (i.e. integrated graphics). This sort of GPU inconsistency is so common with WebGL right now that it reminds me of trying to browse the web on Linux circa 2000.

Not a pleasant experience.


I got a lot of these errors on the console for Chrome: .WebGLRenderingContext: GL ERROR :GL_INVALID_ENUM : glCompressedTexImage2D: internal_format was GL_COMPRESSED_RGBA_S3TC_DXT1_EXT

Turns out it requires S3TC compression which is not supported in Mesa drivers by default (only decompression is). After installing libtxc_dxtn.so it worked just fine in Chrome.

Also it doesn't work with Firefox 10.0.12, even if I enable WebGL. It does work with latest nightly (Firefox 22.0a1) though.


Aha! Installing the libtxc_dxtn_s2tc0 package fixed it, and it ran smoothly (with a small periodic stutter). That fixed BananaBread too (well, it's still buggy, but sometimes it works correctly). That package seriously needs to be a default for Ubuntu, given how many WebGL pages I've seen it break.


Another solution is to: "export force_s3tc_enable=true" (or equivalent setting in ~/.drirc) since only decompression is needed.


works fine in chrome for me




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: