jbills
04-18-2005, 04:42 PM
not sure if someone has suggested it yet - surely - but it would be nice to have a shape parenting feature of some kind.
I'm just not quite sure how this might be implemented?
In most other programs, the groundwork is laid to have axis or transform keyframes seperate from shape keyframes. Currently the two are joined in s+r. So, I'm not sure how parenting might work.
If the separation exists, then you just parent the "axis" of a shape to another shape and you're done. But it's hard to parent shape keyframes to another shape, as points move differently. I guess you might be able to parent the center of the shape or something?
Really, I think it might be good to break out axis (and I say axis meaning position, scale, rotation - axis is a term that comes from discreet products - sorry) and shape keyframes seperately to provide this sort of functionality. This would allow some powerful tracker interaction as well, as you could use trackers to move shapes but not set shape keyframes. Shake has it so you can bake trackers into the shape keys, which is nice - but I'm not sure this would be necessary if everything was seperate. Baking is really a workaround because things behave unpredictably at times in shake and sometimes the only solution is to bake the movement in because something's whacked with their parenting code and how it interacts with rotoshapes.
What also might be good is if you could somehow parent a shape to another but limit the parenting to a certain timeframe. So say I had a goose feather that I wanted to parent to an existing hat spline, but only for so long. It *might* be cumbersome to have to duplicate a spline to break that parented relationship. Might be nice to be able to define a time range for the parenting relationship. I'm not sure - would have to work with it both ways and see what is easier.
But would love to see something like this in the future? Just throwing it out, maybe others can chip in some features along this line of thinking - haven't thought it through much.
Thanks!
I'm just not quite sure how this might be implemented?
In most other programs, the groundwork is laid to have axis or transform keyframes seperate from shape keyframes. Currently the two are joined in s+r. So, I'm not sure how parenting might work.
If the separation exists, then you just parent the "axis" of a shape to another shape and you're done. But it's hard to parent shape keyframes to another shape, as points move differently. I guess you might be able to parent the center of the shape or something?
Really, I think it might be good to break out axis (and I say axis meaning position, scale, rotation - axis is a term that comes from discreet products - sorry) and shape keyframes seperately to provide this sort of functionality. This would allow some powerful tracker interaction as well, as you could use trackers to move shapes but not set shape keyframes. Shake has it so you can bake trackers into the shape keys, which is nice - but I'm not sure this would be necessary if everything was seperate. Baking is really a workaround because things behave unpredictably at times in shake and sometimes the only solution is to bake the movement in because something's whacked with their parenting code and how it interacts with rotoshapes.
What also might be good is if you could somehow parent a shape to another but limit the parenting to a certain timeframe. So say I had a goose feather that I wanted to parent to an existing hat spline, but only for so long. It *might* be cumbersome to have to duplicate a spline to break that parented relationship. Might be nice to be able to define a time range for the parenting relationship. I'm not sure - would have to work with it both ways and see what is easier.
But would love to see something like this in the future? Just throwing it out, maybe others can chip in some features along this line of thinking - haven't thought it through much.
Thanks!