object coordinate (using an empty) in Cycles volumetric shader not moving with object in linked/instanced group. #69014

Closed
opened 4 years ago by BassamKurdali · 5 comments

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: f6cb5f5449
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 bugtest_src.blend
2- Download the file bugtest_scene.blend 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.

**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: `f6cb5f5449` 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 [bugtest_src.blend](https://archive.blender.org/developer/F7683209/bugtest_src.blend) 2- Download the file bugtest_scene.blend [bugtest_scene.blend](https://archive.blender.org/developer/F7683214/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.
Poster

Added subscriber: @BassamKurdali

Added subscriber: @BassamKurdali
Poster

I'm not 100% sure this is a bug. would need a depsgraph or cycles dev (or both) to comment.

I'm not 100% sure this is a bug. would need a depsgraph or cycles dev (or both) to comment.
Collaborator

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Collaborator

This looks like a duplicate of #56534

This looks like a duplicate of #56534
Collaborator

Closed as duplicate of #56534

Closed as duplicate of #56534
lichtwerk closed this issue 4 years ago
Sign in to join this conversation.
No Label
Interest/Alembic
Interest/Animation & Rigging
Interest/Asset Browser
Interest/Asset Browser Project Overview
Interest/Audio
Interest/Automated Testing
Interest/Blender Asset Bundle
Interest/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/ID Management
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Masking
Interest/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
Interest/Python API
Interest/Render & Cycles
Interest/Render Pipeline
Interest/Sculpt, Paint & Texture
Interest/Text Editor
Interest/Translations
Interest/Triaging
Interest/Undo
Interest/USD
Interest/User Interface
Interest/UV Editing
Interest/VFX & Video
Interest/Video Sequencer
Interest/Virtual Reality
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
Module › Animation & Rigging
Module › Core
Module › Development Management
Module › Eevee & Viewport
Module › Grease Pencil
Module › Modeling
Module › Nodes & Physics
Module › Pipeline, Assets & IO
Module › Platforms, Builds, Tests & Devices
Module › Python API
Module › Render & Cycles
Module › Sculpt, Paint & Texture
Module › Triaging
Module › User Interface
Module › VFX & Video
Platform/FreeBSD
Platform/Linux
Platform/macOS
Platform/Windows
Priority › High
Priority › Low
Priority › Normal
Priority › Unbreak Now!
Status › Archived
Status › Confirmed
Status › Duplicate
Status › Needs Information from Developers
Status › Needs Information from User
Status › Needs Triage
Status › Resolved
Type › Bug
Type › Design
Type › Known Issue
Type › Patch
Type › Report
Type › To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#69014
Loading…
There is no content yet.