Seems odd that the only way 'motion_blur'  works is to use the keyword
'clock' and nothing else.  Is this intended?  I guess it was not written up
to accept anything else, user defined, such as Clock or MotionClock, etc.
for the transformations.
May as well say that it sure is a great new feature though while I'm talking
about it, and ask if this might become independant of the global settings in
a future version.

Bob
--
// omniVERSE
// http://users.aol.com/inversez/

Post a reply to this message

The way it works is by re-parsing that object multiple times with multiple
clock values.  I would be very difficult for it to to 'know' which variables
the user is treating like the clock and even more difficult to know how to
modify those variables in the way the user would want them modified.  If you
put your #declare C=clock; WITHIN the motion_blur object, then C things will
probably work the way you expect.

-Nathan

omniVERSE <inv### [at] aolcom> wrote...
> Seems odd that the only way 'motion_blur'  works is to use the keyword
> 'clock' and nothing else.  Is this intended?  I guess it was not written
up
> to accept anything else, user defined, such as Clock or MotionClock, etc.
> for the transformations.
> May as well say that it sure is a great new feature though while I'm
talking
> about it, and ask if this might become independant of the global settings
in
> a future version.
>
> Bob
> --
> // omniVERSE
> // http://users.aol.com/inversez/
>
>
>

Post a reply to this message

I've used things like #declare CM = (1-clock) many times with the motion blur
object, inside and out, and I've never had a problem. Go figure.
Keep up the good work!

H.E. Day

Nathan Kopp wrote:

> The way it works is by re-parsing that object multiple times with multiple
> clock values.  I would be very difficult for it to to 'know' which variables
> the user is treating like the clock and even more difficult to know how to
> modify those variables in the way the user would want them modified.  If you
> put your #declare C=clock; WITHIN the motion_blur object, then C things will
> probably work the way you expect.
>
> -Nathan
>
> omniVERSE <inv### [at] aolcom> wrote...
> > Seems odd that the only way 'motion_blur'  works is to use the keyword
> > 'clock' and nothing else.  Is this intended?  I guess it was not written
> up
> > to accept anything else, user defined, such as Clock or MotionClock, etc.
> > for the transformations.
> > May as well say that it sure is a great new feature though while I'm
> talking
> > about it, and ask if this might become independant of the global settings
> in
> > a future version.
> >
> > Bob
> > --
> > // omniVERSE
> > // http://users.aol.com/inversez/
> >
> >
> >

Post a reply to this message

Thanks for that info Nathan, it does do right when inside the statement
itself.
However, I have to wonder what H.E. is getting there with it working inside
or out, I just rechecked again and it does not see the defined C=clock sort
of way when not included into the motion_blur.  Win98SE used here and of
course the Windows version of MegaPOV, could it be platform dependant?
Wouldn't think so...

Bob

"H.E. Day" <mil### [at] teleportcom> wrote in message
news:385878DD.2D6E16F3@teleport.com...
> I've used things like #declare CM = (1-clock) many times with the motion
blur
> object, inside and out, and I've never had a problem. Go figure.
> Keep up the good work!
>
> H.E. Day
>
> Nathan Kopp wrote:
>
> > The way it works is by re-parsing that object multiple times with
multiple
> > clock values.  I would be very difficult for it to to 'know' which
variables
> > the user is treating like the clock and even more difficult to know how
to
> > modify those variables in the way the user would want them modified.  If
you
> > put your #declare C=clock; WITHIN the motion_blur object, then C things
will
> > probably work the way you expect.
> >
> > -Nathan
> >
> > omniVERSE <inv### [at] aolcom> wrote...
> > > Seems odd that the only way 'motion_blur'  works is to use the keyword
> > > 'clock' and nothing else.  Is this intended?  I guess it was not
written
> > up
> > > to accept anything else, user defined, such as Clock or MotionClock,
etc.
> > > for the transformations.
> > > May as well say that it sure is a great new feature though while I'm
> > talking
> > > about it, and ask if this might become independant of the global
settings
> > in
> > > a future version.
> > >
> > > Bob
> > > --
> > > // omniVERSE
> > > // http://users.aol.com/inversez/
> > >
> > >
> > >
>

Post a reply to this message