Floaty disconnected bones appearing on complex rigs #66582

New Issue

Alex · 2019-07-08T23:04:47+02:00

Alex commented

2019-07-08 23:04:47 +02:00

System Information
Operating system: macOS Mojave & Pop!_OS
Graphics card: AMD FirePro D700 6 GB & Iris Integrated

Blender Version
Broken: 2.80 (2019007-07 23:53) Hash: bb2abacb4b
Worked: Never... but sometimes..?

Short description of error
Sometimes when building complex rigs my armature will decide it dislikes a bone or bones and the bone acts as if its disconnected from the rest of the armature but sort of jiggly (See Video Below). Its very strange. Kinda neat looking but not what I am going for. This effect seems to show up and disappear and random. It remains after export to FBX and Collada if the animation is exported when the bug is showing up.

Exact steps for others to reproduce the error
I wish I could detail how this happens. It really only happens after i have been working on a rig for a while. It does seems to happen a lot with bones connected to IK constraints but its has happened to other bones at random as well.JigglyBoneBug_Blender (19.7.7).mp4

NORA_RigLabel.blend1

NORA_RigLabel.blend

**System Information** Operating system: macOS Mojave & Pop!_OS Graphics card: AMD FirePro [D700](https://archive.blender.org/developer/D700) 6 GB & Iris Integrated **Blender Version** Broken: 2.80 (2019007-07 23:53) Hash: bb2abacb4b5c Worked: Never... but sometimes..? **Short description of error** Sometimes when building complex rigs my armature will decide it dislikes a bone or bones and the bone acts as if its disconnected from the rest of the armature but sort of jiggly (See Video Below). Its very strange. Kinda neat looking but not what I am going for. This effect seems to show up and disappear and random. It remains after export to FBX and Collada if the animation is exported when the bug is showing up. **Exact steps for others to reproduce the error** I wish I could detail how this happens. It really only happens after i have been working on a rig for a while. It does seems to happen a lot with bones connected to IK constraints but its has happened to other bones at random as well.[JigglyBoneBug_Blender (19.7.7).mp4](https://archive.blender.org/developer/F7577636/JigglyBoneBug_Blender__19.7.7_.mp4) [NORA_RigLabel.blend1](https://archive.blender.org/developer/F7577643/NORA_RigLabel.blend1) [NORA_RigLabel.blend](https://archive.blender.org/developer/F7577642/NORA_RigLabel.blend)

Alex commented

2019-07-08 23:04:47 +02:00

Added subscriber: @newyear-3

Germano Cavalcante commented

2019-07-09 15:03:40 +02:00

Added subscribers: @Sergey, @mano-wii

Germano Cavalcante commented

2019-07-09 15:03:40 +02:00

If you open the console you will see that the rig has 14 dependency cycles.
This is usually cause of delay.
But I don't have much knowledge in this area.
@Sergey, what do you think, this is a bug?
depedency_cycles_log.txt

If you open the console you will see that the rig has 14 dependency cycles. This is usually cause of delay. But I don't have much knowledge in this area. @Sergey, what do you think, this is a bug? [depedency_cycles_log.txt](https://archive.blender.org/developer/F7579090/depedency_cycles_log.txt)

Sergey Sharybin commented

2019-07-09 15:18:42 +02:00

Undefined behavior of rig when it has dependency cycle is not a bug.

There is chance it is fake/avoidable dependency cycle, but for investigation we need a simple rig, which only includes relevant parts, with as few bones as possible.

Undefined behavior of rig when it has dependency cycle is not a bug. There is chance it is fake/avoidable dependency cycle, but for investigation we need a simple rig, which only includes relevant parts, with as few bones as possible.

Alex commented

2019-07-09 16:27:45 +02:00

I have removed all unnecessary bones, mesh, and constraints. If anything is removed from this version of the model the floatybone issue stops happening. Looks like their are still 9 dependency cycles. Hope this helps and is not all just user error. ha ha. Thanks for taking a look at this.

Floatybones_Example.blend1

Floatybones_Example.blend

I have removed all unnecessary bones, mesh, and constraints. If anything is removed from this version of the model the floatybone issue stops happening. Looks like their are still 9 dependency cycles. Hope this helps and is not all just user error. ha ha. Thanks for taking a look at this. [Floatybones_Example.blend1](https://archive.blender.org/developer/F7579268/Floatybones_Example.blend1) [Floatybones_Example.blend](https://archive.blender.org/developer/F7579267/Floatybones_Example.blend)

Germano Cavalcante commented

2019-07-09 16:45:59 +02:00

@Sergey, in the new attached file, when you move the bone near the origin and press ESC the problem is more noticeable.
But I still can't confirm if it has any fake/avoidable dependency cycle.

@Sergey, in the new attached file, when you move the bone near the origin and press `ESC` the problem is more noticeable. But I still can't confirm if it has any fake/avoidable dependency cycle.

Alex commented

2019-07-09 16:59:50 +02:00

I have played with it a little more and gotten it down to 1 dependency cycle. This is a different area of the rig but when you move the bone (LargeLegAnchor.R) you will see that bone (LargeLegTrack.R) has the floaty bone issue. In this version file if you delete the copy rotation constraint the issue goes away but not if you just turn it off. This seems to be the same issue but is being caused by something different? Not sure. Floatybones_Example2.blend1

Floatybones_Example2.blend.

I have played with it a little more and gotten it down to 1 dependency cycle. This is a different area of the rig but when you move the bone (LargeLegAnchor.R) you will see that bone (LargeLegTrack.R) has the floaty bone issue. In this version file if you delete the copy rotation constraint the issue goes away but not if you just turn it off. This seems to be the same issue but is being caused by something different? Not sure. [Floatybones_Example2.blend1](https://archive.blender.org/developer/F7579329/Floatybones_Example2.blend1) [Floatybones_Example2.blend](https://archive.blender.org/developer/F7579328/Floatybones_Example2.blend).

Sergey Sharybin commented

2019-07-09 17:13:38 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2019-07-09 17:13:38 +02:00

Sergey Sharybin self-assigned this 2019-07-09 17:13:38 +02:00

Sergey Sharybin commented

2019-07-09 17:13:38 +02:00

In the original file from Floatybones_Example.blend bone Thigh2.L copies rotation from Thigh2Pivot.L, but at the same time Thigh2.L is parent of Thigh2Pivot.L. Rest of the cycles seems to have similar nature.

Floatybones_Example2.blend has similar situation.

This is real dependency cycle and we can not do anything about it. You'd need to find a way to rig your model without introducing such cycles.

In the original file from `Floatybones_Example.blend` bone `Thigh2.L` copies rotation from `Thigh2Pivot.L`, but at the same time `Thigh2.L` is parent of `Thigh2Pivot.L`. Rest of the cycles seems to have similar nature. `Floatybones_Example2.blend` has similar situation. This is real dependency cycle and we can not do anything about it. You'd need to find a way to rig your model without introducing such cycles.

Alex commented

2019-07-09 17:16:49 +02:00

Thanks again for looking at this. Glad it's just me and not a bug. ha ha. Cheers!

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Floaty disconnected bones appearing on complex rigs #66582