The Denoise Node Turns the Rendered Image into Pure Black at the Resolution of 1920 *1920 #76668
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
16 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#76668
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
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87
CPU: Intel Core i7-8550U
Blender Version
Broken: version: 2.90 (sub 1), branch: master, commit date: 2020-05-11 21:02, hash:
542ff416e2Worked: Never
Short description of error
The denoise node fails to work when the render resolution is set to 1920*1920
Exact steps for others to reproduce the error
Based on the default startup, you can also check out the attached .blend file as well if you want.
Then you will see, after the render is done, the image becomes pure black.
Denoise Node Resolution Bug.blend
Added subscriber: @Eary
#78522 was marked as duplicate of this issue
Added subscriber: @Alaska
Changed status from 'Needs Triage' to: 'Needs User Info'
I'm unable to reproduce this issue in Blender 2.82a, 2.83
8956e9e5f6(2020-05-11 19:18), or 2.90542ff416e2(2020-05-11 21:02) with a new scene or the .blend file you've included.From the top of Blender can you select "Help>Save system info" and attach it to this report? There's also probably some debuging steps you can run, but I'm not well versed in the process, so I'll leave this up to the developers to discuss with you.
Here is the system info .txt file
system-info.txt
The issue may also be a result of a lack of RAM. Are you able to monitor your RAM usage in task manager while running the denoise node (Right click the task bar usually at the bottom of your screen and select "Task Manager" then select "More details" then select the "Performance" tab and select "Memory") and report back with what happens. Maybe even include a screenshot.
It's almost completely flat, I don't think that's the problem.
Changed status from 'Needs User Info' to: 'Needs Triage'
Yeah, it doesn't seem like the issue. It's definitely something that needs more debugging information that hopefully the developers can help you in collecting.
In the meantime, if you need a scene rendered and denoised, I'm willing to render and denoise it for you.
It's nothing important, I just randomly sculpted something and wanted to post it to my social media. :)
Okay. Anyway, I wish you luck in getting this sorted.
Removed subscriber: @Alaska
Added subscriber: @ankitm
#76015 (Black screen restart crash using compositor rendering for image generation)
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Needs User Info'
#76015 is Different kind of black screen :)
@Eary does this happen if you click on File > Defaults > Load Factory Settings?
Also can you try to hold right mous button and move cursor over rendered image and check if color in sampler panel is black as well?
It is the same after loading factory settings, and in the sampler panel the x and y change when I move the mouse but not z, and the RGB values stay 0.
Added subscriber: @brecht
Does this happen specifically with 1920*1920, or is it specifically with any resolution above a certain size? Or any square resolution?
I tested again on 1920*1080 ratio, and change only the percentage as it goes, the result is that it happens to any resolution above 104%
That seems to be a mistake ?
Do you mean the percentage exceeding 100%? I don't think that's a mistake, it is a convenient way of setting the resolution. For example, 200% of 1920 * 1080 means 2k, 400% means 4k etc. In this case, 104% roughly means 1996*1123. Anyway, it doesn't matter. The threshold is somewhat dynamic, sometimes 104% or even 105% works, but sometimes 103% won't work. But it is safe to assume that it is not only for squre, it's for any ratio. And it happens at higher resolution. Like 2K and 4K are sure to black out every time.
Update: 1920 * 1920 suddenly starts to work fine today, but 2k and 4k etc. are still blacking out.
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscriber: @JustRed
Still a thing -
Tested 2048x2048 on 25th june build (2.9), denoising on - no results (image fully black). Denoising off - works fine.
Resized image to 1024x2048 - denoising on - no results.
Resized to 1555x1231 - denoising on - no results.
Object is the default UV Sphere with default uvs. Material has transmission on 1 and an IOR of 2.460. Is lit using a 4k hdri.
Sunlight has no impact on the bake.
GTX 1060 - 16gb ram - i7 6700hq - Win10 - latest nvidia drivers as of june 27 2020.
Scene is completely empty except for 2 cubes, 1 uv sphere, 1 camera and a plane, consisting out of 525 faces in total.
Ram usage is fine at ~500mb, barely any load.
Using combined bake, but even individual bake types give no result.
Rendering through CUDA (GPU only), but with optix denoiser.
This only concerns bakes with Optix render denoising on.
Added subscriber: @zonaweb
I'm having this issue too. I Made a video to show it.
I was rendering with 1080 X 1280 and 200% in blender 2.83.1
Core i7 7700k (stock)
RX 570 (stock)
16Gb DDR4
Action 29-06-2020 17-12-28.mp4
Dimensions settings
Memory usage
vertices, faces, tris, objects and blender memory usage.
System-info.txt
system-info.txt
Added subscriber: @GodSpeed
I Have the same issue too :(
except i dont use optix, i use the default one.
CPU: AMD Radeon E2- 9000 series
GPU: Radeon R2 series
and i use windows 10.
My CPU has SSE4.1+
on searching over internet i saw the same error occurring to people using Linux or their CPU doesnt support SSE4.1+ , but i have all those and still cant fix this.
Blender Bug.mp4
Added subscribers: @RC12, @sharaths21312
And yeah Also I tried Changing the Resolution but it still ends up black
Removed subscriber: @RC12
UPDATE: There is a new switch in the latest 2.90 build in the render settings panel to toggle openimage denoise, I tested it and found out that the 2k render with that option toggled is denoising just fine (though generally slower), while the denoise node is still making it black. There is something unique to the node that is causing my problem.
Added subscriber: @PetterLundh
I figured out one thing, if I want to denoise it right after rendering the image, it is going to turn black. But I can save the image as a multilayer openexr file, and thn restart my computer, something interesting happens. After restarting, open Blender's compositor, check "use node" and drag the openexr in. Ctrl Shift on it, you can see it is totally black in the "composite" layer mode, but if you change layer mode to "view layer" you can see the original image. I can denoise just fine after restarting. But after some time the denoise node blacks out again.
What is interesting to me is that the blacked out image is recorded in the multilayer openexr file under "composite" layer mode. For those who cannot reproduce, don't know if you can get into the openexr file to see what happened during the composition, here is the file:
I am going over old reports. Can you still reproduce this issue in latest build form https://builder.blender.org/download/ ?
Sorry for late reply, yes it is still the case
Added subscriber: @ploobul
Still seems to be a problem, I've managed to replicate this exact same issue.
Added subscriber: @lichtwerk
Could this be related {#94127}?
Added subscriber: @Raimund58
@Eary Can you still reproduce it with Blender 3.0?
Yes I can still reproduce
Also just to be clear, the denoise option in render settings is doing fine, it's just the compositor denoise node that's still giving me black. I mainly use the render setting denoise nowadays since I have learned that there is no real difference between them in speed or quality.
Quite interesting. I can not reproduce it on my machine.
system-info.txt
With Blender 3.0 if your CPU was missing some needed flags, both denoising methods (node and render) should always return black. (afaik)
With Blender >=Blender 2.93 it just would be noisy but not black.
So, my guess is that this report is not related to #94127 (Cycles/Compositor: The denoiser returns a black image if not all requirements are fulfilled)
Added subscriber: @Sergey
I can not reproduce the issue on various machines here.
Does the issue persist when you disable tiling in the performance settings?
Yes it still happens without tiles. The thing is, it's not about Cycles, it's about the denoise node, this means I load a 2k EXR in and I would have the same problem. I think it might be the "CPU not fulfilling requirement" situation, because everytime I encounter that problem, I can just save a multilayer EXR and restart my computer, import the EXR and denoise with no problem. Therefore restarting the computer makes my CPU come back to life? And after using for a while the problem would come back and I would need to restart again.
Added subscriber: @3di
also happens intermittently at other resolutions. I think it's probably to do with system resources? Maybe it could be avoided by processing each node sequentially rather than parallel (I'm assuming it's parallel based on the issue).
For production renders the possibility of this happening randomly at some point amongst hundreds of thousands of frames, takes Blender off the table completely as a viable option.
It happened to me yesterday on a 1920 x 1080 render where the individual rays where being denoised separately. On one of the frames, the gloss channel was completely black. Couldn't get the issue to repeat when trying to render that frame again several times.
Could this be caused by Blender not correctly handling the denoiser returning multiple tiles when OIDN automatically goes into tiled denoising mode if the memory requirements exceed OIDN's maxMemoryMB default of 3000 MB as described here: https://www.openimagedenoise.org/documentation.html
Or alternatively, perhaps Blender has increased this parameter so that the full frame is always denoised, and this is resulting in insufficient memory during denoising?
The documentation mentions the split happens internally, so doesn't sound that this is something what requires an explicit handling from our side.
That being said, it could be a factor indeed. Is just very hard to troubleshoot since we were still unable to replicate the issue on our side.
Well if it's a case of the tiled denoising being the issue, that only occurs when the image being denoised requries more than 3000mb, then perhaps you could replicate by lowering the maxMemoryMB to something very low like 30mb (to gurantee the tiled denoising happens).
If it's not that, then possibly it's because of insufficient system resources during denoising, in which case try depleting ram prior to using the denoise node.
The only time it happened for me is when I've had many denoise nodes in the node tree a few years ago, but I don't think that can be the issue any longer as I believe it now executes them sequentially rather than in parallel.
Only bringing it up again because someone reported it to me yesterday.
My money would be on it being due to insufficient system resources, as that would explain why the reports became far less frequent after changing the denoise nodes to process sequentially. If this is also true, then that might suggest it could be avoided more often still by dynamically assigning the maxMemoryMB parameter based on available system ram, so that when there's less than the 3000mb default it should still operate if paging is disabled.