Child bones doesn’t follow parent when IK chain length are overlapping #73262

Closed
opened 2020-01-20 13:02:47 +01:00 by Novice · 8 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 25.20.100.6472

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: 26bd5ebd42
Worked: 2.79

Short description of error
When a IK constraint passes another IK the armature get detached bones.

Exact steps for others to reproduce the error
Open blender with the default scene and remove everything.
Add armature. Tab into edit mode. Extrude a new bone. Extrude one more bone. They will all be connected to their parent.

Add a cube at the tip of the last bone and another one at the tip of the middle bone.

Tab into pose mode. Select the last bone (Bone.002). Select "Bone Constraint Properties" -> "Add Bone Constraint" -> "Inverse Kinematics". Select as target the cube at the tip of that bone. (In the blend file it's thumbIK). Change "Chain Lenght" to 2.
armature_thumbIK_chain_lenght_2.JPG

Still in pose mode select the middle bone, (Bone.001). Select "Bone Constraint Properties" -> "Add Bone Constraint" -> "Inverse Kinematics". Select as target the cube at the tip of that bone. (In the blend file it's wristIK). Change "Chain Lenght" to 2.
armature_wristIK_chain_lenght_2.JPG

Go into object mode. Select the IK for the middle bone. Move it around and see how the last bone stays where it is. It doesn't follow the armature. This will cause models being deformed.

armature_detached.JPG

armature_detached_IK_2_79b.blend

Notice in the blend file how all bones are connected, except the first being created which doesn't have a parent.
armature_connected_bones.JPG
Notice "Automatic IK" is not being selected.
armature_NO_auto_IK.JPG

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 25.20.100.6472 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: `26bd5ebd42` Worked: 2.79 **Short description of error** When a IK constraint passes another IK the armature get detached bones. **Exact steps for others to reproduce the error** Open blender with the default scene and remove everything. Add armature. Tab into edit mode. Extrude a new bone. Extrude one more bone. They will all be connected to their parent. Add a cube at the tip of the last bone and another one at the tip of the middle bone. Tab into pose mode. Select the last bone (Bone.002). Select "Bone Constraint Properties" -> "Add Bone Constraint" -> "Inverse Kinematics". Select as target the cube at the tip of that bone. (In the blend file it's thumbIK). Change "Chain Lenght" to 2. ![armature_thumbIK_chain_lenght_2.JPG](https://archive.blender.org/developer/F8289567/armature_thumbIK_chain_lenght_2.JPG) Still in pose mode select the middle bone, (Bone.001). Select "Bone Constraint Properties" -> "Add Bone Constraint" -> "Inverse Kinematics". Select as target the cube at the tip of that bone. (In the blend file it's wristIK). Change "Chain Lenght" to 2. ![armature_wristIK_chain_lenght_2.JPG](https://archive.blender.org/developer/F8289571/armature_wristIK_chain_lenght_2.JPG) Go into object mode. Select the IK for the middle bone. Move it around and see how the last bone stays where it is. It doesn't follow the armature. This will cause models being deformed. ![armature_detached.JPG](https://archive.blender.org/developer/F8289561/armature_detached.JPG) [armature_detached_IK_2_79b.blend](https://archive.blender.org/developer/F8299176/armature_detached_IK_2_79b.blend) Notice in the blend file how all bones are connected, except the first being created which doesn't have a parent. ![armature_connected_bones.JPG](https://archive.blender.org/developer/F8289556/armature_connected_bones.JPG) Notice "Automatic IK" is not being selected. ![armature_NO_auto_IK.JPG](https://archive.blender.org/developer/F8289558/armature_NO_auto_IK.JPG)
Author

Added subscriber: @BlenderAmateur

Added subscriber: @BlenderAmateur

Added subscribers: @dr.sybren, @mano-wii

Added subscribers: @dr.sybren, @mano-wii

I believe it is the same problem described in #73051
It worked on blender 2.79, but it doesn't work on 2.80.

@dr.sybren, can you confirm if it is the same problem?
To reproduce it, just open the attached file, move one target cube and then the other.

I believe it is the same problem described in #73051 It worked on blender 2.79, but it doesn't work on 2.80. @dr.sybren, can you confirm if it is the same problem? To reproduce it, just open the attached file, move one target cube and then the other.
Author

It's a duplicate, I just attached a simpler blend file and showed the problem is still there with connected bones.

When I didn't see anything in the other report for a week after it was closed as invalid, but it was shown the problem was still there even with connected bones, I thought comments written after it was closed was not read. So I wrote a new bug report.

It's a duplicate, I just attached a simpler blend file and showed the problem is still there with connected bones. When I didn't see anything in the other report for a week after it was closed as invalid, but it was shown the problem was still there even with connected bones, I thought comments written after it was closed was not read. So I wrote a new bug report.

Closed as duplicate of #73051

Closed as duplicate of #73051

@BlenderAmateur Can you make the example file with Blender 2.79? As it was made with 2.80, I cannot open it in 2.79 to confirm that it's working there.

@BlenderAmateur Can you make the example file with Blender 2.79? As it was made with 2.80, I cannot open it in 2.79 to confirm that it's working there.

I updated the description with a file that opens in blender 2.79b

I updated the description with a file that opens in blender 2.79b

In #73262#857452, @mano-wii wrote:
I updated the description with a file that opens in blender 2.79b

> In #73262#857452, @mano-wii wrote: > I updated the description with a file that opens in blender 2.79b ♥
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#73262
No description provided.