Linked group breaks Object Mapping in Texture Coordinates #56534

New Issue

Sacha Goedegebure · 2018-08-25T11:52:54+02:00

Sacha Goedegebure commented

2018-08-25 11:52:54 +02:00

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

Link the group "object_mapping" from the blend file
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
object_mapping.blend

**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 [object_mapping.blend](https://archive.blender.org/developer/F4380315/object_mapping.blend)

Sacha Goedegebure commented

2018-08-25 11:52:54 +02:00

Added subscriber: @SachaGoedegebure

blender-admin commented

2018-08-25 11:52:54 +02:00

#98468 was marked as duplicate of this issue

blender-admin commented

2018-08-25 11:52:54 +02:00

#92949 was marked as duplicate of this issue

blender-admin commented

2018-08-25 11:52:54 +02:00

#76999 was marked as duplicate of this issue

blender-admin commented

2018-08-25 11:52:54 +02:00

#69014 was marked as duplicate of this issue

blender-admin commented

2018-08-25 11:52:54 +02:00

#68064 was marked as duplicate of this issue

blender-admin commented

2018-08-25 11:52:54 +02:00

#54316 was marked as duplicate of this issue

Bastien Montagne commented

2018-08-26 10:53:31 +02:00

Added subscribers: @brecht, @mont29

Brecht Van Lommel was assigned by Bastien Montagne

2018-08-26 10:53:31 +02:00

Bastien Montagne commented

2018-08-26 10:53:31 +02:00

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

@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…

Note that this is not related to linking, instantiating the group in original file shows exact same behavior. @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…

Sacha Goedegebure commented

2018-08-27 03:23:42 +02:00

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.

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 commented

2018-08-30 13:58:12 +02:00

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.

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.

Brecht Van Lommel commented

2019-02-01 19:12:15 +01:00

Added subscribers: @SteffenD, @ZedDB, @lichtwerk

Brecht Van Lommel commented

2019-08-01 18:23:01 +02:00

Added subscribers: @Raulus, @fclem

Philipp Oeser commented

2019-08-22 09:45:12 +02:00

Added subscriber: @BassamKurdali

bassam kurdali commented

2019-08-22 18:25:35 +02:00

I posted a workaround in 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 posted a workaround in [https://developer.blender.org/T69014 ](URL) 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)

Clément Foucault commented

2019-08-26 14:57:33 +02:00

Removed subscriber: @fclem

Brecht Van Lommel removed their assignment 2020-01-18 14:25:06 +01:00

Dmitry commented

2020-03-24 22:20:12 +01:00

Added subscriber: @DimaM