Page MenuHome

Linked group breaks Object Mapping in Texture Coordinates
Confirmed, NormalPublicTO DO

Description

System Information
Windows 10

Blender Version
Broken: 2.79b official release

Short description of error
Linked group breaks Object Mapping in Texture Coordinates, when:

  • a texture (on a plane) uses another object (empty) as texture coordinates
  • all objects are in the same group

Further explanation in the blend file.

Exact steps for others to reproduce the error

  1. Link the group "object_mapping" from the blend file
  2. move the group in any direction

Despite the gradient texture on the plane using the empty's coordinates, this is completely ignored once linked as a group

Event Timeline

Bastien Montagne (mont29) lowered the priority of this task from 90 to Normal.

Note that this is not related to linking, instantiating the group in original file shows exact same behavior.

@Brecht Van Lommel (brecht) I believe that’s related to how Cycles handle that kind of coordinates? Not sure that is actually a bug, nor fixable, though, since I do not see how code could know which dupliobject to use to generate coordinates instead of using actual original object…

oh yeah, I could've just instance it in the same file.

This does make Object mapping less useful for groups. After linking the group, I tried to bypass it by making the empty proxy, or with 'Make Duplicates Real', but none of these methods work.

Brecht Van Lommel (brecht) triaged this task as 50 priority.Aug 30 2018, 1:58 PM

The solution to this is probably rather complicated, particularly if there are multiple object instances or the material is used by multiple objects.

I think it would involve finding the object "closest" to another object in the group hierarchy, and storing this transform as an object attribute rather than a material attribute.

I posted a workaround in [[ URL | https://developer.blender.org/T69014 ]]
Basically if you parent everything to the rig that you then proxy, moving the rig object should be sufficient to keep everything in sync (and not moving the instance origin)
Note that workarounds can be more complex in more complex rigs (my original rig is like that)

I faced this in 2.82a. As for Cycles so for Eevee. I don't know how to add a tag here. And I made proxies for everything.