Le Forgeron <jgr### [at] freelocalhost> wrote:
> Did it perform well ?

  Much better than your suggestion.

  There was absolutely no limitation on how the object could move and
what kind of material it could have (it was perfectly ok for it to
be transparent and refractive, it still gave the correct result).

  The idea was simple:
  You specified with a special block how many samples you want to take
and then used the 'clock' identifier (which goes from 0 to 1) in the
object definition to define its transformations or whatever. The engine
would then internally create as many copies of the objects as the number
of samples specified (each one of them with a different 'clock').
  For each ray that hits any of the bounding boxes of the moving object,
the ray is traced against every internal copy of the object and the
results are averaged.

  If you used enough samples, the result would be perfect.

> Was there any problem ?

  Not really. The result was practically perfect, but the team decided
that it was a too specific effect and that they wanted to develop a
more generic solution for pov4 (a solution which would probably allow
to make many diverse effects, such as motion blur, blurred reflection,
blurred refraction and many others).

> You mentioned "older" MegaPov: does it means it was not reported ? has-it 
> been superceded by a better system ?

  It just means that it has not yet been included in the newer megapov.

-- 
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}//  - Warp -

Post a reply to this message