Armature: Bone dependency tree does not highlight selected bone deep enough #88413

New Issue

tt · 2021-05-19T22:47:10+02:00

tt commented

2021-05-19 22:47:10 +02:00

System Information
Operating system: Linux-5.4.0-73-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.119.03

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-05-19 10:17, hash: 81e3d904db
Worked: (newest version of Blender that worked as expected)

Short description of error
In the outliner parented meshes and curves and empties show behind the parent object and can even be selected from there and if of object down the parent relationship tree is selected this is hightlighed in the icons behind the parent object. This is not happening for bones in an armature and their relations the way it should be.

Exact steps for others to reproduce the error
I added a MB Lab Character and selected one of the armbones, these are deep enough down the bone relations tree, then try to navigate down the bone tree in the outliner to see where this bone is...

(1) there is no indication a lot of layers deep

(2) only when you are one layer above the selected bone the relation is highlighted

(3) There we go, that was harder to find than neccessary.

Also the small number next to the one bone symbol shows the number of children bones to that bone but not the children of the children, while for meshes even these relations are added up and shown. Maybe have 2 numbers there, one for overall children and one for the first grade children as bones can only parent bones and more bone icons are redundant.

Also while working with bones and armatures I found using object constraints like the "child of" constraint really useful, when an object like an empty is related to a bone with that constraint that could also show in the outliner with a quick selection of that object, but that is probably more of a feature request but I thought I just mention the idea here as it is very related (another child process lol)

**System Information** Operating system: Linux-5.4.0-73-generic-x86_64-with-glibc2.31 64 Bits Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.119.03 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-05-19 10:17, hash: `81e3d904db` Worked: (newest version of Blender that worked as expected) **Short description of error** In the outliner parented meshes and curves and empties show behind the parent object and can even be selected from there and if of object down the parent relationship tree is selected this is hightlighed in the icons behind the parent object. This is not happening for bones in an armature and their relations the way it should be. **Exact steps for others to reproduce the error** I added a MB Lab Character and selected one of the armbones, these are deep enough down the bone relations tree, then try to navigate down the bone tree in the outliner to see where this bone is... (1) there is no indication a lot of layers deep ![bug01.jpg](https://archive.blender.org/developer/F10127943/bug01.jpg) (2) only when you are one layer above the selected bone the relation is highlighted ![bug02.jpg](https://archive.blender.org/developer/F10127949/bug02.jpg) (3) There we go, that was harder to find than neccessary. ![bug03.jpg](https://archive.blender.org/developer/F10127951/bug03.jpg) Also the small number next to the one bone symbol shows the number of children bones to that bone but not the children of the children, while for meshes even these relations are added up and shown. Maybe have 2 numbers there, one for overall children and one for the first grade children as bones can only parent bones and more bone icons are redundant. Also while working with bones and armatures I found using object constraints like the "child of" constraint really useful, when an object like an empty is related to a bone with that constraint that could also show in the outliner with a quick selection of that object, but that is probably more of a feature request but I thought I just mention the idea here as it is very related (another child process lol)

tt commented

2021-05-19 22:47:10 +02:00

Added subscriber: @ToxicTuba

Philipp Oeser commented

2021-05-26 15:50:58 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-05-26 15:50:58 +02:00

I can confirm the difference in behavior of armature/bone hierarchies vs. object hierarchies (and without digging deeper I would not see a reason to not use the object behavior here, but will check code).

Tip: to quickly navigate to the selected bone, use {key .}

I can confirm the difference in behavior of armature/bone hierarchies vs. object hierarchies (and without digging deeper I would not see a reason to not use the object behavior here, but will check code). Tip: to quickly navigate to the selected bone, use {key .} ![image.png](https://archive.blender.org/developer/F10143167/image.png)

blender-admin commented

2021-05-26 17:01:58 +02:00

This issue was referenced by b6a35a8153

This issue was referenced by b6a35a8153c30f5c1516fef6fb5c16482248cdf0

Philipp Oeser commented

2021-05-26 17:08:52 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'