Bone group does not hide bone if it was moved using assign #114281

New Issue

Antonio Vazquez · 2023-10-30T17:39:05+01:00

Antonio Vazquez commented

2023-10-30 17:39:05 +01:00

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 545.92

Blender Version
Broken: version: 4.0.0 Beta, branch: blender-v4.0-release, commit date: 2023-10-29 13:19, hash: e9ad267151c9

Open default scene.
Create an armature in the default bone group.
Create bone_1 and bone_2.
Create a new bone group.
Create a bone_3.
Select bone_2, the new bone group and press assign.
Unselect all, and pressing the select button of the group bone_2 and bone_3 are selected.
Hide the group, only bone_3 is hidden.

Example contains two bones in the last group. Hide group and only one bone is hidden.

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 545.92 **Blender Version** Broken: version: 4.0.0 Beta, branch: blender-v4.0-release, commit date: 2023-10-29 13:19, hash: `e9ad267151c9` 1) Open default scene. 2) Create an armature in the default bone group. 3) Create `bone_1` and `bone_2`. 4) Create a new bone group. 5) Create a `bone_3`. 6) Select `bone_2`, the new bone group and press assign. 7) Unselect all, and pressing the select button of the group `bone_2` and `bone_3` are selected. 8) Hide the group, only `bone_3` is hidden. Example contains two bones in the last group. Hide group and only one bone is hidden.

Bone Group.blend

821 KiB

Antonio Vazquez added the

labels 2023-10-30 17:39:06 +01:00

Philipp Oeser commented

2023-11-01 16:04:03 +01:00

Bone.002 is a member of both Group B and Group C.
If it was a member of Group C only, then hiding Group C works properly.
(alternatively, you would have to hide both Group B and Group C to fully hide Bone.002)

Em, yes, this is different to 3.6 bone layers [where we could only be part of one layer].
So this seems burried in the design, not sure if @dr.sybren wants to comment?

Personally, I dont think it is a bug.

`Bone.002` is a member of both `Group B` and `Group C`. If it was a member of `Group C` **only**, then hiding `Group C` works properly. (alternatively, you would have to hide both `Group B` and `Group C` to fully hide `Bone.002`) Em, yes, this is different to 3.6 bone layers [where we could only be part of one layer]. So this seems burried in the design, not sure if @dr.sybren wants to comment? Personally, I dont think it is a bug.

Philipp Oeser added

Module

Animation & Rigging

Status

Needs Info from Developers

and removed

Status

Needs Triage

labels 2023-11-01 16:04:22 +01:00

Philipp Oeser commented

2023-11-01 16:09:27 +01:00

Clarified in chat with @antoniov , will close then

Philipp Oeser closed this issue

2023-11-01 16:09:30 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Info from Developers

labels 2023-11-01 16:09:32 +01:00

Sybren A. Stüvel commented

2023-11-02 10:06:03 +01:00

Bone.002 is a member of both Group B and Group C.
If it was a member of Group C only, then hiding Group C works properly.
(alternatively, you would have to hide both Group B and Group C to fully hide Bone.002)

Em, yes, this is different to 3.6 bone layers [where we could only be part of one layer].
So this seems burried in the design, not sure if @dr.sybren wants to comment?

For the record: Bones could be part of multiple armature layers, and would be shown if any of these layers were visible. 4.0 bone collections & 3.6 armature layers behave in exactly the same way (or at least, they should, if not it's a bug).

I think you're confusing armature layers with bone groups. A bone could only be part of one bone group. These determined bone color, though, and not visibility.

> `Bone.002` is a member of both `Group B` and `Group C`. > If it was a member of `Group C` **only**, then hiding `Group C` works properly. > (alternatively, you would have to hide both `Group B` and `Group C` to fully hide `Bone.002`) > > Em, yes, this is different to 3.6 bone layers [where we could only be part of one layer]. > So this seems burried in the design, not sure if @dr.sybren wants to comment? For the record: Bones could be part of multiple armature layers, and would be shown if any of these layers were visible. 4.0 bone collections & 3.6 armature layers behave in exactly the same way (or at least, they should, if not it's a bug). I think you're confusing armature layers with bone groups. A bone could only be part of one bone group. These determined bone color, though, and not visibility.

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

Bone group does not hide bone if it was moved using assign #114281