Warp <war### [at] tagpovrayorg> wrote:
> Mike Raiford <"m[raiford]!at"@gmail.com> wrote:
> > I don't really know if it needs to be included in POV-Ray, though.
> > Rigging up an animation, and averaging the frames isn't that tough to
> > do, and you'd still need to rig the animation to do it properly anyway.
> > So, it just takes the step of averaging the images out.
>
> > Unless, of course, I'm seriously missing something here.
>
>   With internal support the rendertime can be considerably faster because
> only the moving parts are rendered many times, not the whole image. With
> the averaging-frames trick you'll have to render the entire image for each
> frame, and additionally you need some software to post-process the result.
>
> --
>                                                           - Warp

Exactly Warp, that's why MegaPov is so handy - if you want to spin an airplane
prop it renders only that specific area and averages the result automatically.

I spent a couple of hours with the motion blur code last night and made some
good progress. But I found that Chris and Thorsten have made some changes to
the base code in migrating to multithreaded C++ classes (big improvement
guys!), so it stalled me a bit. Some of the old functions were transitioned
into class methods with similar names, so no big deal. But some of them (and
even whole files, e.g., lighting.cpp) have disappeared completely, so looks
like I'll need to spend a few nights reviewing the changes so I can get a
handle on the new pipeline.

-Rob

Post a reply to this message