Volume Density Cap in Cycles #104227

Closed
opened 2023-01-30 05:34:00 +01:00 by Martín Sanchez · 6 comments

System Information
Operating system: Manjaro Linux 22.0 x64
Graphics card: NVIDIA GeForce RTX 3080 ti with proprietary drivers 525.85.05
Proccessor: AMD Ryzen 9 5900x
RAM: 64gb DDR4
system-info.txt

Blender Version
Blender 3.4.1

Short description of error
The density in the volume shaders (both "Principled Volume" and "Volume scatter"), I think they do not work correctly.

I attach 4 images where you can see a simple configuration of a volume material. As the density increases (through a multiply), in Eevee it correctly sees the density increase of the volume but in Cycles it "stuck" at a value close to 1 and then does not increase the density any more. Occurs on both CPU and GPU (CUDA and Optix).

Exact steps for others to reproduce the error

  • Create an empty file.
  • Add a cube and scale 2-3x.
  • Assign him the material shown in the attached images.
  • Modify the multiply value and display in Eevee and Cycles.

Cycles - Multiply 100.png

Eevee - Multiply 100.png

Eeve - Multiply 1.png

Cycles - Multiply 1.png

**System Information** Operating system: Manjaro Linux 22.0 x64 Graphics card: NVIDIA GeForce RTX 3080 ti with proprietary drivers 525.85.05 Proccessor: AMD Ryzen 9 5900x RAM: 64gb DDR4 [system-info.txt](https://archive.blender.org/developer/F14214195/system-info.txt) **Blender Version** Blender 3.4.1 **Short description of error** The density in the volume shaders (both "Principled Volume" and "Volume scatter"), I think they do not work correctly. I attach 4 images where you can see a simple configuration of a volume material. As the density increases (through a multiply), in Eevee it correctly sees the density increase of the volume but in Cycles it "stuck" at a value close to 1 and then does not increase the density any more. Occurs on both CPU and GPU (CUDA and Optix). **Exact steps for others to reproduce the error** - Create an empty file. - Add a cube and scale 2-3x. - Assign him the material shown in the attached images. - Modify the multiply value and display in Eevee and Cycles. ![Cycles - Multiply 100.png](https://archive.blender.org/developer/F14211519/Cycles_-_Multiply_100.png) ![Eevee - Multiply 100.png](https://archive.blender.org/developer/F14211518/Eevee_-_Multiply_100.png) ![Eeve - Multiply 1.png](https://archive.blender.org/developer/F14211517/Eeve_-_Multiply_1.png) ![Cycles - Multiply 1.png](https://archive.blender.org/developer/F14211516/Cycles_-_Multiply_1.png)

Added subscriber: @MartinSanchez-3

Added subscriber: @MartinSanchez-3
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Hi, thanks for the report. Please share .blend file. I'm not able to replicate this locally in 3.4

Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78```
Hi, thanks for the report. Please share .blend file. I'm not able to replicate this locally in 3.4 ```**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78```

Hello! Thank you very much for your quick response.

I continued to investigate the issue. Apparently there is an option in the volume options in "Render Properties" called Steps "Rate Render" and by reducing that value the render looks correct. I guess it's set to 1 for performance reasons.
So it would be resolved, it is not a bug but something I was unaware of its existence. I apologize, I didn't know about that option.

Thank you!

Hello! Thank you very much for your quick response. I continued to investigate the issue. Apparently there is an option in the volume options in "Render Properties" called Steps "Rate Render" and by reducing that value the render looks correct. I guess it's set to 1 for performance reasons. So it would be resolved, it is not a bug but something I was unaware of its existence. I apologize, I didn't know about that option. Thank you!
Member

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
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
2 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#104227
No description provided.