Moving a parent object with its children to another collection does not move the entire hierarchy #85525

New Issue

Sebastien Larocque · 2021-02-10T18:06:42+01:00

2021-02-10 18:06:42 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30

Blender Version
Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-02-08 14:44, hash: df0bce3f7d
Worked: Never

Short description of error
Moving a parent object with its children to another collection does not move the entire hierarchy

Exact steps for others to reproduce the error
*Open the attached blend file.
*In the Outliner, select and drag either “Empty_Parent” or “Cube_Parent” to another collection.
*After that, you’ll see that the children are not moved to the other collection.

The children are still accessible through the parent, but in gray.

I don’t know if this is a design decision that’s voluntary. However, like moving a folder in a file manager program, we expect the folders and files inside to follow when being dragged to another folder.

How it impacts productivity
*Moving a parent object alone to another collection is impossible. The user needs to develop the hierarchy and also to select the children. Slower process and more complicated.
*If you forgot that the object had children, your hierarchy is kind of split up between two collections.
*If you move the parent from collection A to collection B for example and delete the collection A, the child objects are moved to the top scene collection. That makes managing child objects even harder.
*If you have a long list of parent objects (for example 20) and you want to move these parent objects to another collection with their children, you will need to develop the hierarchy of all the parent objects, select the children and then move the entire selected objects.
*If you have more complex parent objects, it becomes a nightmare. For example, imagine a solar system with the sun, planets and their moons.
*You can still do “Select Hierarchy” from the contextual menu, but that works only for one object at a time.

Note on parent object
For years, I’ve always seen Blender not being able to handle properly parent objects with their children. Other examples related to this kind of things are: duplicating a parent does not consider the children, importing (Append menu) parent object does not consider the children, etc. That bug report here has tentacles in other aspects or behavior related to parent objects.

The parent objects don’t behave like real parents. If there is a concept of parent, I expect a parent to behave like a real parent object would do. A part of it still works by moving and rotating the parent for example, but the rest is really broken.

Overall, whether it's for the collection or the other parenting stuff, that behavior seems buggy to me.

MovingParentObjectToAnotherCollection.blend

Before moving
{F9771347 size=full}

After moving
{F9771354 size=full}

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30 **Blender Version** Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-02-08 14:44, hash: `df0bce3f7d` Worked: Never **Short description of error** Moving a parent object with its children to another collection does not move the entire hierarchy **Exact steps for others to reproduce the error** *Open the attached blend file. *In the Outliner, select and drag either “Empty_Parent” or “Cube_Parent” to another collection. *After that, you’ll see that the children are not moved to the other collection. The children are still accessible through the parent, but in gray. I don’t know if this is a design decision that’s voluntary. However, like moving a folder in a file manager program, we expect the folders and files inside to follow when being dragged to another folder. **How it impacts productivity** *Moving a parent object alone to another collection is impossible. The user needs to develop the hierarchy and also to select the children. Slower process and more complicated. *If you forgot that the object had children, your hierarchy is kind of split up between two collections. *If you move the parent from collection A to collection B for example and delete the collection A, the child objects are moved to the top scene collection. That makes managing child objects even harder. *If you have a long list of parent objects (for example 20) and you want to move these parent objects to another collection with their children, you will need to develop the hierarchy of all the parent objects, select the children and then move the entire selected objects. *If you have more complex parent objects, it becomes a nightmare. For example, imagine a solar system with the sun, planets and their moons. *You can still do “Select Hierarchy” from the contextual menu, but that works only for one object at a time. **Note on parent object** For years, I’ve always seen Blender not being able to handle properly parent objects with their children. Other examples related to this kind of things are: duplicating a parent does not consider the children, importing (Append menu) parent object does not consider the children, etc. That bug report here has tentacles in other aspects or behavior related to parent objects. The parent objects don’t behave like real parents. If there is a concept of parent, I expect a parent to behave like a real parent object would do. A part of it still works by moving and rotating the parent for example, but the rest is really broken. Overall, whether it's for the collection or the other parenting stuff, that behavior seems buggy to me. [MovingParentObjectToAnotherCollection.blend](https://archive.blender.org/developer/F9771344/MovingParentObjectToAnotherCollection.blend) Before moving {[F9771347](https://archive.blender.org/developer/F9771347/BeforeMoving.jpg) size=full} After moving {[F9771354](https://archive.blender.org/developer/F9771354/AfterMoving.jpg) size=full}

Sebastien Larocque commented

2021-02-10 18:06:42 +01:00

Added subscriber: @SebBlender

Philipp Oeser commented

2021-09-20 21:47:08 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-09-20 21:47:08 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Philipp Oeser closed this issue

2021-09-20 21:47:08 +02:00

Philipp Oeser commented

2021-09-20 21:47:08 +02:00

Hi and thx for the report! (sorry it took so long to answer).

This can be cumbersome (in the Outliner), I agree.
In the 3DView, I find myself using Select More/Less > More (this goes up and down the hierarchy) {key Ctrl +} or Select More/Less > Extend Child which I map to {key Shift +} and hammer it until the whole hierarchy is selected (this works on multiple selected items to begin with, not just the active one.

Select Hierarhy in the Outliner would be good to suppert on multiple selected items, true.

However (sorry to be strict here), the issue reported here is a request for modified/improved behavior and not a bug in current behavior.
Will have to close since this bug tracker is only for bugs and errors.
For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Hi and thx for the report! (sorry it took so long to answer). This can be cumbersome (in the Outliner), I agree. In the 3DView, I find myself using `Select More/Less` > `More` (this goes up and down the hierarchy) {key Ctrl +} or `Select More/Less` > `Extend Child` which I map to {key Shift +} and hammer it until the whole hierarchy is selected (this works on multiple selected items to begin with, not just the active one. Select Hierarhy in the Outliner would be good to suppert on multiple selected items, true. However (sorry to be strict here), the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Will have to close since this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

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

Moving a parent object with its children to another collection does not move the entire hierarchy #85525