motion Graph editor

Discuss ideas for new features with other users. To submit feature requests to Smith Micro, please visit support.smithmicro.com

Moderators: Víctor Paredes, Belgarath, slowtiger

Post Reply
allansteele
Posts: 4
Joined: Tue Dec 20, 2005 11:05 pm
Location: Portland
Contact:

motion Graph editor

Post by allansteele »

motion Graph editor similar to Maya
cgCharAnimator
Posts: 2
Joined: Tue Dec 13, 2005 5:00 am

Post by cgCharAnimator »

hoo-yeah! That would be the best! The current graph editor UI is ... a little wonky.
User avatar
Rhoel
Posts: 844
Joined: Fri Feb 25, 2005 8:09 am
Location: Phnom Penh, Cambodia
Contact:

Post by Rhoel »

If by "the way Maya works" you mean including the kind of little bezier handles that 3D max has, I'm up for it too ... you can have total control then of the way actions happen.

Try getting the standard bouncing ball test to look right with the current controls :) ... you can't.
User avatar
Rasheed
Posts: 2008
Joined: Tue May 17, 2005 8:30 am
Location: The Netherlands

Post by Rasheed »

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.
User avatar
Rhoel
Posts: 844
Joined: Fri Feb 25, 2005 8:09 am
Location: Phnom Penh, Cambodia
Contact:

Post by Rhoel »

Rasheed wrote: - step
Thanks for reminding me - I forgot to post the side comment from my Bug report (on Ease in/out problems) .

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
macton
Posts: 93
Joined: Thu Aug 18, 2005 6:29 am
Location: San Diego

Post by macton »

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.
I incorporated "STEP BY" into my "CC: Paste Curve to Points Position" script which might help a little.
See your other thread: http://www.lostmarble.com/forum/viewtop ... highlight=
Post Reply