Page MenuHome

The Denoise Node Turns the Rendered Image into Pure Black at the Resolution of 1920 *1920
Needs Developer to Reproduce, NormalPublic


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: rB542ff416e274
Worked: 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.

  1. Switch the render engine to Cycles
  2. Under Output Properties tab, set the resolution to 1920*1920, make sure the percentage is 100%
  3. Under View Layer Properties tab, check Denoising Data
  4. Go to the Compositor, add a denoise node, connect all three sockets accordingly
  5. Hit F12 to render

Then you will see, after the render is done, the image becomes pure black.

Event Timeline

Alaska (Alaska) changed the task status from Needs Triage to Needs Information from User.May 12 2020, 7:32 AM
Alaska (Alaska) added a subscriber: Alaska (Alaska).

I'm unable to reproduce this issue in Blender 2.82a, 2.83 8956e9e5f6c0 (2020-05-11 19:18), or 2.90 542ff416e274 (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

Alaska (Alaska) added a comment.EditedMay 12 2020, 7:37 AM

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.

Zijun Zhou (Eary) added a comment.EditedMay 12 2020, 7:56 AM

It's almost completely flat, I don't think that's the problem.

Alaska (Alaska) changed the task status from Needs Information from User to Needs Triage.EditedMay 12 2020, 8:01 AM

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.

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.EditedMay 12 2020, 10:44 AM

T76015 is Different kind of black screen :)

@Zijun Zhou (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.

Does this happen specifically with 1920*1920, or is it specifically with any resolution above a certain size? Or any square resolution?

Zijun Zhou (Eary) added a comment.EditedMay 12 2020, 4:10 PM

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%

.. to any resolution above 104%

That seems to be a mistake ?

Zijun Zhou (Eary) added a comment.EditedMay 12 2020, 7:41 PM

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.

Richard Antalik (ISS) changed the task status from Needs Information from User to Needs Developer to Reproduce.May 19 2020, 12:03 PM
Jaro (iarilo) added a subscriber: Jaro (iarilo).EditedJun 27 2020, 1:23 PM

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.

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

Dimensions settings

Memory usage

vertices, faces, tris, objects and blender memory usage.


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.

And yeah Also I tried Changing the Resolution but it still ends up black

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.