Page MenuHome

Grouping with turned off DupliVisibility and linking twice causes posed mesh to distort (Armature mod refers to wrong instance?)
Closed, ArchivedPublic


--- Operating System, Graphics card ---
Win8 64bit GTX660 (v2.65a)
Win7 64bit GTX560Ti (v2.63a)

--- Blender version with error, and version that worked ---
Error on 2.65a, 2.63a & 2.65.9r54003

--- Short description of error ---
Create a human (and hide armature in group prop) on 1st file
then link to the human and duplicate to create flock group on 2nd file
then link to the flock of humans on 3rd file.
Reopen after saving last file causes human body to distort.

--- Steps for others to reproduce the error (preferably based on attached .blend file) ---
1st file.------
1.Create simple armature and mesh object then parent with auto-weight.
(2.Change pose to easily distinct the error at last.)
3.Group two objects.
4.Move the armature to Layer11 then turn off visibility of the layer of the Group
2nd file----
5.Link to the Group from new blend file.
6.Duplicate Empty then group these empties.
3rd file ---
7.Link to the Group in 2nd file from new blend file.
8.Save it then reopen it. (Seemed normal before reopen it)
9.Distorted mesh appears.

*If turned on the DupliVisibility in first file, the bug is gone.
*Save and reopen last file is required to see the bug.
*Ctl+Shift+A on last file shows that distorted mesh's modifier points wrong armature instance.
*(Attached image) Clicking on Pose in Outliner on 2nd file causes Blender to crash.
I don't know the crash relates to this article but suspecting.


To Do

Event Timeline

Sounds like another juciy dupligroups+linking instancing bug.

Thoughts Ton?

Thanks for the very well documented report.

This kind of recursion for groups is not supported for animated systems, only for static objects...
If you want to link in character groups, that group should not have linked groups inside.

Obviously it should work - but that's a huge project we keep postponing for its complexity (The "Dependecy Graph" project).
We collect such issues here in wiki for future reference. When we pick up the project we'll revisit this report!

Ton Roosendaal (ton) closed this task as Archived.Feb 8 2013, 6:25 PM