> But 2.75 hrs!! Sheesh.

I couldn't agree more.

I was watching the statistics right before the actual render started to go
and it was well over 20 billion tokens parsed.
The scanning algorithm had to work through 150^3 points using inside(...)
and for each point that was inside the object, it would compare with its 8
neighbors too determine whether it was on the surface.

Its all just some un-useless code that I'll use for a larger project later.
But it looks like this part works great, albeit freaky slow.

Post a reply to this message