Arbitrary Object Texture Coodinate won't work on Instaced Collections. #98468

New Issue

Julio Cargnin Pereira · 2022-05-28T16:23:11+02:00

2022-05-28 16:23:11 +02:00

System Information
Operating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.68.02

Blender Version
Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: cc66d1020c
Worked: (newest version of Blender that worked as expected)

Short description of error
A material with a custom object on Texture Coordinate node will have its coordinate left behind when instanced from a collection even if you parent the custom object to the material holder.

Exact steps for others to reproduce the error
Add an Empty;
Add a Material to the Default Cube;
Add Texture Coordinate Node and set the Empty as Custom Source;
Plug the Object Output to the Material Output and preview the Shading.
Parent the Empty to the Cube just in case;
Move the Cube;

Here it's all correct. The coordinate keeps relative to the Cube as expected as the Empty is being transformed along with it.

Now the problem:
Instance the collection where the Cube and the Empty belong to;
Move the Instanced Collection.
Result: The coordinate does not move along with the Empty within the instanced Collection.

sample files:
Arbitrary Object Space Bug on Linked Collection.zip

video:
Object-Space-Bug_.mp4

I'm not 100% sure if this is the expected behavior but this seems a very dangerous workflow and counter intuitive if you plan to instance something created like that.

**System Information** Operating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.31 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.68.02 **Blender Version** Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: `cc66d1020c` Worked: (newest version of Blender that worked as expected) **Short description of error** A material with a custom object on Texture Coordinate node will have its coordinate left behind when instanced from a collection even if you parent the custom object to the material holder. **Exact steps for others to reproduce the error** Add an Empty; Add a Material to the Default Cube; Add Texture Coordinate Node and set the Empty as Custom Source; Plug the Object Output to the Material Output and preview the Shading. Parent the Empty to the Cube just in case; Move the Cube; Here it's all correct. The coordinate keeps relative to the Cube as expected as the Empty is being transformed along with it. Now the problem: Instance the collection where the Cube and the Empty belong to; Move the Instanced Collection. Result: The coordinate does not move along with the Empty within the instanced Collection. sample files: [Arbitrary Object Space Bug on Linked Collection.zip](https://archive.blender.org/developer/F13118253/Arbitrary_Object_Space_Bug_on_Linked_Collection.zip) video: [Object-Space-Bug_.mp4](https://archive.blender.org/developer/F13118328/Object-Space-Bug_.mp4) I'm not 100% sure if this is the expected behavior but this seems a very dangerous workflow and counter intuitive if you plan to instance something created like that.

Julio Cargnin Pereira commented

2022-05-28 16:23:11 +02:00

Added subscriber: @CosmoMidias

Richard Antalik commented

2022-05-30 01:16:45 +02:00

Closed as duplicate of #56534

Richard Antalik closed this issue

2022-05-30 01:16:45 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Arbitrary Object Texture Coodinate won't work on Instaced Collections. #98468