In article <39f33152@news.povray.org>, "Tony[B]" 
<ben### [at] panamac-comnet> wrote:

> Why?

Because motion_blur works by parsing the block multiple times, changing 
the clock variable slightly each time. If a variable is declared outside 
that block, it is parsed once and the result fed into the block. Since 
this value doesn't rely on the blurred clock, all the copies of whatever 
is affected by the blur are exactly the same.


> Can't this be fixed?

Probably...but only by parsing the entire scene file multiple times. And 
this would probably eliminate the possibility of having separate 
motion_blur blocks with different quality levels, would make parsing 
much slower, would require rewriting a large portion of the existing 
motion blur code, would be more difficult to implement, and finally, 
isn't really something that *should* be "fixed". The way it is is(don't 
you just *love* English?) far more flexible, it gives you much more 
control of what actually goes on. If you want something animated but not 
blurred, no problem: just save the clock value in a variable outside the 
motion_blur block.

Sorry, but it isn't a bug, just a misunderstanding on your part.

-- 
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/

<><

Post a reply to this message