Relocating linked armatures removes bone modifiers! #65483

New Issue

Karlo · 2019-06-04T10:38:36+02:00

Karlo commented

2019-06-04 10:38:36 +02:00

System Information
Operating system: win7
Graphics card: gtx 1080TI

Blender Version
Broken: latest, c13e10a740, 06-04-2019
Worked: (optional)

Short description of error

After an armature that was previously linked using relative path is moved and relocated all the bone constraints are removed thus breaking
the rig.

Exact steps for others to reproduce the error

linkModifierTest.blend

In this file Bone.001 has a copyTransforms constraint. Moving Bone should move Bone.001 and the cube (which is linked to Bone.001 using ctrp+p>Bone)

Place my file in some folder
Make a new blend outside in some other folder, link the collection testGroup from my file and create a proxy of the armature (everything works correctly so far)
Make the new file use relative paths and save
Move my file to a new folder location
Open the linking file you created. Outline > Blender File > RMB on broken link > Relocate
After locating the file, it is loaded in without any constraints

**System Information** Operating system: win7 Graphics card: gtx 1080TI **Blender Version** Broken: latest, c13e10a7404d, 06-04-2019 Worked: (optional) **Short description of error** After an armature that was previously linked using relative path is moved and relocated all the bone constraints are removed thus breaking the rig. **Exact steps for others to reproduce the error** [linkModifierTest.blend](https://archive.blender.org/developer/F7086221/linkModifierTest.blend) In this file Bone.001 has a copyTransforms constraint. Moving Bone should move Bone.001 and the cube (which is linked to Bone.001 using ctrp+p>Bone) - Place my file in some folder - Make a new blend outside in some other folder, link the collection testGroup from my file and create a proxy of the armature (everything works correctly so far) - Make the new file use relative paths and save - Move my file to a new folder location - Open the linking file you created. Outline > Blender File > RMB on broken link > Relocate - After locating the file, it is loaded in without any constraints

Karlo commented

2019-06-04 10:38:36 +02:00

Added subscriber: @kpavicic

Bastien Montagne commented

2019-06-04 17:15:08 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2019-06-04 17:15:08 +02:00

Think there are several missing pieces and wrong naming here… Am assuming you are talking about constraints, not modifiers, and that you create a proxy of your linked collection for the armature, between step 2. and 3.?

If that’s the case, I’ll have a closer look, but am afraid that it won’t be a high priority bug, proxies are known to be half-broken in many corner cases, and should be replaced sooner than later by library overrides anyway.

Think there are several missing pieces and wrong naming here… Am assuming you are talking about constraints, not modifiers, and that you create a proxy of your linked collection for the armature, between step 2. and 3.? If that’s the case, I’ll have a closer look, but am afraid that it won’t be a high priority bug, proxies are known to be half-broken in many corner cases, and should be replaced sooner than later by library overrides anyway.

Karlo commented

2019-06-04 17:54:32 +02:00

I am indeed talking about constraints. Apologies for the mistake. And you're right, a proxy needs to be created for the armature. I will make the edits.

If it's not a high priority how would one currently go about fixing paths after a folder with the rigs has moved? I ran into this bug and it's stopping me from restructuring.
Unfortunately I'm not familiar with library overrides. Would this make the path changes more like in maya where a user simply types in the new file location?

I am indeed talking about constraints. Apologies for the mistake. And you're right, a proxy needs to be created for the armature. I will make the edits. If it's not a high priority how would one currently go about fixing paths after a folder with the rigs has moved? I ran into this bug and it's stopping me from restructuring. Unfortunately I'm not familiar with library overrides. Would this make the path changes more like in maya where a user simply types in the new file location?

Demeter Dzadik commented

2019-07-17 21:27:17 +02:00

Added subscriber: @Mets

Demeter Dzadik commented

2019-07-17 21:27:17 +02:00

I can reproduce this.

I'm guessing what will happen is this will not be fixed since it is a corner case and the replacement system for proxies is coming soon™. @mont29 am I correct? If so, what to do with this report? Is there a point having something on Confirmed, when we know it's unlikely to be fixed?

I can reproduce this. I'm guessing what will happen is this will not be fixed since it is a corner case and the replacement system for proxies is coming soon™. @mont29 am I correct? If so, what to do with this report? Is there a point having something on Confirmed, when we know it's unlikely to be fixed?

Bastien Montagne commented

2019-09-04 17:08:35 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2019-09-04 17:08:35 +02:00

Bastien Montagne self-assigned this 2019-09-04 17:08:35 +02:00

Bastien Montagne commented

2019-09-04 17:08:35 +02:00

Issue here is actually that we never update bone constraints from bone layers that are not protected in the source armature (this allows users to remove constraints from bones of those unprotected layers as they like).

Since we cannot keep any pose info when the source linked IDs are missing (as we get an empty place-holder armature), there is no way to reconstruct that data once relocating the library, not automatically at least.

As @Mets said, proxy is considered in a frozen, pre-deprecation state now, so I don’t think it's worth spending more time trying to work around that issue. Hopefully library overrides will make that case easier to handle.

Thanks for the report anyway.

Issue here is actually that we never update bone constraints from bone layers that are not protected in the source armature (this allows users to remove constraints from bones of those unprotected layers as they like). Since we cannot keep any pose info when the source linked IDs are missing (as we get an empty place-holder armature), there is no way to reconstruct that data once relocating the library, not automatically at least. As @Mets said, proxy is considered in a frozen, pre-deprecation state now, so I don’t think it's worth spending more time trying to work around that issue. Hopefully library overrides will make that case easier to handle. Thanks for the report anyway.

Simone Barbieri commented

2020-01-13 11:25:24 +01:00

Added subscriber: @s.barbieri

Simone Barbieri commented

2020-01-13 11:25:24 +01:00

Sorry to comment on a closed task, but I'm having the same problem with the new library override system.

When relocating the library, all the bones constraints and custom objects are removed.

Sorry to comment on a closed task, but I'm having the same problem with the new library override system. When relocating the library, all the bones constraints and custom objects are removed.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Relocating linked armatures removes bone modifiers! #65483