**System Information**
Operating system: macOS-12.3-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13
**Blender Version**
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-03-12 10:29, hash: `rBf6b73966101d`
Worked: (newest version of Blender that worked as expected)
**Short description of error**
I tested the newest OCIO v2 config from Github (https://github.com/AcademySoftwareFoundation/OpenColorIO-Config-ACES/releases/tag/v0.2.0)
in Blender 3.2 Alpha. It was first time I tried that.
I had to change the OCIO 2.1 version to 2.0 to make it actually work in Blender. I was assured that this shouldn't be a problem.
I rendered a test scene and saw some strange shading errors with the default sRGB view transform.
Selecting a different view transform like Rec.709 fixes the issue.
I posted about the issue on my blog https://www.toodee.de/?page_id=5517 and on ACESCentral.com
https://community.acescentral.com/t/opencolorio-2-configs-for-aces/4354
The rendered EXR file is fine of course. The problem only occurs in the render view or when I try to export the rendered image.
JPG works fine, PNG breaks in a different way and creates a strangely bright image.
{F12932848}
The shader uses the cyan patch of the X-Rite Colorchecker. Its the only patch which color values in ACEScg are outside the linear_sRGB gamut.
{F12932852}
{F12932853}