#Path bug in 3.1, 3.2
4 messages in this thread
I found a very annoying bug in Imagine 3.2 today. Objects set to follow paths
will not start at the begining of the path (although they do end at the end of
the path). I took the project back to version 3.0, and the path worked as it is
supposed to, with the object starting at the begining at the path. Going back
to version 3.0 brought out another annoyance; the object's brush maps,
assembled in 3.2, were upside down in version 3.0.
Impulse promised to look into it.
David,
I just tried the object following the path in 3.2, and yep…it doesn't start
at the beginning og the path. It starts at the next interpolated position.
For now, if you still want to use 3.2, you can use this workaround:
For example purposes I'll use a 30 frame anim.
Position the object at the beginning of the path object in frame 1, but do not
have the object's position set to follow the path (ie: use TWEEN position).
Now in frames 2-30 of the anim add a new position bar and have the object
follow the path. This will give you the smooth motion from beginning to end.
-GreG
I think I'm following your suggestion, and I tried some variations on this. I
still have dificulty because I am trying to use the acceleration and
deceleration features of paths as set up in the Action Editor. I need my object
to smoothly decelerate from one speed to another, and while I can get close
using workarounds with path length and start position, I can't quite get the
close-to-exact match I need. I'll go back and play with it some more, though.
Thanks for your suggestion. If I can't get it to work in 3.2 I'll just go back
to 3.0.
-David
David,
Is it really necessary to use paths at all? Can't you just set up
keyframes were you need the object to be, and let spline interpolation do
accel/decel automatically?
-Tim