WebGL around the net, 17 March 2011

You can leave a response, or trackback from your own site.

6 Responses to “WebGL around the net, 17 March 2011”

  1. Tapio says:

    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!

  2. Lindsay Kay says:

    Strangely that Chrome 10 bug, where WebGL breaks input fields in Windows, is not affecting Google Body..

  3. Wendel says:

    “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.

  4. raja says:

    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?

  5. nemo says:

    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.

  6. giles says:

    @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.

Leave a Reply

Subscribe to RSS Feed Follow Learning WebGL on Twitter