Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I noticed something : when the viewpoint is lookint at a flying block wich is not that big, it's lagging the same as looking at the entire world. Is is rendering something in the background which is out of the view ? I'm not saying it's not a nice demo, actually I like the feeling very much. This perlin noise is pretty enjoyable. But I can't understand why it's that slow ;(


> I noticed something : when the viewpoint is lookint at a flying block wich is not that big, it's lagging the same as looking at the entire world. Is is rendering something in the background which is out of the view?

Yes it is. I have experimental frustum culling implemented but something with the coordinates is wrong and it starts to cull things it should not.

> But I can't understand why it's that slow ;(

Because it's work in progress and in many parts the implementation is just not finished yet. I need to fix the frustum culling, I have to improve the front to back rendering, have to switch to transferred objects for the web workers where possible, speed up the critical code paths and fix the Chrome performance bugs that come from too many VBO switches.


Doing a fast 3D engine is hard, even if most of the 3D is done for you. It's slow because it's simple, and because JavaScript is actually a fairly hard language to do some of this quickly in.

Also because web workers don't work great yet.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: