Linked groups explode when moved/rotated #38801

New Issue

No. · 2014-02-24T11:06:07+01:00

No. commented

2014-02-24 11:06:07 +01:00

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

Create a thing
Create another thing
Link the first thing into the second thing
Play with it (move it, rotate it, whatever)
Press F12 or Shift+Z
Return to normal mode
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.blend

emblem.blend

**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.blend](https://archive.blender.org/developer/F78719/showcase.blend) [emblem.blend](https://archive.blender.org/developer/F78720/emblem.blend)

No. commented

2014-02-24 11:06:07 +01:00

Changed status to: 'Open'

No. commented

2014-02-24 11:06:07 +01:00

Added subscriber: @Karai17

Lukas Tönne self-assigned this 2014-02-24 14:38:15 +01:00

Lukas Tönne commented

2014-02-24 14:38:15 +01:00

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

Brecht Van Lommel commented

2014-02-24 17:52:50 +01:00

Added subscriber: @brecht

blender-admin commented

2014-02-24 19:00:44 +01:00

This issue was referenced by blender/blender-addons-contrib@188f8d0935

This issue was referenced by blender/blender-addons-contrib@188f8d093504aa3dcf28efc404c395ad43fc633f

blender-admin commented

2014-02-24 19:00:44 +01:00

This issue was referenced by 188f8d0935

This issue was referenced by 188f8d093504aa3dcf28efc404c395ad43fc633f

Lukas Tönne commented

2014-02-24 19:06:09 +01:00

Changed status from 'Open' to: 'Resolved'

Lukas Tönne closed this issue

2014-02-24 19:06:09 +01:00

Lukas Tönne commented

2014-02-24 19:06:09 +01:00

Closed by commit 188f8d0935.

Closed by commit 188f8d0935.

No. commented

2014-03-12 02:21:44 +01:00

Changed status from 'Resolved' to: 'Open'

No. reopened this issue

2014-03-12 02:21:44 +01:00

No. commented

2014-03-12 02:21:44 +01:00

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 commented

2014-03-12 18:44:15 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2014-03-12 18:44:15 +01:00

@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. commented

2014-03-12 20:24:56 +01:00

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.

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 ](https://www.dropbox.com/s/1uhnzhvt3u553jq/showcase.blend) [Staff ](https://www.dropbox.com/s/4rwwrmafz9xwt4a/staff.blend) *Unreliable in this sense is that every time I press F12 to refresh the render, the transform changes.

Lukas Tönne commented

2014-03-13 08:20:36 +01:00

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 ...

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 commented

2014-05-12 16:41:54 +02:00

Changed status from 'Open' to: 'Resolved'

Lukas Tönne closed this issue

2014-05-12 16:41:54 +02:00

Lukas Tönne commented

2014-05-12 16:41:54 +02:00

Closed by commit blender/blender-addons-contrib@188f8d0935.

Sign in to join this conversation.