Since mid-May, when the Google O3D team announced that they were changing O3D from a browser plug-in to a WebGL extension, I have been furiously trying to get it to work on my laptop.
I have tried everything from all of the nightly builds of the supported browsers, to using a software renderer to no avail. My graphics card just flat out refuses to run WebGL, and thus by implication, the new O3D. This is a little bit of a bother for me, as up to now, it has been working rather well as a browser plug-in.
One other thing I have noticed, is that particularly since the announcement, the amount of traffic to my blog to my O3D posts has dropped rather significantly – I am now getting on average a quarter of the hits than a month ago.
This can be due to a number of factors, one of which may be my lack of new posts as of late, but more likely it has to do with O3D itself. Since the WebGL version has been released, I have not been able to write up much about it, since I have not managed to get it to work, so either people are finding other sources which ARE writing about WebGL instead of coming to my blog, or else people have just given up interest in O3D in general, or, like me, are struggling to get the new version to work.
It would be really sad if O3D was becoming irrelevant, but I am hoping that progress will be made in getting O3D (and WebGL) to a decent level where it is supported in standard browsers again, and on most hardware platforms as I do want to see this technology fly…
Serge Meunier is a software developer living in Cape Town, South Africa. He loves programming, fencing, philosophy, feeding his internet addiction, and, of course, dogs.