diff options
| author | Bastien Montagne <bastien@blender.org> | 2021-05-06 18:45:40 +0300 |
|---|---|---|
| committer | Bastien Montagne <bastien@blender.org> | 2021-05-06 19:21:20 +0300 |
| commit | 7cade013c1943d0412b3629e86626100a6f683dc (patch) | |
| tree | c701b027d9ee5347d08a826913451b47f3987bfc /source/blender/blenkernel/intern/armature_update.c | |
| parent | 98a1540627f3c36f17c0064babe605faa2152246 (diff) | |
LibOverride: Better handling of 'orphaned' Objects in override creation.
One of current annoying limitations of Blender re Collections/Objects is
that objects are forbidden to not be instantiated in at least one
collection.
Code ensuring that as a pst-processing step of override creation/resync
operations would be a bit too eager to add those objects to an external
'ad-hoc' collection, which poses several issues (both in term of keeping
the scene well organized, and related to override hierarchy handling).
So now be very conservative and only generate and use external 'storage'
collection for those objects when it is absolutely mandatory.
In pratice, it means this should never happen anymore on any decently
organized data source.
Diffstat (limited to 'source/blender/blenkernel/intern/armature_update.c')
0 files changed, 0 insertions, 0 deletions