Page MenuHome

Collections Duplication Issue
Closed, ArchivedPublic


System Information
Operating system: MacOS + Windows 10 both tested
Graphics card: Gtx 1070

Blender Version
Broken: 2.8 Beta
Collections duplication is binding them together and not allowing for individual selection of the new collection

Short description of error
If you duplicate a collection you cannot individually modify the new collection as it's tied (mirrored?) to the previous one.

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
Create a set of objects, in the collections tab select a collection and duplicate it. If you toggle the visibility of the first collection off the newly duplicated collection will also be toggled on/off. Each object is mirrored to the original and cannot be modified individually. Even if this behavior is intentional it's extremely bizarre.

-Also small note: The Z key in edit mode on Mac is opening a shading pie menu by default instead of giving the option to enter wireframe. On the windows version I am not having this issue. Both copies of Blender 2.8 are fresh installations with no preference modifications yet the keybinds are acting differently.



Event Timeline

Brecht Van Lommel (brecht) claimed this task.

The hiding is actually per object, the hide icon for collections only toggles the visible of all the objects within it. So if it contains the same objects this happens.

This may change still (though it also useful to be able to hide objects regardless if they are in multiple collections), but for now it's not considered a bug.

Regarding Z key, it is quite like the preferences are different. If you had installed blender 2.8 at any point in the past it might still be using preferences from that.

I understand, what I'm saying is that the new collection of totally separate objects is not separated. You cannot individually modify them. Anything you do to the first object will also be applied to the duplicated collection.

Create a new project, duplicate the cube. Then right click in the collections window and click duplicate. Now take your newly duplicated collection and do anything to it. The new collection will modify the original despite being a duplicated group and collection. You cannot toggle anything even visibility without affecting the original collection.

I cannot imagine why this would be the default behavior and why duplicate wouldn't create a copy of the object that can be modified. In the 2d layering workflow duplicating your layer/group for example makes a new layer you can now work on independently. It doesn't just create another reference to the first layer.

I believe this is unintended?

We will likely add a "Duplicate Hierarchy" for this in the future, for now all this does is duplicate the collection, not its contents.

Hi, when you refer to "its contents" it also includes the objects themselves or only the collection hierarchy?

Just to add to this - you can't even select the original collection without also selecting the duplicate. You can't deselect one without also deselecting the other. Your duplicate can't even be moved to a different location so it can only occupy the exact same space as the original. If you unlink the duplicate collection it disappears, and if you unlink the individual items in the collection they disappear. The only way I can find to have two identical collections is to duplicate the contents of a collection and move the duplicates to a new collection.