Page MenuHome

object coordinate (using an empty) in Cycles volumetric shader not moving with object in linked/instanced group.
Closed, DuplicatePublic

Description

System Information
Operating system: Linux-5.1.17-300.fc30.x86_64-x86_64-with-fedora-30-Thirty 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e
Worked: Unknown

Short description of error
I have a volumetric material that uses an empty object coordinates for a gradient texture that influences color (cycles render)
This material is on an object that is part of a collection. Moving the empty in the library file works fine, but, when linking the entire collection (and instancing it) moving the instance keeps the texture coordinate at the original location, instead of moving with the collection. It's like the dependency is being ignored but in the material only.

Exact steps for others to reproduce the error
1- Download the file bugtest_src.blend


2- Download the file bugtest_scene.blend
3- Open the file bugtest_scene.blend, and switch the viewport to rendered shading
4- Observe the white circle in the volumetric cube, and the empty sticking out of it (locating it)
5- Move the instance in the scene, and observe that the white circle doesn't move with it, but stays in the original mapping, potentially dis-appearing altogether if you move the instance far enough.
What should happen:
The white circle should move with instanced empty (well maybe - perhaps this is intended behavior?)
Workaround:
Parenting all objects to a proxy and moving the proxy alone, leaving the instance at the origin.