While working on a Third version on my 4x4 Autodrive system, I have encountered a
Very weird behaviour of a Limit Location Constraint.
I have put on these links below two Blend files. They are indentical, except the fact that one has been saved with the Limit Location set with its influence factor to 1.0, and the other one has been saved with the Limit Location set with its influence factor to 0.0.
The constraint (look at the right upper corner of the screen) is applied to the red object named Axle-Front. You can check the effect of the constraint by going one frame forward. When the constraint is not efficient, the whole system is delayed and the red object named Axle-Rear appears separated from the blue object named Bar-Rear.
- When the file is saved with the influence of the constraint set to 0, when you reload the file the constraint does its work only if you set it to 1 : normal behaviour.
But you can notice 2 abnormal things :
When the file is saved with the influence of the constraint set to 1, when you reload the file, the constraint does its work only if it is set to 0 !
If you have saved the file with the constraint set to 1, as the constraints works correctly with the influence set to 0 when you re-open the file, you could expect that the constraint is useless.
So, try to delete the constraint. You will see that it doesn’t work : The unwanted delay in the rig appears again ! :eek:
What do you thing about this problem ?
Thanks in advance for any idea. Do you think it’s a bug ?