- Problems in Chrome 10 under Windows
— it looks like input fields in pages that use WebGL won’t work. This was reported a while back but somehow made it into the stable release. To check if your browser is affected, try this test page by Stephen Bannasch, who also reported the problem on the WebGL list.
- If you like formula one car racing, you’ll love this simple (but very well-rendered) game, HelloRacer.
- But if you prefer your games Doomy, have a look at the latest version of Pl4n3’s Wloom.
- Alternatively, if low-fi Roguelike games — with a shiny WebGL makeover — are more your kind of thing, you should definitely try A Little Anxious When It’s Dark.
- Moving away from games, there’s some fun new stuff on the Mozilla Web O’ Wonder: the Letter-heads from Simurai, and an update of Benjamin DeLillo’s 360° video WebGLU demo.
- From Cedric Pinson, osgjs, a new JavaScript implementation of OpenSceneGraph based on WebGL (repo here, blog here), and a fun vehicle editor for a game.
- This is an interesting idea: WebGL-2D, an implementation of the HTML5 Canvas2D API in WebGL to give you Canvas 2D’s ease of use with WebGL’s speed.
- On a similarly 2D note, WebGLSpriteEngineJS is worth checking out.
- This SceneJS Earth is targeted at teaching middle-school students how the seasons work.
WebGL around the net, 17 March 2011
March 17th, 2011
6 Comments
These “around the net” posts really are superb. They basically present everything that’s worth checking out in the WebGL front and save a ton of googling (I mean it’s surreal that something can actually beat google search at something…). Keep up the good work!
Strangely that Chrome 10 bug, where WebGL breaks input fields in Windows, is not affecting Google Body..
“Problems in Chrome 10 under Windows”
I can simulate the same problem in Chrome 10 in others operation system.
When I open 3, sometimes 2, chrome windows with the same webgl application, the background of the page and the input act weird. (not 3 tabs, but 3 different window)
Just tested again using the example
http://visual-demos.dev.concord.org/seasons/earth/latitude-line-test.html
Im on Ubuntu 10.04, Chrome 10.
note: The problem doesnt happen if I open 1 chrome, and 2 firefox.
I couldn’t play the HelloRacer game in Firefox 4.
It worked on Chrome though. 12 fps, it seems low, but is that the norm on browser based 3d?
Hey Raja. HelloRacer is at 40fps for me on my ancient Nvidia 120M card, Windows XP, Firefox 4.
At just under the 60fps cap on my nvidia card GeForce 9800GT, Linux, Firefox 4.
I don’t think it can go any further than that.
ATI offers “meh” webgl performance under linux, and has always had bad Xrender support, but my Radeon HD 4670 is at 35FPS under Firefox 4.
If it isn’t working for you, try updating your video drivers as bjacob said in that post that this blog linked to earlier.
You can also see your vid card info under about:support in Firefox.
@Tapio — well, Google alerts help a lot when I’m looking for stuff
@Lindsay — that is odd. Perhaps they’re using their own components and it only effects normal native ones?
@Wendel — very odd! Well, hopefully Chrome 11 will be out soon and will fix it all.
@raja, @nemo — I get a pretty decent framerate too. Agreed that a driver update might help.