Cycles Cryptomatte wrong on objects with SSS #97169

New Issue

Rincewind · 2022-04-08T15:21:49+02:00

Rincewind commented

2022-04-08 15:21:49 +02:00

System Information
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: cc66d1020c
Worked: never it seems

Short description of error
When using Crytomatte with an object which uses subsurface scattering, the composed result is too bright

Exact steps for others to reproduce the error

Create an object with SSS
Compose the image

The dice is in the Crytomatte render too bright.

Video

blender_aYggpozVGZ.mp4

Blender File

Crytomatte Test.blend

Workaround

**System Information** Operating system: Windows-10-10.0.19042-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 **Blender Version** Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: `cc66d1020c` Worked: never it seems **Short description of error** When using Crytomatte with an object which uses subsurface scattering, the composed result is too bright **Exact steps for others to reproduce the error** 1. Create an object with SSS ![Crytomatte Screen 01.png](https://archive.blender.org/developer/F12983901/Crytomatte_Screen_01.png) 2. Compose the image ![Crytomatte Screen 02.png](https://archive.blender.org/developer/F12983905/Crytomatte_Screen_02.png) The dice is in the Crytomatte render too bright. **Video** [blender_aYggpozVGZ.mp4](https://archive.blender.org/developer/F12983911/blender_aYggpozVGZ.mp4) **Blender File** [Crytomatte Test.blend](https://archive.blender.org/developer/F12983964/Crytomatte_Test.blend) **Workaround** ![Crytomatte Screen 02 workaround.png](https://archive.blender.org/developer/F12983914/Crytomatte_Screen_02_workaround.png)

Rincewind commented

2022-04-08 15:21:49 +02:00

Added subscriber: @Rincewind3D-1

Rincewind commented

2022-04-08 15:33:22 +02:00

Update:

It may be just an UI bug in Blender. If I save images as a composed version and the original render, both seems to be the identical:

Composed with Cryptomatte

Orignal Image

Update: It may be just an UI bug in Blender. If I save images as a composed version and the original render, both seems to be the identical: Composed with Cryptomatte ![Crytomatte Compositioin Render.png](https://archive.blender.org/developer/F12983971/Crytomatte_Compositioin_Render.png) Orignal Image ![Crytomatte Original Render.png](https://archive.blender.org/developer/F12983973/Crytomatte_Original_Render.png)

Philipp Oeser commented

2022-04-08 16:05:57 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-04-08 16:05:57 +02:00

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

Philipp Oeser commented

2022-04-08 16:05:57 +02:00

Hm, can confirm.
Legacy Cryptomatte has the same problem, mattes are also off.
In Eevee, this seems OK though

Hm, can confirm. Legacy Cryptomatte has the same problem, mattes are also off. In Eevee, this seems OK though

Philipp Oeser changed title from ~~Crytomatte & SSS is broken~~ to Cycles Crytomatte wrong on objects with SSS

2022-04-08 16:07:14 +02:00

Philipp Oeser changed title from ~~Cycles Crytomatte wrong on objects with SSS~~ to Cycles Cryptomatte wrong on objects with SSS

2022-04-08 16:16:01 +02:00

Rincewind commented

2022-04-08 19:05:21 +02:00

Added subscriber: @Jeroen-Bakker

Rincewind commented

2022-04-08 19:05:21 +02:00

maybe @Jeroen-Bakker can help?

Lukas Stockner commented

2022-05-07 23:19:47 +02:00

Added subscriber: @LukasStockner

Lukas Stockner commented

2022-05-07 23:19:47 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Lukas Stockner closed this issue

2022-05-07 23:19:47 +02:00

Lukas Stockner self-assigned this 2022-05-07 23:19:47 +02:00

Lukas Stockner commented

2022-05-07 23:19:47 +02:00

Fixed by 1b566b70c1.

Fixed by 1b566b70c1.

Rincewind commented

2022-05-08 00:01:59 +02:00

Intresting. I can confirm that this bug is fixed in the current 3.2 Beta.

So, the hohle time Crypomatte gave back the correct image and the image without Crypomatte was bugged?

Intresting. I can confirm that this bug is fixed in the current 3.2 Beta. So, the hohle time Crypomatte gave back the correct image and the image without Crypomatte was bugged?

Lukas Stockner commented

2022-05-08 21:17:52 +02:00

No, the problem was that data passes were being written twice, and that included the Cryptomatte pass. If you look at the matte pass in a version without the fix, its values are over 1.

Rincewind commented

2022-05-09 01:20:55 +02:00

Just to clarify, how should it look like?

Before the bugfix my example file created a brighter box with cryptomatte and a darker box without cryptomatte (original render pass).

Since the bugfix, I get the bright box in the origina render pass and cryptomatte.

This means, what Cryptomatte returned before the bugfix is now the new default for the render pass.

I don't know what's here right and wrong. Just want to clarify it. ;)

Just to clarify, how should it look like? Before the bugfix my example file created a brighter box **with** cryptomatte and a darker box without cryptomatte (original render pass). Since the bugfix, I get the bright box in the origina render pass **and** cryptomatte. This means, what Cryptomatte returned **before** the bugfix is now the new default for the render pass. I don't know what's here right and wrong. Just want to clarify it. ;)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cycles Cryptomatte wrong on objects with SSS #97169