This site contains adult imagery and is not suitable for people below 18 years of age.

By using this site, you attest that you're 18 years or older.

This site also uses cookies, but only for functions related to the site, such as storing sessions and user choices.

We do not put tracking cookies on your computer.

Sending request ...

Copy/duplicate as initialized change

The idea of the 'as initialized' options for new steps is great, but I find that in practice it often just causes more work.

For me the most efficient way to animate is to make a couple of timelines+drivers for common things like moaning, hand gestures, sway etc. that are kept for multiple steps or even throughout a scene. The weight, speed and driver properties are then altered per step to fit that step's needs.

With this setup, if a new step is created 'as initialized' it will copy the keyframes of these looping timelines which is undesirable and then needs to be manually corrected.

I thought of two fairly straightforward changes that will make creating new steps 'as initialized' behave more like how I would expect it to:
- Only keyframes from timelines with weight > 0 are copied
- Only keyframes from timelines with interpolation mode 'clamped' are copied.

This would allow one to continue with 'story'-like timelines (that should be clamped) while ignoring the looping that happens within a step.

Developer response

Implemented with Build 2025-05-01

-Blacky

Comments
V2lsbCBsb29rIGludG8uIEZlZWxzIGFsbW9zdCBsaWtlIGEgYnVnIG9yIGF0IHRoZSB2ZXJ5IGxlYXN0IHVuZGVzaXJhYmxlIGJlaGF2aW9yLg==

Will look into. Feels almost like a bug or at the very least undesirable behavior.

4 months, 3 weeks ago
SW1wbGVtZW50ZWQgZm9yIG5leHQgcmVsZWFzZS4=

Implemented for next release.

4 months, 3 weeks ago

0

vote sum by 0 users.
Suggestion status
Implemented.
Spend votes
Suggester
4 months, 3 weeks ago