WebGL around the net, 20 January 2011

  • I can’t read Japanese, but if Google Translate isn’t leading me astray, I think someone has managed to drive a three.js WebGL animation from Kinect!
  • More great three.js demos: from AlteredQualia, Hilbert Curves and image postprocessing, from Mario Gonzalez a simple scene editor, and from I’m-not-quite-sure-who, a movie file being used as a texture [UPDATE turns out the last one is 2D canvas, not WebGL — which makes it more impressive, if less relevant to this blog :-) Thanks to AlteredQualia for the head-up.].
  • I linked to Aleksandar Rodic’s jellyfish back in October, but it’s got much better since then!
  • Try clicking on this canvas (by Paul Zinn-Justin)
  • This looks pretty impressive (and pretty pretty): from Sami Mäkelä, a 1024-body simulation, running on the GPU using the float textures extension; I believe that currently makes it Chrome-only (GPU-heavy, give it a while to get started).
  • The Copperlicht Quake 3 demo has been improved to show off their new release 1.3.3, with improved collision detection and view direction control — well worth a look.
  • Recent versions of Chromium have started throwing odd errors to do with unexpected EOFs in shader strings. The problem is that they recently started enforcing a little-known part of the WebGL spec that banned the use of characters like quotes or @ signs in GLSL shaders, even in comments! There’s been a lot of discussion about the issue on the Public WebGL list, and the general consensus seems to be that while actual shader code can be in a restricted character set, you should be able to put anything you want in comments — including non-ASCII characters. So, the spec has been changed and now you can put any UTF-8 text in your comments; the actual code, however, must still be ASCII. Looks like implementations will support that shortly.
You can leave a response, or trackback from your own site.

4 Responses to “WebGL around the net, 20 January 2011”

  1. Thanks for links ;) Just a small correction – Three.js video texture demo is not WebGL, it’s using 2d canvas renderer. This is still on todo list for WebGLRenderer.

  2. giles says:

    Thanks! I’ll fix the links.

  3. Aleksandar says:

    Thanks for posting the link to the Japanese author of the Kinect example. He helped to make the Kinect interface with my example. I will share my progress soon. Also, I made a short post about this kinect+webgl interface technique. http://blog.aleksandarrodic.com/?p=4

  4. giles says:

    Hey Aleksandar, that’s fantastic! Really interesting stuff, I’m looking forward to reading more.

Leave a Reply

Subscribe to RSS Feed Follow Learning WebGL on Twitter