Driver relationship is broken in linked scenes, when override is done in wrong order #99261

New Issue

Matthias · 2022-06-29T10:02:37+02:00

Matthias commented

2022-06-29 10:02:37 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59

Blender Version
Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: cc66d1020c
Worked: ?

Short description of error
Shape key driving another shape key gets broken in linked scenes when making library override in the wrong order.

Exact steps for others to reproduce the error
2.blend
1.blend
Open file 2.blend and tweak shape key value

Or from scratch:

Create Cube (cube01) with shape key.
Duplicate Cube (cube02)
Set shape key of first cube to be the driver of shape key of second cube.
Pack into new collection.
Save scene.
Create new file and scene.
Link collection with cubes to new scene.
Override Collection.
Override object data of cube01.
Override object data of cube02.
Driver relationship is broken. Works if override is done in opposite order.

Maybe this happens for other Driver relationships also. Just tested it with shape keys.

My problem is, that I already did a bunch of editing in my scene with a linked character and just now found out about this, so it's not possible for me to reset the overrides and redo them in the order that works.
There should be a way to fix this, other than having to reset the overrides.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59 **Blender Version** Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: `cc66d1020c` Worked: ? **Short description of error** Shape key driving another shape key gets broken in linked scenes when making library override in the wrong order. **Exact steps for others to reproduce the error** [2.blend](https://archive.blender.org/developer/F13258709/2.blend) [1.blend](https://archive.blender.org/developer/F13258710/1.blend) Open file 2.blend and tweak shape key value Or from scratch: - Create Cube (cube01) with shape key. - Duplicate Cube (cube02) - Set shape key of first cube to be the driver of shape key of second cube. - Pack into new collection. - Save scene. - Create new file and scene. - Link collection with cubes to new scene. - Override Collection. - Override object data of cube01. - Override object data of cube02. - > Driver relationship is broken. Works if override is done in opposite order. Maybe this happens for other Driver relationships also. Just tested it with shape keys. My problem is, that I already did a bunch of editing in my scene with a linked character and just now found out about this, so it's not possible for me to reset the overrides and redo them in the order that works. There should be a way to fix this, other than having to reset the overrides.

Matthias commented

2022-06-29 10:02:37 +02:00

Added subscriber: @Mots

Matthias commented

2022-06-29 10:38:00 +02:00

Also, the same thing happens when trying to do the driver relationship inside the scene that contains the linked cubes, except then the override order doesn't matter.
This works as long as working with the scene, but upon reopening/reverting, the relationship doesn't work anymore.

Also, the same thing happens when trying to do the driver relationship inside the scene that contains the linked cubes, except then the override order doesn't matter. This works as long as working with the scene, but upon reopening/reverting, the relationship doesn't work anymore.

Richard Antalik commented

2022-07-04 21:05:23 +02:00

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

Bastien Montagne commented

2022-07-11 11:12:36 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2022-07-11 11:12:36 +02:00

Changed status from 'Confirmed' to: 'Archived'

Bastien Montagne closed this issue

2022-07-11 11:12:36 +02:00

Bastien Montagne commented

2022-07-11 11:12:36 +02:00

As explained in the documentation, when doing single overrides that way, you indeed need to manually fix relationships between data-blocks, there is no way for Blender to know/guess which ID pointer should be remapped where, etc.

This why the 'override hierarchy' should be the preferred way to use to create overrides.

Note that the 'create single override' option is likely to disappear entirely from the UI in Blender 3.3, since it's a fairly advanced option requiring a lot of manual work, and its practical usage is close to null.

As explained in [the documentation](https://docs.blender.org/manual/en/3.2/files/linked_libraries/library_overrides.html), when doing single overrides that way, you indeed need to manually fix relationships between data-blocks, there is no way for Blender to know/guess which ID pointer should be remapped where, etc. This why the 'override hierarchy' should be the preferred way to use to create overrides. Note that the 'create single override' option is likely to disappear entirely from the UI in Blender 3.3, since it's a fairly advanced option requiring a lot of manual work, and its practical usage is close to null.

Matthias commented

2022-07-11 12:18:32 +02:00

Well, there's just a little problem.
I'm talking about Object Data Overrrides, which aren't automatically overridden, when making the initial override.
I have to override the object data of each object one after the other, doesn't matter if I use the override single or hierarchy.

Well, there's just a little problem. I'm talking about Object Data Overrrides, which aren't automatically overridden, when making the initial override. I have to override the object data of each object one after the other, doesn't matter if I use the override single or hierarchy. ![blender_ObjectDataOverride_01.PNG](https://archive.blender.org/developer/F13285378/blender_ObjectDataOverride_01.PNG)

Bastien Montagne commented

2022-07-11 15:26:42 +02:00

I believe that kind of issue is not showing anymore in more recent versions of Blender (3.2/future 3.3)? as long as you always use the 'hierarchy' version of the override operation of course.

Matthias commented

2022-07-11 16:53:28 +02:00

Just tried the latest alpha, same behavior.

So let me explain my exact steps:

I import my collection
Select Collection
Object>Relations>Make Library Override

every OBJECT (container) gets a library override (link symbol with arrow)

to override OBJECT DATA, I have to expand every OBJECT (container), select the OBJECT DATA, and override it.

There is no option to override the hierarchy above my meshes (container objects), because they already have the override status (link symbol with arrow). Not in the right click menu, nor in the Object>Relations Menu (there it's greyed out).

Just tried the latest alpha, same behavior. So let me explain my exact steps: I import my collection Select Collection Object>Relations>Make Library Override - > every OBJECT (container) gets a library override (link symbol with arrow) to override OBJECT DATA, I have to expand every OBJECT (container), select the OBJECT DATA, and override it. There is no option to override the hierarchy above my meshes (container objects), because they already have the override status (link symbol with arrow). Not in the right click menu, nor in the Object>Relations Menu (there it's greyed out).

Matthias commented

2022-07-11 17:02:21 +02:00

Here are some screenshots to better explain:

Here are some screenshots to better explain: ![blender_ObjectDataOverride_03.PNG](https://archive.blender.org/developer/F13286077/blender_ObjectDataOverride_03.PNG) ![blender_ObjectDataOverride_04.PNG](https://archive.blender.org/developer/F13286076/blender_ObjectDataOverride_04.PNG) ![blender_ObjectDataOverride_02.PNG](https://archive.blender.org/developer/F13286075/blender_ObjectDataOverride_02.PNG)

Bastien Montagne commented

2022-07-12 09:43:56 +02:00

Changed status from 'Archived' to: 'Confirmed'

Bastien Montagne reopened this issue

2022-07-12 09:43:56 +02:00

Bastien Montagne commented

2022-07-12 09:43:57 +02:00

Aaaaah OK now I see what you mean, thanks! Yes this is a fairly intricate issue, will see how to fix it.