I like the talk of this becoming a potential feature, even if way off into a
future version or patch.  Something to consider would be how texture is
applied to such objects, or all of the scene in the case of camera movement.
The multiplications cause a lot of overlapping texture to occur and that has
to be adjusted for.  I think some of the image averaging procedures account
for this from what I remember was said before.  Within POV-Ray itself
however there would need to be similar adjustment since each still image is
in fact a series of images of a sort.
Don't want to put a damper on the subject, just wanted to be sure that this
also was thought about. And I guess this is where I came in, the talk of
collecting color info for the object(s).
Btw, I know nothing of programming in here.  I had only done my own "in-pov"
tests of motion blur and found the need to either csg difference or tone the
texture color down while a object moves.
I'll let you all continue now and leave you with it  ; )

Bob

Goran Begicevic <gor### [at] tidaxse> wrote in message
news:38401830.B80A56D8@tidax.se...
> > Sounds like you'd still have the problem caused by shadows, reflections
and
> > refraction.
>
>
> Hmmm...i don't think i will. Could you please point out why? I cannot
> think of any problem here.
>
>
> Let's do a mind-experiment. Ray is being shot from camera. Ray
> intersects cube in the scene. Vector is calculated from
> intersection-point to light_source and checked to all object in scene to
> see if intersection-point is obscured by anything (in shadow).
>
> Now, if there is a motion-blur object between our cube and light_source
> we should use same approach as if our blur-object is intersected by
> camera-ray. Object is jittered in time domain, some value between fully
> obscured and fully lighted is obtained , and that value is used to
> determine color of that pixel.
>
> Correct me if i'm wrong.
>
>
>
> Cheers, Goran

Post a reply to this message