Warp <war### [at] tagpovrayorg> wrote:
>   Deciding what goes where is not the task for a raytracer.

POV-Ray isn't only a raytracer. It also have script editor and language with
weak animation support. These are not features of raytracer. Are you trying
to say that POV-Ray should take XML source input and output only one frame?
Or how about making POV-Ray to compliant RenderMan standard?

However, rendering motion blur requires knowing how objects are moving and
efficient way to do this is using extra rays than blending raytraced frames
together. It is also efficient to parse scene only once in animation, so
rendering engine should understand animations and making decisions how
objects are moving.

POV-Ray's biggest problem is weak animation support. It is useful mainly for
still pictures.

Matti

Post a reply to this message