Light Portals have no apparent effect with Branched Path Tracing #44528

Closed
opened 2015-04-28 01:29:08 +02:00 by Zauber Paracelsus · 6 comments

System Information
64bit Manjaro Linux, kernel 3.19
GeForce GTX 650 Ti Boost, driver 346.59

Blender Version
Broken: 2.75 dev, hash 4288ab1

Short description of error
I was trying out the new Light Portals feature with a simple scene, and I found that, while it produced differing images with the default Path Tracing integrator, it had no efffect with the Branched Path Tracing integrator, and the two renders with it enabled and disabled were visually identical, but took about 3x longer to render. On the other hand, when Sample All Direct Lights and Sample All Indirect Lights are turned off, it begins to work, but portals instead seem to increase the amount of noise.

So, I'm guessing that either Branched PT is already better at what light portals do, or it simply isn't effective with Branched PT?

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
This is the .blend file I used for testing: SimplePortalsTest.blend

**System Information** 64bit Manjaro Linux, kernel 3.19 GeForce GTX 650 Ti Boost, driver 346.59 **Blender Version** Broken: 2.75 dev, hash 4288ab1 **Short description of error** I was trying out the new Light Portals feature with a simple scene, and I found that, while it produced differing images with the default Path Tracing integrator, it had no efffect with the Branched Path Tracing integrator, and the two renders with it enabled and disabled were visually identical, but took about 3x longer to render. On the other hand, when Sample All Direct Lights and Sample All Indirect Lights are turned off, it begins to work, but portals instead seem to increase the amount of noise. So, I'm guessing that either Branched PT is already better at what light portals do, or it simply isn't effective with Branched PT? **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps This is the .blend file I used for testing: [SimplePortalsTest.blend](https://archive.blender.org/developer/F167396/SimplePortalsTest.blend)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @ZauberParacelsus

Added subscriber: @ZauberParacelsus

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2015-04-28 11:04:29 +02:00

It's not about branched/non-branched path tracing, in your portals are used wrong.

  • Portal's size is cricial, it needs to cover whole area from where background light is coming. You've got it default size which is waaaaay to small comparing with the door frame
  • Background light is crucial word here, currently portals does not guide anything apart from light emitted by the background itself. In your setup majority of the light is coming from the sun.

Here's a modified .blend which shows portals in action: SimplePortalsTest.blend

Thanks for the report, but further improvements of new features is something what happens naturally and we can't (for some unspeakable reason ;) to have all cases covered with initial commit of some new feature.

It's not about branched/non-branched path tracing, in your portals are used wrong. - Portal's size is cricial, it needs to cover whole area from where background light is coming. You've got it default size which is waaaaay to small comparing with the door frame - Background light is crucial word here, currently portals does not guide anything apart from light emitted by the background itself. In your setup majority of the light is coming from the sun. Here's a modified .blend which shows portals in action: [SimplePortalsTest.blend](https://archive.blender.org/developer/F167590/SimplePortalsTest.blend) Thanks for the report, but further improvements of new features is something what happens naturally and we can't (for some unspeakable reason ;) to have all cases covered with initial commit of some new feature.

What do you mean default size? I made sure to scale it up because I assumed that was necesary! Even reopening the original file just now, I can see that the area lamp is the correct size (though the viewport has to be set to wireframe in order to see it).

SimplePortalTest_Wireframe.png

I even downloaded the copy I had uploaded, and it also is the correct size.

What do you mean default size? I made sure to scale it up because I assumed that was necesary! Even reopening the original file just now, I can see that the area lamp is the correct size (though the viewport has to be set to wireframe in order to see it). ![SimplePortalTest_Wireframe.png](https://archive.blender.org/developer/F167640/SimplePortalTest_Wireframe.png) I even downloaded the copy I had uploaded, and it also is the correct size.

Anyways, feel free to close the report. I had a misunderstanding of what the light portals were used for.

Anyways, feel free to close the report. I had a misunderstanding of what the light portals were used for.
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#44528
No description provided.