Point light not working properly inside a volume while rendering with GPU #47649

New Issue

Pablo · 2016-03-01T21:38:34+01:00

Pablo commented

2016-03-01 21:38:34 +01:00

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

**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](https://archive.blender.org/developer/F286551/error1.blend) Blend file with the problem ![2.77 CPU.png](https://archive.blender.org/developer/F286553/2.77_CPU.png) CPU viewport, working fine ![2.77 GPU.png](https://archive.blender.org/developer/F286555/2.77_GPU.png) GPU viewport, not working properly

Pablo commented

2016-03-01 21:38:34 +01:00

Changed status to: 'Open'

Pablo commented

2016-03-01 21:38:34 +01:00

Added subscriber: @Pablo-Trensardina

blender-admin commented

2016-03-01 21:38:34 +01:00

#47656 was marked as duplicate of this issue

Wolfgang Faehnle commented

2016-03-01 22:04:55 +01:00

Added subscriber: @mib2berlin

Wolfgang Faehnle commented

2016-03-01 22:04:55 +01:00

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.

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.

Cenek Strichel commented

2016-03-02 03:37:26 +01:00

Added subscriber: @Cenda

Cenek Strichel commented

2016-03-02 03:37:26 +01:00

I can confirm bug. GF960 GTX, Win10 64b, Blender 2.77RC1
2.76b is fine

I can confirm bug. GF960 GTX, Win10 64b, Blender 2.77RC1 2.76b is fine

Wolfgang Faehnle commented

2016-03-02 03:58:11 +01:00

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

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

Sergey Sharybin commented

2016-03-02 11:13:11 +01:00

Added subscribers: @ideasman42, @Sergey

Campbell Barton was assigned by Sergey Sharybin

2016-03-02 11:13:11 +01:00

Sergey Sharybin commented

2016-03-02 11:13:11 +01:00

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,

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,

Sergey Sharybin commented

2016-03-02 12:49:48 +01:00

Added subscriber: @lsscpp