Errors encountered when re-opening a .blend file with multiple library overrides with local parents #109993

New Issue

Erik Scott · 2023-07-12T06:19:22+02:00

Erik Scott commented

2023-07-12 06:19:22 +02:00

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

Blender Version
Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: c7fc78b81ecb
Worked: never to my knowledge (also broken in 3.5.1)

Short description of error
Project saved with two library overrides of the same linked asset. The parent object of both overrides was made local so it could be renamed and drivers added to custom properties. Upon re-opening the .blend file, some (all but one?) of the parent objects was no longer local, stuck at the origin, and the parent-child relationship as no longer properly reflected in the outliner.

Exact steps for others to reproduce the error
Please see the attached LibraryOverrideError.zip file. It contains an example of a messed-up file (CombinedFile.blend) and a file for reproducing the error (CombinedFileStarter.blend). There is also an assets folder which contains various assets to be linked in and made into library overrides.

Detailed Steps:

Open default scene
Go to File > Link. Navigate to assets > GenericComponents.blend > Collection > VECTOR_INDICATOR and click "Link"
In the 3d viewport, click Object > Library Override > Make.
Select the FORCE_INDICATOR_PARENT empty.
Localize the empty so that it can be renamed: in the properties panel in the object tab, click the chain-arrow icon next to the object name to create a local version and rename it to "left" (exact name is not necessary to re-produce the error).
Make sure the "left" empty is selected and Ctrl-click the cube
Press Ctrl-P and select "Object (Without Inverse)". (make cube object parent)
Move the "left" empty to another position (X = -5)
Repeat steps 2 through 8 with another VECTOR_INDICATOR. When re-naming the parent empty, name it "right", and the intended position（X = 5）
Save the file and close Blender.
Re-open the file and observe the outliner. Notice that one of the parent empties (either wing_rt or wing lt) has been renamed back to FORCE_INDICATOR_PARENT.001. It is no longer local, and the child objects are no longer appear as childern under it in the outliner (despite still being children). The parent has been re-positioned back to the global origin, and is no-longer parented to the airframe_axes object. It cannot be moved, rotated, or scaled.

Some of these steps probably aren't strictly necessary. However, this is a simplified version of the situation in which I encountered this issue and I felt it was important to retain the context for the purposes of reproducibility and to demonstrate the error within a specific workflow.

Workarounds
Appending the asset works fine, as it keeps everything local to the file. Unfortunately, this defeats the pointed of having a remote asset that can be re-used and updated across multiple places.

I have attempted a workaround in which I don't make the parent object local. Instead, I would create a super-parent (named "wing_lt", for instance) and give it custom properties. The custom properties of the original linked parent would then be driven by the super parent's properties using drives. Unfortunately, the custom properties of a library override cannot use drivers (even ones marked "library overridable").

Other thoughts
Simply allowing drivers in the custom properties of a library override would go a long way towards making linked rigs work well. Alternatively, a way to add an "interface" of custom properties to linked assets without having to create overrides would be huge benefit to my intended use case and workflow.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40 **Blender Version** Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: `c7fc78b81ecb` Worked: never to my knowledge (also broken in 3.5.1) **Short description of error** Project saved with two library overrides of the same linked asset. The parent object of both overrides was made local so it could be renamed and drivers added to custom properties. Upon re-opening the .blend file, some (all but one?) of the parent objects was no longer local, stuck at the origin, and the parent-child relationship as no longer properly reflected in the outliner. **Exact steps for others to reproduce the error** Please see the attached LibraryOverrideError.zip file. It contains an example of a messed-up file (CombinedFile.blend) and a file for reproducing the error (CombinedFileStarter.blend). There is also an assets folder which contains various assets to be linked in and made into library overrides. Detailed Steps: 1. Open default scene 2. Go to File > Link. Navigate to assets > GenericComponents.blend > Collection > VECTOR_INDICATOR and click "Link" 3. In the 3d viewport, click Object > Library Override > Make. 4. Select the FORCE_INDICATOR_PARENT empty. 5. Localize the empty so that it can be renamed: in the properties panel in the object tab, click the chain-arrow icon next to the object name to create a local version and rename it to "left" (exact name is not necessary to re-produce the error). 6. Make sure the "left" empty is selected and Ctrl-click the cube 7. Press Ctrl-P and select "Object (Without Inverse)". (make cube object parent) 8. Move the "left" empty to another position (X = -5) 9. Repeat steps 2 through 8 with another VECTOR_INDICATOR. When re-naming the parent empty, name it "right", and the intended position（X = 5） 10. Save the file and close Blender. 11. Re-open the file and observe the outliner. Notice that one of the parent empties (either wing_rt or wing lt) has been renamed back to FORCE_INDICATOR_PARENT.001. It is no longer local, and the child objects are no longer appear as childern under it in the outliner (despite still being children). The parent has been re-positioned back to the global origin, and is no-longer parented to the airframe_axes object. It cannot be moved, rotated, or scaled. Some of these steps probably aren't strictly necessary. However, this is a simplified version of the situation in which I encountered this issue and I felt it was important to retain the context for the purposes of reproducibility and to demonstrate the error within a specific workflow. **Workarounds** Appending the asset works fine, as it keeps everything local to the file. Unfortunately, this defeats the pointed of having a remote asset that can be re-used and updated across multiple places. I have attempted a workaround in which I don't make the parent object local. Instead, I would create a super-parent (named "wing_lt", for instance) and give it custom properties. The custom properties of the original linked parent would then be driven by the super parent's properties using drives. Unfortunately, the custom properties of a library override cannot use drivers (even ones marked "library overridable"). **Other thoughts** Simply allowing drivers in the custom properties of a library override would go a long way towards making linked rigs work well. Alternatively, a way to add an "interface" of custom properties to linked assets without having to create overrides would be huge benefit to my intended use case and workflow.

LibraryOverrideError.zip

693 KiB

Erik Scott added the

labels 2023-07-12 06:19:23 +02:00

Pratik Borhade commented

2023-07-12 08:29:10 +02:00

Thanks for the report. Can confirm even when I link the object data in default scene. (updated the report accordingly)

It is no longer local, and the child objects are no longer appear as childern under it in the outliner (despite still being children)

After reopening the file, no user has detected for some overridden objects.
I'm not sure about the cause. Maybe @mont29 have an idea? (want me to simplify this issue further?)

Thanks for the report. Can confirm even when I link the object data in default scene. (updated the report accordingly) > It is no longer local, and the child objects are no longer appear as childern under it in the outliner (despite still being children) After reopening the file, no user has detected for some overridden objects. I'm not sure about the cause. Maybe @mont29 have an idea? (want me to simplify this issue further?)

Pratik Borhade added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Errors encountered when re-opening a .blend file with multiple library overrides with local parents #109993