Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Animation Editors - Set Keyframe Type to be not only an act-once operation but a "setting". #4239

Open
Draise14 opened this issue May 3, 2024 · 1 comment
Labels
Experimental Something to try out

Comments

@Draise14
Copy link
Collaborator

Draise14 commented May 3, 2024

image
image

When you set a keyframe to a certain type, you would expect any following new keyframes to be of the same time (extreme, hold, etc) - but it only "sets" the keyframe type once.. these are not settings but act-once operators.

Typically as an animator you animate first in extremes, pose to pose, then breakdowns, then moving holds, then jitter and the like.. in stages, so having to repeatedly set your key types as you work over and over is a big time suck.

Current workflow

  1. Create keys

  2. Select keys

  3. Set key type

  4. Make new keys

  5. Select keys

  6. Set key type (often the same kind due to the nature of animation)

  7. And to continue into a new mode, you then repeate this process over and over as you make keys.

Rinse and repeat.

Proposed workflow

  1. Set key type

  2. Make new keys

  3. Notice you're in the right key type "mode"

  4. Change key type, key in that "mode" then carry on in a new "mode" of keyframing types.

Benefits

  • Will allow an animator to keyframe in an organized way from the beginning, without the extra cost of select+set+select+set in a big field of keys
  • Will allow animation supervision to be much easier since it won't be any extra cost to "label" your keyframes on animation as you work the process.
  • Will assist to be visually organized keyframes in the dopesheet to later adjust easily
@Draise14 Draise14 added the 0 - task A normal development task label May 3, 2024
@Draise14
Copy link
Collaborator Author

Draise14 commented May 3, 2024

image

I wonder if it would make sense to have these not as a global preference, but a per project preference or something.... and have the three keyframe types as "modes" as a preference.

We already have two doing a default, which is great, but it would be nicer if the default "mode" changed directly from header.

@Draise14 Draise14 added Experimental Something to try out and removed 0 - task A normal development task labels May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Experimental Something to try out
Projects
None yet
Development

No branches or pull requests

1 participant