- User Since
- Dec 11 2009, 1:17 PM (513 w, 3 d)
Sep 2 2019
Probably not. It now certainly does what I was asking for when Campbell created this task.
Feb 9 2016
Yup, just tried it in a recent build and found that option.
Apr 7 2015
It would be good to double check that. Rigify rigs use transforms for posing, and custom props for properties, like IK/FK and hinges, which you don't need to be included in the breakdowner..
From memory, the Sintel rig did indeed use custom properties for facial stuff. However, I can't double check that now, as last time I checked, the Sintel rig didn't work in the current Blender.
Mar 27 2015
On further investigation, this is to do with the window manager xfce overtaking the shortcut.
Mar 24 2015
Apr 16 2014
Neat. That would do the trick for me.
In my opinion, yes.
Alternatively, maybe a toggle switch in the user prefs or on the timeline (beside the play/next buttons)?
Apr 15 2014
ddjef sums it up quite well.
The "next keyframe" controls should be limited to the current selection.
Mar 19 2014
Works for me. Thanks aligorith!
Mar 18 2014
I just checked my file in 2.70 RC2 and can confirm the bug isn't there.
Not sure how the RCs work, but the last build where I saw the bug was eaf387b, which I downloaded and built as I posted my first comment.
Ok... excuse the size (it's 3.4Mb)
I'm having the same problem. It seems there is something quite wrong with how blender assesses drivers at the moment.
I've attached a comparative screenshot showing the same file in Blender 2.70 (211f08d) and Blender 2.69.
In this case it's not an action constraint, but a shape key driven by the Y scale of a bone.
Mar 17 2014
This would be great to get fixed soon!
Oops... just found a duplicate report. Sorry!