blender/blender
150
479
Fork 710
Code Issues 6.8k Pull Requests 895 Projects 18 Wiki Activity

Blank GPU compositor result with Legacy Cryptomatte node unless compositor is updated #126604

New Issue
Open
opened 2024-08-21 15:50:43 +02:00 by Narek-Suqiasyan · 5 comments
Narek-Suqiasyan commented 2024-08-21 15:50:43 +02:00
Copy Link

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 560.81

Blender Version
Broken: version: 4.2.1 LTS, branch: blender-v4.2-release, commit date: 2024-08-19 11:21, hash: 396f546c9d82
Worked: 4.1.1 because it didn't have the GPU compositor

Short description of error
The legacy Cryptomatte node will produce blank outputs directly after rendering when using the GPU compositor. Updating the compositor node tree updates it.

Exact steps for others to reproduce the error

  • Create a scene with the Cryptomatte passes enabled (I just changed the render engine to Cycles and enabled the Material Cryptomatte pass. The Object pass doesn't seem effected.)
  • Activate the GPU compositor in Render Properties -> Performance -> Compositor -> Device (This issue only seems to impact the GPU compositor)
  • Use the Cryptomatte node in the compostior:
    • Render the image.
    • Open a compositor node editor and add a Legacy Cryptomatte node to the compositor, connecting the relevant passes to the node.
    • Activate the Pick output of the node and pick a material to be used.
    • Switch back to the Image or Matte output
  • Render the image again.
  • Notice that the output is black/blank.
  • Reconnect the output of the Cryptomatte node to the output to make it work.

Interestingly the Legacy Cryptomatte node doesn't produce a output if the GPU compositor is used in full precision mode.

Here is a file with most of the steps done for you. Legacy Cryptomatte GPU compositor issue.blend

Original report

Short description of error
I have composition nodes with cryptomattes, after rendering I need to unplug and plug the Composite node for having my render. Now I can't render animation. But if I plug the Composite node to Render layer without another nodes, render working.

Exact steps for others to reproduce the error
File in description

**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 560.81 **Blender Version** Broken: version: 4.2.1 LTS, branch: blender-v4.2-release, commit date: 2024-08-19 11:21, hash: `396f546c9d82` Worked: 4.1.1 because it didn't have the GPU compositor **Short description of error** The legacy Cryptomatte node will produce blank outputs directly after rendering when using the GPU compositor. Updating the compositor node tree updates it. **Exact steps for others to reproduce the error** - Create a scene with the Cryptomatte passes enabled (I just changed the render engine to Cycles and enabled the Material Cryptomatte pass. The Object pass doesn't seem effected.) - Activate the GPU compositor in `Render Properties -> Performance -> Compositor -> Device` (This issue only seems to impact the GPU compositor) - Use the Cryptomatte node in the compostior: - Render the image. - Open a compositor node editor and add a Legacy Cryptomatte node to the compositor, connecting the relevant passes to the node. - Activate the `Pick` output of the node and pick a material to be used. - Switch back to the `Image` or `Matte` output - Render the image again. - Notice that the output is black/blank. - Reconnect the output of the Cryptomatte node to the output to make it work. Interestingly the Legacy Cryptomatte node doesn't produce a output if the GPU compositor is used in full precision mode. Here is a file with most of the steps done for you. [Legacy Cryptomatte GPU compositor issue.blend](/attachments/6640347a-ae0a-4f6a-802e-69c128f12742) <details> <summary>Original report</summary> **Short description of error** I have composition nodes with cryptomattes, after rendering I need to unplug and plug the Composite node for having my render. Now I can't render animation. But if I plug the Composite node to Render layer without another nodes, render working. **Exact steps for others to reproduce the error** File in description </details>
Narek-Suqiasyan added the
Severity
Normal
Type
Bug
Status
Needs Triage
 labels 2024-08-21 15:50:44 +02:00
Narek-Suqiasyan commented 2024-08-21 15:53:09 +02:00
Author
Copy Link
No description provided.
Recording 2024-08-21 175237.mp4
4.9 MiB
Narek-Suqiasyan commented 2024-08-21 16:09:40 +02:00
Author
Copy Link

Error fixed, just I swap cryptomatte (legecy) to cryptomatte node

Error fixed, just I swap cryptomatte (legecy) to cryptomatte node
Alaska commented 2024-08-22 05:20:04 +02:00
Member
Copy Link

The Cryptomatte Legacy addon should not have that issue.

I tried recreating your node setup, but a lot of detail is missing so I'm not sure how to recreate it.

Can you share a file that has the issue with us?

