Regression: Cryptomatte doesn't show all objects available #101601
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#101601
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.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15
Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash:
0759f671ce
Also tried 3.2.0 stable and 3.3.1 Release Candidate
Worked: 2.93.10 LTS (both legacy cryptomatte and new cryptomatte),
Short description of error
Cryptomatte is missing objects.
Expected (2.93.10 LTS):
Current (3.3.0):
It seems even worse with the Material output:
Note that this test scene is just the default cube duplicated around and materials duplicated too.
Exact steps for others to reproduce the error
cryptomatte_test.blend
With the test scene: hit the render button, and play with the different cryptomatte options, or use the legacy node. None of them show all four objects correctly on broken versions.
The issue seems identical with using a multilayer EXR rendered and saved from a working version like 2.93.10 LTS. So I guess the issue isn't the render nor data provided but either the cryptomatte itself or the data "reading" ?
Caused by
9dbea1db66
Added subscriber: @L0Lock
Added subscribers: @brecht, @Alaska
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
For reference, the Cryptomatte does have all objects, it's just that one of the objects has an alpha of 0, making it invisible.
If you use this compositor setup, you will see the object again.
However, having cryptomatte objects that are invisible is annoying to work with. @brecht, do you think this is worth investigating? Or should it be left "as is" since the information is technically still there.
I didn't set this up in the shader and I didn't touch the object's display properties either, it's literally the default cube and default material duplicated three times. And all the cubes are present in the final render, and the alpha channel itself is fully white.
I'm not an expert in the subject, but that doesn't sound like a normal behavior to me.
Changed status from 'Needs Developer To Reproduce' to: 'Needs Triage'
I don't think the Pick output should have zero alpha where there are objects, it should work for picking objects without additional nodes.
Someone will need to bisect to find the cause of this change.
I just thought I would document some quick findings from testing.
Somewhere between version 2.91 and 2.92, Cyrptomatte was expanded to make use of the alpha channel. Ever since that change, the cryptomatte output for this .blend file has been consistent for all newer versions of Blender.
So, the cube on the right when using Cryptomatte object has had an alpha of 0 ever since Blender 2.92.
The reason it looks different in Blender 3.2 and above is due to this bug: #98575 (Issues with HDRIs and render result pixel values that exceed half float limits)
Because the cube has an extremely high brightness (which turns black due to this bug), and thus turns invisible due to how Blender displays coloured 0 alpha pixels.
Upon further investigation, the culprit commit is
9dbea1db66
. I've provided a "simple" fix here: D16165But we're still going to run into issues where some objects are invisible due to the issue reported in #98575 turning the culprit objects black.
Added subscriber: @Jeroen-Bakker
CC @jbakker.
Cryptomatte doesn't show all objects availableto Regression: Cryptomatte doesn't show all objects availableChanged status from 'Needs Triage' to: 'Confirmed'
This issue was referenced by
0048820df8
Changed status from 'Confirmed' to: 'Resolved'
Changed status from 'Resolved' to: 'Confirmed'
Seems not to be working as expected.
Added subscriber: @EAW
@brecht To clarify, the pick is working fine. The name of the object appears when hovering over it, even when invisible, and is entered into the node when you click with picker.
@Alaska All the blocks have zero alpha: if that was the issue then none of the blocks would appear. The compositor is coded with the assumption that all images have associated alpha.
This is a color management issue. Setting the view transform to "Standard" or Raw" produces results identical to versions 3.0 or earlier.
@Jeroen-Bakker I think it is the fact that you set the OCIO View Transform GPU code generator to set 1e32 equal to infinity. The hash of the "invisible" block is around 1e35.
Yes, came to the same conclusion that OCIO view transform is rendering it black. Clamping shows Cube.003, but that would might break cryptomatte in some cases.
We could clamp it within the f16 range, so CM would not break.
@Jeroen-Bakker you might try removing the 1e32 = inf line of code. I am afk so I cannot verify, but I recall that commit having a comment referring to the “current” version of the OCIO library that hadn’t actually been merged at that point, and wondering if you had built the new version of the library on your own, or were possibly mistaken in what version you were using. The bug report in the OCIO tracker was closed with the claim that the fix for Mac GPU code generation was already in that version of the Library. So perhaps that line of code is no longer needed.
This fixes the issue, in the end.
Better option would be to fix this when uploading the data to the GPU, but that might require a copy. Will check tomorrow if we could fix this in the image engine.
This issue was referenced by
0386737097
This issue was referenced by
872a45f42b
Changed status from 'Confirmed' to: 'Resolved'