Page MenuHome

Constraint on Linked Armature broken.
Closed, InvalidPublic


System Information
Win 10 Pro 2 X Asus Rog II

Blender Version
Broken: 2.79a
Worked: 2.78

Short description of error

Constraint won't follow proxied armature's bone correctly in any given space.

Exact steps for others to reproduce the error

A portion of my project directory is in this archive:

Just open the scene file "SHOT_06_RV01_01.blend" in the "Scenes" folder of the project directory and check out the empty named "CAM TARGET" which has a 'Copy Transforms' constraint applied to it and is constrained to the bone named "Forward" in the rig armature of the plane which is linked from the "Source_Blends" folder. It should stick to the bone's center in world space, instead it is dubiously offset some amount.

Been working on this in 2.79a RC, due to the fact that 2.79 is just too buggy to do any serious work on (randomly and persistently crashes like crazy when you interact with the armature)



Event Timeline

It's been 5 days since I submitted this report, no response?

Bastien Montagne (mont29) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Feb 27 2018, 8:51 AM

Is there any reason why you do not assign the proxy's bone as target of your constraint?

Not sure what happens here, but it does not seem to be an update issue, more like 'something' somewhere in the file which generates that offset. Maybe the original offset of the armature withing its linked group, or something like that? In any case, trying to reproduce such thing from scratch in a dead simple .blend file (instead of a production one) would make things much easier to investigate.

For what is worth, tried your file with 2.78c and 2.77, and both exhibit that same gap too, so this is not a regression (not a recent one at least). And we want to get rid of proxies altogether, kind of feeling worthless to spend time on this now, since there is an easy and obvious workaround…

Dear Bastien;

Thank you so much for taking the time to check out my scene. I sincerely owe you an apology, for I re-checked the scene file myself, and found out that I mistakenly transformed the proxy itself by certain units, hence resulting in a double-transform situation. I know that you guys are real busy with both a point release and 2.8, so please accept my apologies for taking your time with something so obvious. This is the second time this month, and it really kinda makes me feel bad :(

Doing away with proxies would be absolutely great imo. As of yet, referencing (linking) in Blender could be tad cloggy in certain production situations. I have my fingers crossed for a referencing system that is akin to some of Blender's industry counterparts, like with an editor and multiple file referencing of the same scene to name a few.

God speed in your work.



Thanks, we can close that one then :)