|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|
|
|
|
|
|
|||||||||
|
|
||||||||||||||
|
|
||||||||||||||
|
|
||||||||||||||
|
|
|
|||||||||||||
|
|
|
|
|
|
|
|||||||||
|
BryceTalk Camera Discussion
|
BryceTalk Camera Discussion, June 29, 1999
|
|
|
AuntiAlias: When it comes to animation of an object -- any object... in Bryce... there are two ways to move in space.... The first is trajectory AuntiAlias: that's what you make automatically when you have autokey on, and you move time scrubber, then move object.. and bryce automagically interpolates between first and second position AuntiAlias: that's the smooth gray line with blue points where keys are.... called a Trajectory... I was looking at the Bryce manual, and it tends to call it a path... however.... in the tutorial I wrote for the manual AuntiAlias: (which starts on page 95, I believe) I make a distinction between the trajectory and that other thing, which is called an object path the idea here is this: you can use keyframes to create an object's motion geometry in space that is, its POSITION AuntiAlias: it goes from point A to B to C to D... AuntiAlias: and, depending on the need, you may have as many points in there as you need to define the shape of the trajectory AuntiAlias: if there are curves, you need more "points" than you need for a straight line so... AuntiAlias: that's all well and good for establishing where the object (object, by the way, DOES include Camera) is in space over time but on the whole, the time element is not as smooth..... so.... that's at the point where you convert the trajectory to an object path Under Objects menu, "Create Object Path" oops... "Create Path" Once you do that.... you have to go back and refine the time element all over again First thing you do is to link the object to the path so that it is constrained to the path two ways of doing so select object: and object icons appear... the diagonal one (like a chain link) is the one that you drag from... TO the path... because the path is small and thin, though... sometimes it's not easy to "hit" it (when you do HIT it, it'll turn blue) so.. you use the other method.. the object attributes dialog box. Second panel in dialog box is "Linking" At the top, there's an area for Object Parent Name with a pop-up menu. so... you scroll in the pop-up menu for Path 1 (assuming that this is the only path you have in your scene) and select Path 1 Once you have a path there, you got more options that appear in the dialog box. (hang on a sec while I do this, so I can describe it accurately) AuntiAlias: It says "constrain to path" and there's a numerical entry box and a set of arrows now... waht constrain means is this it's the position along the path.. the path's beginning and the path's end. One end is 0 and the other end is 100 AuntiAlias: so to move the object along that path over time, you go to time 00:00:00.0 and then place the object at position 0 then move to other end of your timeline (however much that is) and then move the object to position 100 oh.. and make sure to "add keyframe" at each of those times so... you object whether camera.... or null sphere or other object gdmsynth: ? AuntiAlias: oops... your object... moves along a more complex geometry (the path) over two keyframes of time time 0 ... time 1 for smooth movement.... AuntiAlias: you can have more than 1 object constrained to the same path you can have both null object and visible object that way, for instance... but moving at different speeds, for instance and you can scale the path.. or move points on the path over time.... or move the entire path over time! you can constrain one path to another path and you can have camera move on yet another path, tracking a moving object on a parallel path..... the idea here is that you are separating the geometry (where the object moves) from the time element in order to create smooth movement over time once you do that, you get a lot more control and power out of animating things AuntiAlias: and working with the curves in the Advanced Motion Lab (AML) gets to making more sense gdm, your question? gdmsynth: Why does motion along a trajectory in a straight line from A-B run at a different speed than when the trajectory is converted to a path? AuntiAlias: hmmm.. the same trajectory? first as trajectory, then as converted to path? gdmsynth: Yes. AuntiAlias: I don't know exactly.. I'd have to look at the case in question... but I can think of ideas.... such as... are you really at point 0 and at poitns 100 at the beginning and end? gdmsynth: Seems to speed up and slow down at the beginning and ends on a trajectory. AuntiAlias: are you talking about identical time span? or.. gdmsynth: Yes, yes. AuntiAlias: if you've done ease-in-ease-out curves, then, well, there you are!! AuntiAlias: that's where the curves in AML do come in handy DigiVI: gdmsynth: No. Not with any ease in out. If you think not, I'll go back and check it later. AuntiAlias: you'd have to have a straight digonal curve in AML for consistent speed which, by the way, looks very computerish... ease in ease out looks more natural to the eye okay... gdmsynth: Yes no changes to the TimeMapping AuntiAlias: then I don't know the answer to your question, gdmsynth....
>>>> Next up: Tension, Bias and Curve |
|
|
Opinions expressed in this BryceTalk Event belong to
the individuals who stated them;
|
