Page MenuHome

Relocating linked armatures removes bone modifiers!
Closed, ArchivedPublic

Description

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

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)

  1. Place my file in some folder
  2. 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)
  3. Make the new file use relative paths and save
  4. Move my file to a new folder location
  5. Open the linking file you created. Outline > Blender File > RMB on broken link > Relocate
  6. After locating the file, it is loaded in without any constraints

Event Timeline

Bastien Montagne (mont29) lowered the priority of this task from 90 to 30.Jun 4 2019, 5:15 PM

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.

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?

Karlo (kpavicic) updated the task description. (Show Details)
Demeter Dzadik (Mets) raised the priority of this task from 30 to 90.EditedJul 17 2019, 9:27 PM

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™. @Bastien Montagne (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 (mont29) changed the task status from Unknown Status to Unknown Status.Sep 4 2019, 5:08 PM
Bastien Montagne (mont29) claimed this task.

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 @Demeter Dzadik (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.

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.