Cycles: Compositor File Output BW Color Option Issue (again) #101782

Closed
opened 2022-10-12 22:42:58 +02:00 by MC · 9 comments

Because somehow, in the previous issue I opened, my comment didn't post at all when I had updated the google drive link.

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59

Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce
Working: Unknown

Short description of error
Discovered an issue where a compositor's File Output node is set to BW, it fails to output any emission.

Exact steps for others to reproduce the error
Download this file: https://drive.google.com/file/d/19vkFo1q_K0a_ppQKzBc3_fsRyJAq5Lq_/view?usp=sharing
Load up the following file and render out a single image. Renders out a pure black image.
The result is the same if you use the Emit pass.

Strangely, it works if you put in an RGB to BW node in between, which makes me think the file output is drawing exclusively from the R channel.

Extra Notes
This has several other issues included with it. If preferred, I can make multiple reports to them and link them back here.

The issues in particular:

When rendering out with this file, there will be a brief switch of view layers in the render output to "All" and "Turret Barrel", despite having Render Single Layer turned on.

This seems fixed in 3.6 onwards:
The outliner on the right and below does not show updated view layers that are supposed to be off, despite the animation data being active. Only when you click on some of them (not on the EYE icon, just their names!) will they update appropriately, instead of constantly reflecting the animation data (Animation workspace -> LayerToggles NLA).

Because somehow, in the previous issue I opened, my comment didn't post at all when I had updated the google drive link. **System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59 **Blender Version** Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce Working: Unknown **Short description of error** Discovered an issue where a compositor's File Output node is set to BW, it fails to output any emission. **Exact steps for others to reproduce the error** Download this file: https://drive.google.com/file/d/19vkFo1q_K0a_ppQKzBc3_fsRyJAq5Lq_/view?usp=sharing Load up the following file and render out a single image. Renders out a pure black image. The result is the same if you use the Emit pass. Strangely, it works if you put in an RGB to BW node in between, which makes me think the file output is drawing exclusively from the R channel. **Extra Notes** This has several other issues included with it. If preferred, I can make multiple reports to them and link them back here. The issues in particular: When rendering out with this file, there will be a brief switch of view layers in the render output to "All" and "Turret Barrel", despite having Render Single Layer turned on. This seems fixed in 3.6 onwards: `The outliner on the right and below does not show updated view layers that are supposed to be off, despite the animation data being active. Only when you click on some of them (not on the EYE icon, just their names!) will they update appropriately, instead of constantly reflecting the animation data (Animation workspace -> LayerToggles NLA).`
Author

Added subscriber: @MajorCooke

Added subscriber: @MajorCooke
Author

This time the materials are included to replicate the problem.

This time the materials are included to replicate the problem.
da.buy commented 2022-10-13 01:03:14 +02:00 (Migrated from localhost:3001)

Added subscriber: @da.buy

Added subscriber: @da.buy
da.buy commented 2022-10-13 01:03:14 +02:00 (Migrated from localhost:3001)

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

Changed status from 'Needs Triage' to: 'Confirmed'
da.buy commented 2022-10-13 01:03:14 +02:00 (Migrated from localhost:3001)

Can confirm, the compositor file output node will only use the red channel for bw render if forced to implicitly convert rgb input.
Here an easier test setup:

comp_file_output_implicit_bw_conversion_bug.blend

Can confirm, the compositor file output node will only use the red channel for bw render if forced to implicitly convert rgb input. Here an easier test setup: [comp_file_output_implicit_bw_conversion_bug.blend](https://archive.blender.org/developer/F13669846/comp_file_output_implicit_bw_conversion_bug.blend)
Author

There's a few other additional bugs I noticed which I've included under the "Extra Notes" that may be worth looking into.

There's a few other additional bugs I noticed which I've included under the "Extra Notes" that may be worth looking into.
Philipp Oeser removed the
Interest
VFX & Video
label 2023-02-10 09:31:29 +01:00
Sergey Sharybin added
Type
Bug
and removed
Type
Report
labels 2023-02-15 12:43:38 +01:00
Member

The outliner on the right and below does not show updated view layers that are supposed to be off, despite the animation data being active. Only when you click on some of them (not on the EYE icon, just their names!) will they update appropriately, instead of constantly reflecting the animation data (Animation workspace -> LayerToggles NLA).

This seems fixed in 3.6 onwards

>The outliner on the right and below does not show updated view layers that are supposed to be off, despite the animation data being active. Only when you click on some of them (not on the EYE icon, just their names!) will they update appropriately, instead of constantly reflecting the animation data (Animation workspace -> LayerToggles NLA). This seems fixed in 3.6 onwards
Member

Can confirm, the compositor file output node will only use the red channel for bw render if forced to implicitly convert rgb input.
Here an easier test setup:

comp_file_output_implicit_bw_conversion_bug.blend

This was also fixed in 3.6 (presumably by 1771ded381)

@MajorCooke : can you confirm?

If so, I think this report should be closed (if there are remaining issues, it might be better to report these separately).

> Can confirm, the compositor file output node will only use the red channel for bw render if forced to implicitly convert rgb input. > Here an easier test setup: > > [comp_file_output_implicit_bw_conversion_bug.blend](https://archive.blender.org/developer/F13669846/comp_file_output_implicit_bw_conversion_bug.blend) This was also fixed in 3.6 (presumably by 1771ded381125409a578ca57093f79219fe5cf79) @MajorCooke : can you confirm? If so, I think this report should be closed (if there are remaining issues, it might be better to report these separately).
Philipp Oeser added
Status
Needs Information from User
and removed
Status
Confirmed
labels 2023-07-19 11:42:50 +02:00
Member

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-08-15 11:32:16 +02:00
Sign in to join this conversation.
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
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#101782
No description provided.