Re:Show HN: 3DTin - 3D modelling in browser
by jayeshsalvi on Monday January 10, 2011 @12:22PM
(#2089045)
3DTin does use Web Workers. However the smoothing algorithms generate too much data if there are lot of cubes and/or the smoothness is high, that makes the tab/browser unresponsive. The problem of vanished parts of the model at higher smoothness is a known one (happens when WebGL is the backend). I've further optimizations planned in the near future that should improve the performance gradually and fix the bugs like vanished parts. Stay tuned. Thanks for the feedback.
-3DTin Developer
Re:Show HN: 3DTin - 3D modelling in browser
by malkia on Monday January 10, 2011 @01:44PM
(#2089304)
I think smoothing of ONE is just fine - Maybe you should just leave at that.
Cool app :) - Lots to learn from it (using WebGL, etc.).
Before looking in the source code - was something like marching cubes used for the smoothing?
Re:Show HN: 3DTin - 3D modelling in browser
by jayeshsalvi on Monday January 10, 2011 @08:20PM
(#2090457)
3DTin uses Catmull-Clark subdivision to create smooth surfaces. Details here: http://blog.3dtin.com/smoothing-or-subsurfacing - 3DTin Developer
One particularly strange bug: Setting smoothness 'too high' (how high you can set it seems to depend on the number of cubes) causes random parts of the model to vanish.
The responsiveness also leaves something to be desired, especially since it causes the browser/tab to freeze up - I thought it was supposed to be possible to use web workers to solve that problem, but I've yet to see a HTML5 app that actually uses them :(