Wrong render with HDRi when there Sun lamp with strength=0 #48790
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#48790
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
Kubuntu Linux 14.04, GTX 960
Blender Version
Broken: from master, 2.77.1
39ae324
Worked: 2.77a
Short description of error
Wrong render with HDRi when there Sun lamp in the scene with strength=0
Exact steps for others to reproduce the error
Scene: hdri_sun0.blend
HDRi: https://hdrihaven.com/hdri.php?hdri=sisulu&dl=yes
Open the scene. Load the HDRi (it is not packed). Render.
Changed status to: 'Open'
Added subscriber: @YAFU
Sorry, this happens with any type of lamp with strength=0
Added subscriber: @ideasman42
Renders black when the strength is 0.0, both for 2.77a and master (
9269574089a742130f02c0a1184a19d94f0e665d
)Hi.
On my machine the render looks good with 2.77a (
abf6f08
):Added subscriber: @Sergey
The file has
Strength
of 1.0. Setting it to 0.0 makes everything black (as expected).Perhaps I have not been clear here. Apparently you refer to World (HDRi environment texture) strength. You do not touch that value in the scene, you leave that value to 1. With "strength=0" I am referring to the lamp selected by default when you open the scene. You just open the scene and render in Belnder from master (Do not forget to load the HDRi). Did you not get a resulting image like the first image I've shared?. I think it should look like the second image I obtained in Blender 2.77a.
I know, there is no logical reason to put there a lamp with strenght=0. But anyway I do not see any reason to get a resulting image like the obtained from master (first image).
EDIT:
Regarding whether this occurs in CPU/GPU, master/buildbot:
Buildbot
b27322e
:GPU: That diagonal division is very noticeable
CPU: That diagonal division is a bit less noticeable than GPU, but still noticeable.
Compiled from Master
39ae324
:GPU: That diagonal division is very noticeable
CPU: That diagonal division barely noticeable, mainly it is more noticeable when it begins to render the first samples.
Added subscribers: @ThomasDinges, @mont29
Can’t confirm this with CPU rendering indeed, don’t have GPU one here… But imho you are stressing system out of expected 'domain', what’s the point in testing something with zero-strength lamp?
Anyway, @Sergey or @ThomasDinges, can you reproduce the issue now with specified steps?
Hello Bastien!
Oh no. No point at all.
I just was testing another scene where I was working, and I wanted to see the render without the influence of the Sun lamp. As I usually find the outliner a bit complicated, I just decided to put Sun strength=0, then I found the problem . Then I discovered that this did not occur in previous versions of Blender, and then build a small scene and report just in case.
I do not know, maybe in a very large and complex scene a little experienced artist (like me) could be left forgotten there a lamp with strength=0. But I guess it will not be very common cases.
By the way, the problem is still present in my machine and last buildbot.
@YAFU, with the detailed explanation now i see what you mean :) Indeed see the bug here. Investigating...
Added subscriber: @brecht
@brecht, apparently caused by
42aec3b
. Setting strength is required to make it so you're leaving with lamp shader with just output node. You can also simply remove any connection from lamp shader outputs to see the same issue.This issue was referenced by blender/cycles@1f49c7bc43
This issue was referenced by
b645e7081d
The issue was in earlier code to disable lights, but better constant folding made it apparent.
Changed status from 'Open' to: 'Resolved'
@brecht, interesting. Because i was unable to reproduce issue with a revision previous to node refactor. Could have been some red-herring or just some unrelated changes made it visible. Thanks for the fix!
Working well now.
Thanks.