Density of volume shader doesn't change/react on input value #96795

Closed
opened 2022-03-26 11:00:32 +01:00 by Christoph Duyster · 9 comments

System Information
Operating system: macOS-12.1-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Max Apple 4.1 Metal - 76.3

Blender Version
Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: f1cca30557
Worked: (newest version of Blender that worked as expected)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

I try to change the density of my volume shader based on the distance of 2 objects.

image.png

So i have this GN node tree, which obviously works because the distance value is coming over as you can see if i plugin my shader:

image.png

But if i want to see my volume shader....it looks like a constant value. So maybe i am making a stupid mistake or it is a bug...

image.png
density_by_distance.blend

**System Information** Operating system: macOS-12.1-arm64-arm-64bit 64 Bits Graphics card: Apple M1 Max Apple 4.1 Metal - 76.3 **Blender Version** Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: `f1cca30557` Worked: (newest version of Blender that worked as expected) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] I try to change the density of my volume shader based on the distance of 2 objects. ![image.png](https://archive.blender.org/developer/F12948040/image.png) So i have this GN node tree, which obviously works because the distance value is coming over as you can see if i plugin my shader: ![image.png](https://archive.blender.org/developer/F12948034/image.png) But if i want to see my volume shader....it looks like a constant value. So maybe i am making a stupid mistake or it is a bug... ![image.png](https://archive.blender.org/developer/F12948037/image.png) [density_by_distance.blend](https://archive.blender.org/developer/F12948030/density_by_distance.blend)

Added subscriber: @LuckyChris

Added subscriber: @LuckyChris

#96521 was marked as duplicate of this issue

#96521 was marked as duplicate of this issue
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Added subscribers: @brecht, @lichtwerk

Added subscribers: @brecht, @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

You cant use face/vertex based information in a volume shader, can you?
The distance in a shader works if you are rendering this on the surface, yes, but not so if done in a volume.
Dont think this has anything to do with the fact this is coming from geometry nodes, same is true for regular textures or vertex colors.

I think this can be closed (@brecht: correct me if I am wrong).

You cant use face/vertex based information in a volume shader, can you? The distance in a shader works if you are rendering this on the surface, yes, but not so if done in a volume. Dont think this has anything to do with the fact this is coming from geometry nodes, same is true for regular textures or vertex colors. I think this can be closed (@brecht: correct me if I am wrong).

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

This is a limitation, there is no way to interpolate surface attributes into the volume. In the future there may be geometry nodes that help with that kind of thing, doing it at render time would be expensive.

This is a limitation, there is no way to interpolate surface attributes into the volume. In the future there may be geometry nodes that help with that kind of thing, doing it at render time would be expensive.
Member

Added subscriber: @Mantissa

Added subscriber: @Mantissa
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
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
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
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
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 Info 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
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#96795
No description provided.