sandey/blender
1
0
Fork 0
forked from bartvdbraak/blender
Code Pull Requests Activity

Removed ancient (2.1) feature for Constraints... a highly undocumented and

Browse Source 
unpredictable one!

This is what it did; if two or more Constraints are of the same type, it
accumulates the Target positions/rotations for the constraints, averages
them, and then only applies the last Constraint in the row. It seems to
be a trick to blend IK Constraints or so... in all other cases I cannot
find a good use for it (nor did Bassam).

For example; add three Empties, and make one Empty to have 2 location
constraints to the other two. This just didn't work, unless you insert
an "Empty" constraint inbetween.
I will post in the blender.org animation forum feedback for it too. :)

Its quite easy to make it an option, but I first like to grasp fully what
the actual use of such an option is.
This commit is contained in:
Ton Roosendaal 2005-09-28 10:07:54 +00:00
parent 97d749a99f
commit c8a4f20fb8
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/blender/blenkernel/intern/object.c
View File

@ -1574,9 +1574,11 @@ void solve_constraints (Object *ob, short obtype, void *obdata, float ctime)
aquat[0]+=(quat[0])*enf;
Mat4CpyMat4(lastmat, focusmat);
/* removed for now, probably becomes option? (ton) */
/* If the next constraint is not the same type (or there isn't one),
* then evaluate the accumulator & request a clear */
if ((!con->next)||(con->next && con->next->type!=con->type)) {
if (TRUE) { //(!con->next)||(con->next && con->next->type!=con->type)) {
clear= 1;
Mat4CpyMat4(oldmat, ob->obmat);