Offset (Animation) Curve

Post Reply
User avatar
gustavoeb
Moderator
Posts: 587
Joined: 21 Jul 2010, 00:33
Skype: gustavoboehs

Offset (Animation) Curve

Post by gustavoeb » 11 Dec 2012, 04:09

Hi guys, Ive created this to emulate a behaviour from 3ds Max ( :ymsick: ). When it is toggled it will offset your animation if you move the object around, instead of whaiting for you to key it. The whole curve is offseted. It is very pratical, I think.

Here is a little video showing what it is good for:
[vim]https://vimeo.com/55324201[/vim]

And here is the link:
https://dl.dropbox.com/u/39280733/Offse ... s.xsiaddon

note1: you can toggle offset on under Preferences > Custom > Offset Curves, or through the included toolbar. You can also doc the toolbar in your interface, like i did in the video
Gustavo Eggert Boehs
Blog: http://www.gustavoeb.com.br/

Ramon
Posts: 111
Joined: 19 Aug 2010, 22:47

Re: Offset (Animation) Curve

Post by Ramon » 11 Dec 2012, 10:56

gr8

User avatar
druitre
Posts: 471
Joined: 25 Jun 2009, 23:35

Re: Offset (Animation) Curve

Post by druitre » 17 Dec 2012, 11:05

Hi Gustavo,

thanks for the addon, good idea. I'm experiencing issues, though (2013 SP1):

When I start up SI, even though under preferences I've unchecked your addon, SI keys as if it's active. I have to first open prefs>custom>check the box in your addon, then place a key, then uncheck the box, and only then does SI recognize the addon is inactive.

Also, keying a rigged character with the addon active is very slow - takes about 2-3 seconds before becomes responsive after hitting 'k'. (Tested with standard Male Species-rig)

Can you or anyone elese confirm these and (especially for the first issue) help find a solution?

Thanks, Jasper

User avatar
gustavoeb
Moderator
Posts: 587
Joined: 21 Jul 2010, 00:33
Skype: gustavoboehs

Re: Offset (Animation) Curve

Post by gustavoeb » 17 Dec 2012, 19:17

At the moment this is being evaluated from a callback which is called OnValueChanged, when one moves a control in a slighly complex rig probably maaany values change. I have tried to avoid this by avoiding the evaluation of objects that dont have fcurves, and of values that are not related to transformations.
I really thought speed could be a problem, but I was excited to share this as it is the first time I code something in Python in a slightly "hieginic" way.
Ill try messing around with some rigs soon (away from home now), also need to check this problems with the preferences you talk about.
Thanks for sharing your experiences with this...

By the way anyone with experience in optimizing this Python callbacks?
Gustavo Eggert Boehs
Blog: http://www.gustavoeb.com.br/

Post Reply

Who is online

Users browsing this forum: No registered users and 52 guests