Maniphest T38801

Linked groups explode when moved/rotated
Closed, Resolved
Actions

Assigned To
Lukas Tönne (lukastoenne)
Authored By
No. (Karai17)
Feb 24 2014, 11:06 AM
Tags
  • BF Blender
Subscribers
Brecht Van Lommel (brecht)
Campbell Barton (campbellbarton)
Lukas Tönne (lukastoenne)
No. (Karai17)

Description

System Information
Windows 7 Professional x86_64
nVidia GTX 550 Ti

Blender Version
Broken: 2.69.11
Worked: 2.69

Short description of error
If you link a group form another Blender file to your project and interact with it in any way (move it, rotate it, etc), really weird things happen when trying to render.

Exact steps for others to reproduce the error

  1. Create a thing
  2. Create another thing
  3. Link the first thing into the second thing
  4. Play with it (move it, rotate it, whatever)
  5. Press F12 or Shift+Z
  6. Return to normal mode
  7. The linked thing may now contain very bizarre graphical glitches, such as objects seriously out of place or missing.

Note that this does not only happen with Empties as in the example below, this is also affected by chain-linked groups.

showcase.blend484 KBDownload

emblem.blend521 KBDownload

Revisions and Commits

rB Blender
rB188f8d093504 Fix T38801: Dupli objects with modifiers exhibit bad transform artifacts in…
rBAC Blender Add-ons Contrib
rBAC188f8d093504 Fix T38801: Dupli objects with modifiers exhibit bad transform artifacts in…

Event Timeline

No. (Karai17) created this task.Feb 24 2014, 11:06 AM
No. (Karai17) raised the priority of this task from to 90.
No. (Karai17) updated the task description.
No. (Karai17) added a project: BF Blender.
No. (Karai17) edited a custom field.
No. (Karai17) added a subscriber: No. (Karai17).
Lukas Tönne (lukastoenne) claimed this task.Feb 24 2014, 2:38 PM

Probably my own mistake in recent dupli changes relating to obmat overrides ...

Lukas Tönne (lukastoenne) lowered the priority of this task from 90 to 50.Feb 24 2014, 2:38 PM
Brecht Van Lommel (brecht) added a project: Blender 2.70.Feb 24 2014, 5:52 PM
Brecht Van Lommel (brecht) added a subscriber: Brecht Van Lommel (brecht).
Lukas Tönne (lukastoenne) edited this Maniphest Task.Feb 24 2014, 7:06 PM
Lukas Tönne (lukastoenne) changed the task status from Unknown Status to Resolved.Feb 24 2014, 7:06 PM

Closed by commit rB188f8d093504.

No. (Karai17) changed the task status from Resolved to Unknown Status.Mar 12 2014, 2:21 AM

So uh, this appears to still be a problem in 2.70 RC1... But not with the files I have currently linked. I'm still trying to figure out the test case, but when I render a more complex file, things explode and ar eno appropriately placed..

Campbell Barton (campbellbarton) added a subscriber: Campbell Barton (campbellbarton).Mar 12 2014, 6:44 PM

@No. (Karai17) - hi, its really important we get some test file we can redo the problem - this is the only bug tagged as blocking 2.70 release at the moment.

No. (Karai17) added a comment.Mar 12 2014, 8:24 PM

Okay I have seemed to isolate the problem again. Opening the showcase.blend file I've linked below (I cannot seem to find how to upload more files), if you render the image using F12, everything is fine. If you create a copy (shift+D) of the staff, again, everything is fine. HOWEVER! If you MOVE either the original or copy in any way (grab, scale, rotate), BOTH staves will have incorrect and unreliable* transforms. If you only have one staff and move it in any way, again, it has incorrect and unreliable transforms.

Showcase

Staff

*Unreliable in this sense is that every time I press F12 to refresh the render, the transform changes.

Lukas Tönne (lukastoenne) added a comment.Mar 13 2014, 8:20 AM

I can confirm the render is broken, even without duplicating the group instance.

However this does not seem to be a regression, the same error happens in 2.69 already. Looks like Blender Internal's way of evaluating dupli obmats is really fragile when it comes to nested groups ...

Lukas Tönne (lukastoenne) removed a project: Blender 2.70.Mar 13 2014, 8:22 AM
Lukas Tönne (lukastoenne) edited this Maniphest Task.May 12 2014, 4:41 PM
Lukas Tönne (lukastoenne) changed the task status from Unknown Status to Resolved.May 12 2014, 4:41 PM

Closed by commit rBAC188f8d093504.