animation of influence property of child constraint where parent object has a rotation can be quite unintuitive. #43147

Closed
opened 2015-01-06 19:51:59 +01:00 by Robert Forsman · 11 comments

System Information
Linux bubastis 3.10.25-gentoo #10 SMP Thu Jan 30 22:17:35 UTC 2014 x86_64 Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz GenuineIntel GNU/Linux
01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) (prog-if 00 [VGA controller])

Blender Version
Broken: 2.72b
Worked: did it ever?

when animating the influence parameter of a child-of constraint to make an object move between two points the motion can end up being inexplicably non-linear when the parents are rotated.

Create two empties at different locations (e.g. [0,0,2] and [0,0,10] ) . Rotate both empties by -90d around the y axis.

Take the default cube and give it two child-of constraints. One constraint should be targeted at the first empty. It's influence should have two keyframes t0=1, influence=1 and t1=30, influence=0.

The second constraint should be targeted at the second empty. Its influence should have two keyframes t0=1, influence=0 and t1=30, influence=1.

Just to keep things simple, go into the fcurve editor and make both curves linear.

Use alt-A to start the animation. Notice how the cube follows a curved path. This is VERY nonintuitive. The same problem appears to affect child constraints targeted at the bones of armatures. The weirdness becomes even more pronounced if the object with the child constraints has a non-<0,0,0> location.

In my specific use case I'm animating an object that is alternately attached to bones, or traveling between bones in an armature. The empties appear to be an easily reproduced variation that I assume illustrates the same math oddity.

**System Information** Linux bubastis 3.10.25-gentoo #10 SMP Thu Jan 30 22:17:35 UTC 2014 x86_64 Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz GenuineIntel GNU/Linux 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) (prog-if 00 [VGA controller]) **Blender Version** Broken: 2.72b Worked: did it ever? when animating the influence parameter of a child-of constraint to make an object move between two points the motion can end up being inexplicably non-linear when the parents are rotated. Create two empties at different locations (e.g. [0,0,2] and [0,0,10] ) . Rotate both empties by -90d around the y axis. Take the default cube and give it two child-of constraints. One constraint should be targeted at the first empty. It's influence should have two keyframes t0=1, influence=1 and t1=30, influence=0. The second constraint should be targeted at the second empty. Its influence should have two keyframes t0=1, influence=0 and t1=30, influence=1. Just to keep things simple, go into the fcurve editor and make both curves linear. Use alt-A to start the animation. Notice how the cube follows a curved path. This is VERY nonintuitive. The same problem appears to affect child constraints targeted at the bones of armatures. The weirdness becomes even more pronounced if the object with the child constraints has a non-<0,0,0> location. In my specific use case I'm animating an object that is alternately attached to bones, or traveling between bones in an armature. The empties appear to be an easily reproduced variation that I assume illustrates the same math oddity.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @mutantbob

Added subscriber: @mutantbob
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Please always attach a .blend file that helps us to easily recreate the issue.

Please always attach a .blend file that helps us to easily recreate the issue.

Added subscriber: @zeauro

Added subscriber: @zeauro

Your problem is relative to empties rotation.
Position of child is relative to position and rotation of parent.

Problem is more obvious if parents have not the same rotation.

You can avoïd this simply by disabling influence of parent rotation.
constraint_rotation.blend

Your problem is relative to empties rotation. Position of child is relative to position and rotation of parent. Problem is more obvious if parents have not the same rotation. You can avoïd this simply by disabling influence of parent rotation. [constraint_rotation.blend](https://archive.blender.org/developer/F135643/constraint_rotation.blend)
Author

Disabling the influence of parent rotation is not an option. The object would be facing the wrong direction (which is pretty obvious when you use something other than the default cube or rotate by 45d instead of 90d).

As for the .blend file, I see actions for Comment, Change Status, and many others, but no Upload File. And there is no way for me to drag&drop files. I uploaded it to pastebin until the web site is upgraded:

http://www.pasteall.org/blend/33696

Questions that remain:

  • What is the mathematical reason for the oddity in the calculation?
  • Is this existing mathematical model superior for any applications?
  • Is there another model that would give less surprising results in this case and in the majority of other use cases?
  • What would break if the mathematical model were altered to give less surprising results in this case?
  • Is it worth the effort to alter the code to implement a "better" model?
Disabling the influence of parent rotation is not an option. The object would be facing the wrong direction (which is pretty obvious when you use something other than the default cube or rotate by 45d instead of 90d). As for the .blend file, I see actions for Comment, Change Status, and many others, but no Upload File. And there is no way for me to drag&drop files. I uploaded it to pastebin until the web site is upgraded: http://www.pasteall.org/blend/33696 Questions that remain: - What is the mathematical reason for the oddity in the calculation? - Is this existing mathematical model superior for any applications? - Is there another model that would give less surprising results in this case and in the majority of other use cases? - What would break if the mathematical model were altered to give less surprising results in this case? - Is it worth the effort to alter the code to implement a "better" model?

child_of_locrot.blend

When influence of child of constraint is decreasing, it is like cube was moving far away from empty location.

In this .blend, you can disable rotation influence of constraint and see the cube static.
If you keep z rotation active and disable all location influence, cube is just rotating on its own axis.

It is combined influence that produce same result than in a child-parent relationship.

Tipically child of constraint is used to attach an object on a different parent in an instant with a contact.
I have an object in the hand. I put it on the floor. Another character pick it.
It is not supposed to be used to make an object flying from my hand to the hand of the other character.

If you want to create translation and with constrained rotation, use "copy location" and "copy rotation" constraints.

[child_of_locrot.blend](https://archive.blender.org/developer/F135679/child_of_locrot.blend) When influence of child of constraint is decreasing, it is like cube was moving far away from empty location. In this .blend, you can disable rotation influence of constraint and see the cube static. If you keep z rotation active and disable all location influence, cube is just rotating on its own axis. It is combined influence that produce same result than in a child-parent relationship. Tipically child of constraint is used to attach an object on a different parent in an instant with a contact. I have an object in the hand. I put it on the floor. Another character pick it. It is not supposed to be used to make an object flying from my hand to the hand of the other character. If you want to create translation and with constrained rotation, use "copy location" and "copy rotation" constraints.
Author

After some experimentation I have developed the theory that it's because multiple child-of constraints with fractional influence are implemented by creating a transform matrix for each constraint based on the difference between the decomposed loc/rot/scale of the two parents, and attenuated by the influence.

Once these matrices are chained together, things get a little weird.

I was able to achieve the effect I wanted by separating the location/rotation constraints with the location constraints at the top of the stack and rotation at the bottom.

I'm going to vote we file this in the "undocumented oddity" bin.

After some experimentation I have developed the theory that it's because multiple child-of constraints with fractional influence are implemented by creating a transform matrix for each constraint based on the difference between the decomposed loc/rot/scale of the two parents, and attenuated by the influence. Once these matrices are chained together, things get a little weird. I was able to achieve the effect I wanted by separating the location/rotation constraints with the location constraints at the top of the stack and rotation at the bottom. I'm going to vote we file this in the "undocumented oddity" bin.
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Julian Eisel self-assigned this 2015-01-12 20:51:15 +01:00
Member

Yeah, rigging can be complicated ( /me has no clue about it) :( But anyway, looks like we don't have a bug here

Yeah, rigging can be complicated ( /me has no clue about it) :( But anyway, looks like we don't have a bug here
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#43147
No description provided.