Constraints and Actionstrips do not play well together, it seems. I have long known that constraints become part of actions if inserted in certain ways, even though they do not get those dots that Loc, Rot or other Bone elements do. They just clearly get copied when I copy an action. So I guess question one is which one constraints want to be: Part of an action, or not part of an action?
But the biggie that made me post this time is that constraints apparently have NO knowledge of where they belong, because I did the following:
1: Had two identical armatures made (one independent copy of another).
2: One action made, and applied to both armatures (i.e. the action is identical, change in one changes the other)
3: Two seperate sets of constraints made for the armatures, doing the same thing, simply because doing it for one armature had no effect on the other.
4: Inserted keys in all Constraints to take them from 0.0 to 1.0 over the course of 10 frames, the exact same 10 frames for every Constraint.
I got this, and lots of it:
Notice how what the IPO says the Constraint is in that frame (0.0) is not what the Constraint says it is. Constraint influences seem to somehow mangle each other, making them go both up and down even though they are only set to go up. The rest is Blender decided that, heck no, this baby is going down, then up, then down, then up. And I cannot change it; if I insert a keyframe of 0.0 influence, Blender just decides that, heck no, it’s going to be 0.787, then go down, then up.
It makes no sense. It has to be a serious, malicious, devious bug. Please help me…