Archive for the ‘Troubleshooting’ Category

Software rendering

A while back, Vladimir Vukićević updated the OSMESA32.dll build he’s created for people to use on Windows machines that use software rendering, so that it would work with recent builds of Firefox. I’d been intending to test it on my Intel-graphics machine for a while, but it was in storage and a pain to [...]

First cut at a WebGL FAQ

I’ve polished up the content from the talk I gave at WebGL Camp last Friday (video of the Skype presentation of my talk here, all talks linked from here) and used it to create a WebGL FAQ! Thoughts, comments, corrections, whinges and whines all welcome in the comments — or just register and edit [...]

Firefox and Mesa

Recently, the Firefox team updated their support for software rendering so that they use the standard Mesa library that’s distributed with most Linux variants.
As far as I understand it, Mesa can be compiled to have all of its OpenGL functions start with “gl”, which is the default (and follows the OpenGL specification), or with “mgl”, [...]

A render-to-texture problem?

It sounds like some machines might have problems with the render-to-texture code that I’ve written for lesson 16, which is a pain! I’d be really grateful if more people could let me know what they’re seeing when they load up the demo page; you should see a slowly-rotating laptop, on the screen of which [...]

No WebGL in the Chrome dev channel — use Chromium instead

Alvaro Segura writes saying that it looks like they’ve switched off WebGL in the Chrome dev channel; I’ve just tried it out and found the same. A while back, Kenneth Russell recommended (on the public WebGL mailing list) that people using WebGL should use the Chromium nightly builds rather than the dev channel, and [...]

The WebKit flipY bug: fixed?

I’ve a favour to ask: if you’re running Mac OS X 10.6 (Snow Leopard) and have the very latest WebKit nightly build installed, could you check out this page with it and leave a comment here saying whether or not the texture is the right way up?
Here’s why: all of the tutorials on this site [...]

Do textures work for you?

Apparently, gl.enable(gl.TEXTURE_2D) is invalid WebGL, and is absolutely not needed (according to the spec) to make textures work.
However, pipy says in the comments that, at least for him, textures don’t appear without it. Both pipy and Kenneth Russell suspect that the cause might be the graphics driver. [UPDATE: sounds like that was [...]

Changing back and forth…

As they say, it’s six of one and half a dozen of the other… I’ve made some more retrospective changes. The good news first:
On the WebGL Wiki, Gman just removed the code saying gl.enable(gl.TEXTURE_2D) from the tutorial, saying that it’s not required, or indeed valid WebGL! I checked on the mailing list, and [...]

A quick retrospective change to the lessons: image flipping

In the comments to lesson 5, where we introduce textures, rotoglup pointed out that adding an operation per-fragment to flip the texture vertically (which is required because its coordinates increase as you move down the GIF image, while we want maths-like coordinates that increase as you go upwards) is a bit of an overhead for [...]

Context name change with the new draft spec

The new draft spec of WebGL changes the name we use to get the context from the canvas; it used to be moz-webgl for Mozilla or webkit-3d for WebKit. The new standard is experimental-webgl, which the current nightly builds of Firefox seem to use (though they also seem to support the old name), but [...]

Subscribe to RSS Feed Follow me on Twitter!