Cycles: Turning Off Ray Visibility Breaks Occlusion from Environment #43117

Closed
opened 2015-01-04 01:31:12 +01:00 by Zauber Paracelsus · 12 comments

System Information
64bit Ubuntu 14.04, kernel 3.13.0
GeForce GTX 650 Ti, driver version 331
Operating system and graphics card

Blender Version
Broken: 2.73, build c24b694

Short description of error
When you unset the Ray Visibility flags for an object, that object will cease to occlude the environment. The result is that if you have a box and turn off Ray Visibility for Diffuse, then any light from the environment will pass into the object's interior, as though it were not there.

Tested only with CPU and OSL rendering. Unable to test with GPU rendering, as for some reason CUDA no longer detects my GPU.

Exact steps for others to reproduce the error

  1. Download and open the following file:
  2. Set viewport mode to Rendered.
  3. Go to the panel on the lower right, under Ray Visibility.
  4. Unset the Diffuse flag, and note that the sphere turns red, and the surroundings turn bright gray.
  5. Set the Diffuse flag back, and then unset the Glossy flag. Note that the sphere turns blue.
**System Information** 64bit Ubuntu 14.04, kernel 3.13.0 GeForce GTX 650 Ti, driver version 331 Operating system and graphics card **Blender Version** Broken: 2.73, build c24b694 **Short description of error** When you unset the Ray Visibility flags for an object, that object will cease to occlude the environment. The result is that if you have a box and turn off Ray Visibility for Diffuse, then any light from the environment will pass into the object's interior, as though it were not there. Tested only with CPU and OSL rendering. Unable to test with GPU rendering, as for some reason CUDA no longer detects my GPU. **Exact steps for others to reproduce the error** 1) Download and open the following file: 2) Set viewport mode to Rendered. 2) Go to the panel on the lower right, under Ray Visibility. 3) Unset the Diffuse flag, and note that the sphere turns red, and the surroundings turn bright gray. 4) Set the Diffuse flag back, and then unset the Glossy flag. Note that the sphere turns blue.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @ZauberParacelsus

Added subscriber: @ZauberParacelsus
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Please post a .blend

Please post a .blend

Sorry, I accidentally deleted the link, fixing...

Sorry, I accidentally deleted the link, fixing...

Posting the blend in this comment, since I can't go back and edit the original post.

EnvironmentOcclusionBug.blend

Posting the blend in this comment, since I can't go back and edit the original post. [EnvironmentOcclusionBug.blend](https://archive.blender.org/developer/F135030/EnvironmentOcclusionBug.blend)

Added subscriber: @Sergey

Added subscriber: @Sergey

I'm not really sure what's the error in here? Disabled diffuse visibility makes it so diffuse component of the sphere becomes visible (because for that one lighting is no longer blocked by the box. Disabled glossy visibility means glossy component of sphere receives light.

Also, without glossy sphere is rather gray here than blue..

I'm not really sure what's the error in here? Disabled diffuse visibility makes it so diffuse component of the sphere becomes visible (because for that one lighting is no longer blocked by the box. Disabled glossy visibility means glossy component of sphere receives light. Also, without glossy sphere is rather gray here than blue..

You will note that in the scene there is a sun lamp. It has no influence upon the sphere unless you turn off Shadow visibility for the box.

That inconsistency is the problem. Environment Lighting should continue to be blocked just like any other light source when the box's diffuse visibility is turned off.

You will note that in the scene there is a sun lamp. It has no influence upon the sphere unless you turn off Shadow visibility for the box. That inconsistency is the problem. Environment Lighting should continue to be blocked just like any other light source when the box's diffuse visibility is turned off.

You can't really expect environment light to be the same as other light sources actually simply because of their shadow behavior. It would be weird to make it so environment light is affected by the shadow visibility because environment doesn't give shadows apart from AO shadows (which you can't currently control). And because "regular" light sources casts shadows and shadow rays are blocked sphere is not highlighted by the sun.

For me it doesn't seem to be inconsistency not having logic here.

You can't really expect environment light to be the same as other light sources actually simply because of their shadow behavior. It would be weird to make it so environment light is affected by the shadow visibility because environment doesn't give shadows apart from AO shadows (which you can't currently control). And because "regular" light sources casts shadows and shadow rays are blocked sphere is not highlighted by the sun. For me it doesn't seem to be inconsistency not having logic here.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2015-01-07 17:01:02 +01:00

Talked to some artists, and they also finds current behavior quite clear. Changing flags would break loads of scenes, so it should be much bigger outcome than subjective consistency feeling.

If it's really a stopper for your pipeline, then please be welcome to bf-cycles mailing list (http://lists.blender.org/mailman/listinfo/bf-cycles) so discussion raises with all the Cycles users.

In any case, don't consider this a bug, but thanks for the report anyway.

Talked to some artists, and they also finds current behavior quite clear. Changing flags would break loads of scenes, so it should be much bigger outcome than subjective consistency feeling. If it's really a stopper for your pipeline, then please be welcome to bf-cycles mailing list (http://lists.blender.org/mailman/listinfo/bf-cycles) so discussion raises with all the Cycles users. In any case, don't consider this a bug, but thanks for the report anyway.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser Project (Legacy)
Interest
Asset System
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
3 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#43117
No description provided.