motion Graph editor
Moderators: Víctor Paredes, Belgarath, slowtiger
-
- Posts: 4
- Joined: Tue Dec 20, 2005 11:05 pm
- Location: Portland
- Contact:
motion Graph editor
motion Graph editor similar to Maya
-
- Posts: 2
- Joined: Tue Dec 13, 2005 5:00 am
In effect, this would mean that the current set of discrete interpolation types (smooth, linear, ease in/out, ease in, ease out, step, noisy, cycle) should be replaced by an interpolation where the user defines a graph which in turn defines the interpolation going from one key to another. The current interpolation types would then be presets to that function, to keep Moho backward compatible.
The only problem I see is in cycle, because that isn't really an interpolation between two keys, but a loop instruction. So cycle would have to be a separate case (as an algorithm).
A solution could be to have the following options for interpolation types:
- smooth
- linear
- ease in/out
- ease in
- ease out
- step
- noisy
- user defined
- cycle
Selecting the user defined option would open a secondary window showing a user definable key interpolation function.
The only problem I see is in cycle, because that isn't really an interpolation between two keys, but a loop instruction. So cycle would have to be a separate case (as an algorithm).
A solution could be to have the following options for interpolation types:
- smooth
- linear
- ease in/out
- ease in
- ease out
- step
- noisy
- user defined
- cycle
Selecting the user defined option would open a secondary window showing a user definable key interpolation function.
Thanks for reminding me - I forgot to post the side comment from my Bug report (on Ease in/out problems) .Rasheed wrote: - step
At the moment, STEP holds the key until the next keyframe. This fuction is commonly know as a HOLD.
It is better therefore, to split the existing STEP option into two new fuctions:
HOLD - this does what step does now, holds the keyframe postion until the next key frame is encountered.
STEP BY ... - a new function where the position "steps" over a user-defined number of frames (the default should be 2). This is vital when the animation is on twos and the background or camera is panning on singles ... the resulting "cometting" or "bulleting" is not nice on the eye. By putting the pan on two's, the problem goes away.
Both functions should be easy to code.
Rhoel
I incorporated "STEP BY" into my "CC: Paste Curve to Points Position" script which might help a little.Rhoel wrote: STEP BY ... - a new function where the position "steps" over a user-defined number of frames (the default should be 2). This is vital when the animation is on twos and the background or camera is panning on singles ... the resulting "cometting" or "bulleting" is not nice on the eye. By putting the pan on two's, the problem goes away.
See your other thread: http://www.lostmarble.com/forum/viewtop ... highlight=