[2.93-A] Composite Node Output completely black, Viewer Node working from the same data. #86836

New Issue

Rafael · 2021-03-22T21:29:07+01:00

Rafael commented

2021-03-22 21:29:07 +01:00

System Information
Operating system: Windows 10
Graphics card: GTX 1050 TI Overclocked (Second Hand GPU)

Blender Version
Broken: 2.93 Alpha (Date: 2021-03-19 21:37, Branch: master)
Worked: 2.93 Alpha, Local Compilation from Source Code (Date: 2021-03-18, Commit: 51c7ff9222) <-- Tested on Friend's Computer

Description :
While working on a 3D model i wanted to Render a 8k shot, after a complete rendering Compositing started. Once done it gave me a "Black Silhouette" of what i rendered.

On this image you can see the Black Silhouette, the issue only happens on composite node's ouput, viewer node ouput works perfectly.

This image illustrate my current Compositing Setup

Exact steps for others to reproduce the error :
Setup a scene - in my case it's few objects, textures, compositing nodes with two output (one normal, one watermarked) - render 8k and wait for Compositing.

Due to Not-To-Share Models i'm not allowed to share my Blend File.

**System Information** Operating system: Windows 10 Graphics card: GTX 1050 TI Overclocked (Second Hand GPU) **Blender Version** Broken: 2.93 Alpha (Date: 2021-03-19 21:37, Branch: master) Worked: 2.93 Alpha, Local Compilation from Source Code (Date: 2021-03-18, Commit: 51c7ff9222c362e03d07aba0ebbffd9d52fc9d3b) <-- Tested on Friend's Computer **Description :** While working on a 3D model i wanted to Render a 8k shot, after a complete rendering Compositing started. Once done it gave me a "Black Silhouette" of what i rendered. On this image you can see the Black Silhouette, the issue only happens on composite node's ouput, viewer node ouput works perfectly. ![image.png](https://archive.blender.org/developer/F9904547/image.png) This image illustrate my current Compositing Setup ![image.png](https://archive.blender.org/developer/F9904556/image.png) **Exact steps for others to reproduce the error :** Setup a scene - in my case it's few objects, textures, compositing nodes with two output (one normal, one watermarked) - render 8k and wait for Compositing. Due to Not-To-Share Models i'm not allowed to share my Blend File.

Rafael commented

2021-03-22 21:29:07 +01:00

Added subscriber: @Aels-224

Rafael commented

2021-03-22 22:11:44 +01:00

Additional Information.

Turned OptiX Denoising off and didn't got a Black Silhouette on Composite Node output.

I am currently checking to see if it has been reactivated to determine if it was a one-time problem.

Additional Information. Turned OptiX Denoising off and didn't got a Black Silhouette on Composite Node output. I am currently checking to see if it has been reactivated to determine if it was a one-time problem.

Rafael commented

2021-03-22 22:39:50 +01:00

I am currently checking to see if it has been reactivated to determine if it was a one-time problem.

It seems that everything is back to normal when re-enabling OptiX denoising and re-rendering, which seems to be a one-time problem.

> I am currently checking to see if it has been reactivated to determine if it was a one-time problem. It seems that everything is back to normal when re-enabling OptiX denoising and re-rendering, which seems to be a one-time problem.

Philipp Oeser commented

2021-03-23 09:52:56 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-03-23 09:52:56 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2021-03-23 09:52:56 +01:00

If this one-time problem is reproducable, then it would still be good to have a look at this.
However, we would still need a .blend file with this particular setup (models can be replaced with simple geometry), this just ensure we are all on the same page.

If this one-time problem is reproducable, then it would still be good to have a look at this. However, we would still need a .blend file with this particular setup (models can be replaced with simple geometry), this just ensure we are all on the same page.

Rafael commented

2021-03-23 11:05:04 +01:00

Greetings @lichtwerk , I haven't managed to reproduce this particular issue but I think I found a possible cause, I'm no expert so pardon me if I'm off.

While trying to reproduce it, I got this result when doing the previously mentioned steps.
Also, during the night — between my report and now — a friend tried to reproduce my issue and got almost what I just got, visually not identical tho it comes from the same compositing setup.

His theory and now mine is that multiple Composite and Viewer node — even if disable — might interact in a wrong way on to what is outputted.

Here's a clip of his side, note that he is on 2.92 (version on which the "Black Silhouette" issue also happened to me in the past).
https://cdn.discordapp.com/attachments/555448292087955456/823768556474073178/qrU850mZZo.mp4

Here's my mentionned result.

On my picture both Render Result and Viewer Node images should be identical, that said it seems that Composite and Viewer node seem to keep some kind of active status when duplicated, even if not "active" by clicking on them.
I say should since technically both Composite and Viewer node should output the non-watermark picture since the active ones are both linked to the Glare node.

Here's the Blend file, it's the one i used for the picture above
untitled.blend

In hope that it helps, don't hesitate to ask more and please pardon any delay or typos.

Greetings @lichtwerk , I haven't managed to reproduce this particular issue but I think I found a possible cause, I'm no expert so pardon me if I'm off. While trying to reproduce it, I got this result when doing the previously mentioned steps. Also, during the night — between my report and now — a friend tried to reproduce my issue and got almost what I just got, visually not identical tho it comes from the same compositing setup. His theory and now mine is that multiple Composite and Viewer node — even if disable — might interact in a wrong way on to what is outputted. Here's a clip of his side, note that he is on 2.92 (version on which the "Black Silhouette" issue also happened to me in the past). https://cdn.discordapp.com/attachments/555448292087955456/823768556474073178/qrU850mZZo.mp4 Here's my mentionned result. ![image.png](https://archive.blender.org/developer/F9905327/image.png) On my picture both Render Result and Viewer Node images should be identical, that said it seems that Composite and Viewer node seem to keep some kind of active status when duplicated, even if not "active" by clicking on them. I say should since technically both Composite and Viewer node should output the non-watermark picture since the active ones are both linked to the Glare node. Here's the Blend file, it's the one i used for the picture above [untitled.blend](https://archive.blender.org/developer/F9905331/untitled.blend) In hope that it helps, don't hesitate to ask more and please pardon any delay or typos.

Ankit Meel commented

2021-04-04 18:08:17 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Evan Wilson commented

2021-04-04 23:32:37 +02:00

Added subscriber: @EAW

Evan Wilson commented

2021-04-04 23:32:37 +02:00

I have been able to reproduce the issue of the non-active render node being the one that appears in the Image Editor, but only the first time after I copied it. After that, it worked as expected. I don't feel that I have the right steps that are reproducible yet to be able to confirm.

Omar Emara commented

2022-02-11 12:09:09 +01:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-02-11 12:09:09 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Omar Emara commented

2022-02-11 12:09:10 +01:00

The composite node ignores its active status and overrides the previous active node, while the order is not defined.
In convert_to_operation, it should be:

lang=diff
-  bool is_active = (editor_node->flag & NODE_DO_OUTPUT_RECALC) || context.is_rendering();
+  bool is_active = ((editor_node->flag & NODE_DO_OUTPUT_RECALC) || context.is_rendering()) &&
+                   (editor_node->flag & NODE_DO_OUTPUT);

The composite node ignores its active status and overrides the previous active node, while the order is not defined. In `convert_to_operation`, it should be: ``` lang=diff - bool is_active = (editor_node->flag & NODE_DO_OUTPUT_RECALC) || context.is_rendering(); + bool is_active = ((editor_node->flag & NODE_DO_OUTPUT_RECALC) || context.is_rendering()) && + (editor_node->flag & NODE_DO_OUTPUT); ```

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

[2.93-A] Composite Node Output completely black, Viewer Node working from the same data. #86836