The Cryptomatte Legacy addon should not have that issue. I tried recreating your node setup, but a lot of detail is missing so I'm not sure how to recreate it. Can you share a file that has the issue with us?
Alaska added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2024-08-22 05:20:13 +02:00
Alaska changed title from Black render in cycles to Black compositor result with Legacy Cryptomatte node unless compositor is updated 2024-08-22 05:20:53 +02:00
Alaska added the
Interest
Compositing
 label 2024-08-22 05:21:04 +02:00
Alaska commented 2024-08-22 05:34:50 +02:00
Member
Copy Link

I fiddled around and can reproduce the issue now.

Steps to reproduce:

  • Create a scene with the Cryptomatte passes enabled (I just changed the render engine to Cycles and enabled the Material Cryptomatte pass. The Object pass doesn't seem affected.)
  • Activate the GPU compositor in Render Properties -> Performance -> Compositor -> Device (This issue only seems to impact the GPU compositor)
  • Use the Cryptomatte node in the compostior:
    • Render the image.
    • Open a compositor node editor and add a Legacy Cryptomatte node to the compositor, connecting the relevant passes to the node.
    • Activate the Pick output of the node and pick a material to be used.
    • Switch back to the Image or Matte output
  • Render the image again.
  • Notice that the output is black/blank.
  • Reconnect the output of the Cryptomatte node to the output to make it work.

Interestingly the Legacy Cryptomatte node doesn't produce a output if the GPU compositor is used in full precision mode.

Here is a file with most of the steps done for you. Legacy Cryptomatte GPU compositor issue.blend

I fiddled around and can reproduce the issue now. Steps to reproduce: - Create a scene with the Cryptomatte passes enabled (I just changed the render engine to Cycles and enabled the Material Cryptomatte pass. The Object pass doesn't seem affected.) - Activate the GPU compositor in `Render Properties -> Performance -> Compositor -> Device` (This issue only seems to impact the GPU compositor) - Use the Cryptomatte node in the compostior: - Render the image. - Open a compositor node editor and add a Legacy Cryptomatte node to the compositor, connecting the relevant passes to the node. - Activate the `Pick` output of the node and pick a material to be used. - Switch back to the `Image` or `Matte` output - Render the image again. - Notice that the output is black/blank. - Reconnect the output of the Cryptomatte node to the output to make it work. Interestingly the Legacy Cryptomatte node doesn't produce a output if the GPU compositor is used in full precision mode. Here is a file with most of the steps done for you. [Legacy Cryptomatte GPU compositor issue.blend](/attachments/6640347a-ae0a-4f6a-802e-69c128f12742)
Legacy Cryptomatte GPU compositor issue.blend
944 KiB
Alaska added
Module
VFX & Video
Status
Confirmed
 and removed
Status
Needs Information from User
 labels 2024-08-22 05:35:04 +02:00
Alaska changed title from Black compositor result with Legacy Cryptomatte node unless compositor is updated to Blank GPU compositor result with Legacy Cryptomatte node unless compositor is updated 2024-08-22 05:37:46 +02:00
Blender Bot added
Status
Archived
 and removed
Status
Confirmed
 labels 2024-09-06 19:31:06 +02:00
Alaska commented 2024-09-07 05:30:51 +02:00
Member
Copy Link

The issue is still present in latest main. I am re-opening this issue so we can keep track of it.

The issue is still present in latest main. I am re-opening this issue so we can keep track of it.
Alaska reopened this issue 2024-09-07 05:30:55 +02:00
Blender Bot added
Status
Needs Triage
 and removed
Status
Archived
 labels 2024-09-07 05:30:58 +02:00
Alaska added
Status
Confirmed
 and removed
Status
Needs Triage
 labels 2024-09-07 05:31:03 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset System
Asset datablocks, libraries, browser and shelf

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Collada

  
Interest
Compatibility
Backward and forward compatibility

  
Interest
Compositing

  
Interest
Core

  
Interest
Cycles

  
Interest
Dependency Graph

  
Interest
Development Management

  
Interest
EEVEE

  
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
Viewport & EEVEE

  
Interest
Virtual Reality

  
Interest
Vulkan

  
Interest
Wayland
Wayland windowing on Unix

  
Interest
Workbench

  
Interest: X11

Xorg/X11 windowing

  
Legacy
Asset Browser Project

Archived

  
Legacy
Blender 2.8 Project

Archived

  
Legacy
Milestone 1: Basic, Local Asset Browser

Archived

  
Legacy
OpenGL Error

Archived

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Related to security, https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
Module
Animation & Rigging

  
Module
Core

  
Module
Development Management

  
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

  
Module
Viewport & EEVEE

  
Platform
FreeBSD

  
Platform
Linux

  
Platform
macOS

  
Platform
Windows

  
Severity
High

  
Severity
Low

  
Severity
Normal

  
Severity
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

Archived

  
Type
Report

Archived

  
Type
To Do

No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 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#126604
No description provided.
Delete Branch "%!s()"

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?