Black boxes on a denoising render when using a .exr image as a environmental texture #51529
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#51529
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
OS: Windows 10
GPU: AMD 390X 8gb, latest drivers
CPU+RAM: i7-5820k, 32gb Ram
Blender Version
2.78
12651ab
I'm using the benchmark file from Gooseberry and when default rendering with denoise on the black boxes appear at random when denoise kicks in. But it only appears when rendering with '.exr' file as environmental texture. If I convert the same file to '.hdr' file then the boxes are gone. No visual difference noted except for the black boxes.
Changed status to: 'Open'
Added subscriber: @bigbad
Added subscriber: @SteffenD
This EXR coming with this scene is known to contain NaNs. Saving it to HDR format "fixes" this. But even saving it as a new EXR (I tried 16bit half-float with ZIPS compression) got rid of the black boxes.
If you load the original environment EXR into Natron it displays a yellow warning that it replaced some NaNs with white.
Added subscribers: @LukasStockner, @brecht, @Sergey
This is similar to bug i've fixed in
581c819
. Guess we need to move finiste check to image.cpp.@LukasStockner , @brecht, any objections on that?
Sounds fine if it doesn't cause a significant slowdown.
Releasing a fixed version of the scene would probably also be a good idea, this is the third "bug" caused by that HDR.
This issue was referenced by blender/cycles@081d59035b
This issue was referenced by
1d49205b1a
Changed status from 'Open' to: 'Resolved'
I'm not sure if we should release a fixed scene, testing if we handle weird HDR images correct is also valuable since users will likely encounter the as well.
Added subscriber: @bliblubli
@brecht and @Sergey wouldn't it be better and possible to take last valid texel value instead of 0,0,0 for replacing NaNs while cycling through all the texels of the texture?