Point light not working properly inside a volume while rendering with GPU #47649
Labels
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#47649
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 10 64 bits, Nvidia GTX 670
Blender Version
Broken: Blender 2.77 RC 1
b594b25
Short description of error
Point light not working properly inside a volume while using GPU. It lightens the material, but not interacts with the volume. With CPU rendering, it works fine.
Exact steps for others to reproduce the error
Place a point light inside a volume, with another mesh to lighten.
The light in the example comes from HDRI environment map and from point light.
error1.blend Blend file with the problem
CPU viewport, working fine
GPU viewport, not working properly
Changed status to: 'Open'
Added subscriber: @Pablo-Trensardina
#47656 was marked as duplicate of this issue
Added subscriber: @mib2berlin
Cant verify on Blender 2.77 RC1.
Hi you set all samples to 0 in Sampling setting.
No Bug.
Opensuse Tumbleweed x86_64
Intel i5 3570K
GTX 760 4 GB /Display card
GTX 670 2 GB
Driver 361.28
Intel opencl_runtime_15.1_x64_5.0.0.57
EDIT: Don´t saw sampler settings at first view.
Added subscriber: @Cenda
I can confirm bug. GF960 GTX, Win10 64b, Blender 2.77RC1
2.76b is fine
Hi Cenek, you cant set sampling to 0 in 2.76b, it automatically switch to 1.
If you switch volume samples to 1 in 2.77 RC1 it is working too.
Mib
Added subscribers: @ideasman42, @Sergey
This is a forbidden configuration, which should not have ever happened. I managed to "break" the setup using python code, this will be fixed by @ideasman42 soon.
I also found default value for volume samples was wrong, it was fixed in
3d3d491
.The reason it works in 2.76b is because buttons were allowed to clamp values on display, which was causing other issues.
Just set samples to 1, and wait Campbell to fix python bindings so scripts can't violate this again,
Added subscriber: @lsscpp
Range clamping is working correctly now -
e4e21480d6
Changed status from 'Open' to: 'Resolved'
Considering the issue solved now. Thanks for the report!