Duplication of IDs and linked data-blocks #77959

New Issue

Until now (including 2.83), deep copy of object datablocks was very confusing and partially broken code (mostly missing some remapping to duplicated IDs).

Recent refactor made internal code much more maintainable and consistent, but it did add some user-side changes in behaviors (documented in the release notes).

One of them is that linked Objects are no longer kept unchanged when fully copying a scene.

I can see three possibilities here:

Keep new behavior, which matches all other deep-copying (of collections in particular).
Always consider that we do not want to copy sub-data that is linked during a duplicate. That would also involve all other ID types, not only objects.
Restore previous behavior (i.e. have an exception corner case handling reserved to only scene duplication).

Until now (including 2.83), deep copy of object datablocks was very confusing and partially broken code (mostly missing some remapping to duplicated IDs). Recent refactor made internal code much more maintainable and consistent, but it did add some user-side changes in behaviors (documented in [ the release notes](https://wiki.blender.org/w/index.php?title=Reference/Release_Notes/2.90/More_Features#Data_Duplication)). One of them is that linked Objects are no longer kept unchanged when fully copying a scene. I can see three possibilities here: - Keep new behavior, which matches all other deep-copying (of collections in particular). - Always consider that we do not want to copy sub-data that is linked during a duplicate. That would also involve all other ID types, not only objects. - Restore previous behavior (i.e. have an exception corner case handling reserved to only scene duplication).

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

Added subscribers: @mont29, @brecht, @dfelinto, @JulianEisel, @ideasman42

I would personally go for solution #2, imho it makes sense to never copy linked sub-data in that scenario. Alternatively, we could make it an option?

Added subscribers: @Hjalti, @eyecandy

@eyecandy @Hjalti you should also be involved in that discussion I think. ;)

AFAIK this task it done?

@JulianEisel afaik this task is not done at all? I posted the issue with some possible solutions, and got no comment about it at all…

Ah, pardon me. The task just caught my eye when updating the workboard, read the first two sentences and assumed this was about Lib Override duplication... Nevermind, sorry about the noise :)

Added subscriber: @RedMser

If I do not get any feedback here I will just go on and implement #2...

Added subscriber: @Imaginer

My two cents:
I think that when a user does a full copy of a scene (or a full copy of anything) they would expect it be an exact copy/duplicate, i.e. all relationships/links maintained. It sounds like option #2 allows for this, so I agree, go with that one.

My two cents: I think that when a user does a full copy of a scene (or a full copy of anything) they would expect it be an exact copy/duplicate, i.e. all relationships/links maintained. It sounds like option #2 allows for this, so I agree, go with that one.

Changed status from 'Confirmed' to: 'Resolved'

Implemented in 7b1c406b54:

Never duplicate linked IDs as part of deep copy, except when the root duplicated data-block itself is linked (in which case we consider user wants to make some locale deep copy of it).

Implemented in 7b1c406b54: Never duplicate linked IDs as part of deep copy, except when the root duplicated data-block itself is linked (in which case we consider user wants to make some locale deep copy of it).

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Duplication of IDs and linked data-blocks #77959