It's not a bug.
I'm just saying that the actual implementation is wrong.
As you can read in the documentation the clock delta is centered around the
clock value of the current frame, which is wrong (you can't see what is
going to happen). I hope you understand what I'm focusing on.

jrg.
"Warp" <war### [at] tagpovrayorg> ha scritto nel messaggio
news:3b471c8a@news.povray.org...
> JRG <jrg### [at] hotmailcom> wrote:
> : This is also motion blurred. And it's blurred following the armonic
motion
> : of the pendulum. Yet MegaPov motion blur is not correct for what I
mentioned
> : in my previous message. Simply because I can't avoid that MegaPov
renders
> : those frames between t and t+dt/2 which I'm not supposed to see when the
> : actual time coordinate is t.
>
>   As said, you are just using the motion blur in the wrong way (ie. giving
> it the wrong parameters).
>
>   Reduce your scene to an extremely simple form (ie. just the camera, and
> a moving cylinder representing the pendulum) and post it. We can then look
> what you are doing wrong (or alternatively spot a bug in MegaPov, although
> I doubt it).
>
> --
> #macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
> rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
> ],13),8)-3,10>#end blob{N(array[6]{11117333955,
> 7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

Why don't you post a simplified scene as I asked?

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message