Three.js: JavaScript 3D engine for canvas, svg, and WebGL

http://github.com/mrdoob/three.js#readme

by helium • 16 years ago

93 22 16 years ago

niyazpk• 16 years ago

The demos are really mind-blowing. Stuff that I never expected to come so fast to the browser are becoming a reality. This is really exciting stuff for me. I will definitely use some of these libraries (linked to from the page) in a few upcoming canvas based projects.

nkassis5• 16 years ago

http://www.learningwebgl.com is an incredible site for learning about webgl. Here is a list of WebGL frameworks listed on their wiki: http://learningwebgl.com/cookbook/index.php/Main_Page (scroll to the bottom)

I'm personally using O3D right now. I've heard good things about the others such as GLGE

exit• 16 years ago

how are you going about learning o3d? it seems like the documentation effort stopped when they switched to webgl.

nkassis5• 16 years ago

Well, the docs are a little out of date but most of it works as it did before. I had about 3 lines to change when I started using the webgl version. (details of what needs change is available here: http://code.google.com/p/o3d/wiki/GettingStarted)

Some parts are not yet implemented but I've managed to get work done without using any of them. The core devs are often on the mailinglist: http://groups.google.com/group/o3d-discuss

The repos are active, last update was last week. I just use whatever they have in SVN right now, the packages on their webstite is very outdated.

skar• 16 years ago

I'm getting 60 fps approximately for the spinning cube with chrome 6 on Ubuntu Lucid and my laptop has a core i3 with built in arrandale based GPU, not an nvidia or ati one.

Not long ago, on an older laptop, I was getting the same fps for native Linux apps. Seems browsers are acquiring native capabilities, but at a faster rate :)

s3graham• 16 years ago

The 'Example's section aren't using your GPU, they're all using CanvasRenderer it seems.

ashleyw• 16 years ago

It seems to be capped at 60FPS. But it's the simplest demo, my results for the others are nowhere near 60FPS, most aren't even usable unfortunately.

nkassis5• 16 years ago

I get 1FPS on the terrain generation one. Still cool :)

izendejas• 16 years ago

fwiw, i managed 61 fps on a karmic machine w/ i7.

and out of curiosity i tried a froyo powered device (droid 2.2) and got up to 26 fps.

chegra• 16 years ago

I think they could improve the speed if they used webworker

jat850• 16 years ago

I really only glanced at the code so I could be wrong here. But it appeared to me as though the main loop was written with something like, 1000 / 60, which was probably intended to cap at 60fps.

If you took that code and modified the loop to run more frequently, do you get even better performance?

rbreve• 16 years ago

mrdoob is a genius

kylemathews• 16 years ago

What's really crazy is how well these demos work on my Android phone.

nickpinkston• 16 years ago

Yea - there's a great project using this for parametric 3D design in the browser: http://CloudScad.com. Has the ability to produce 3D printable files too.

snissn• 16 years ago

can i make 3-d surface plots with this library? are there any alternatives to facilitate that?

RobLach• 16 years ago

Excellent Demos. The speeds these browser implementations are reaching are far better than I originally expected us to be at this point.

Three.js: JavaScript 3D engine for canvas, svg, and WebGL

Related Stories