You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
The code here is to validate the extensions/file formats of the AOVs are consistent with the global render file format set.
The Redshift Cryptomatte AOV uses a custom Cryptomatte (EXR) file format and thus will always differ from e.g. the global OpenEXR file format.
The "repair" method does allow the user to repair and pass the validator. However, Redshift will still enforce the Cryptomatte (EXR) and after repair will actually spew out Maya errors whenever you select the Cryptomatte AOV with the Attribute Editor visible - this is due to that particular AOV not havingt he OpenEXR file format entry available.
To Reproduce
Steps to reproduce the behavior:
Create a render scene with Redshift
Add Cryptomatte AOV
Check the errors, perform a repair
See the issue described above.
Expected behavior
Should just allow the Cryptomatte (EXR) file format to be set for cryptomatte AOVs.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Windows
Host: Maya 2022 py3 Redshift 3.5.03
[cuID:2hz0tnq]
The text was updated successfully, but these errors were encountered:
Describe the bug
The code here is to validate the extensions/file formats of the AOVs are consistent with the global render file format set.
The Redshift Cryptomatte AOV uses a custom
Cryptomatte (EXR)
file format and thus will always differ from e.g. the globalOpenEXR
file format.The "repair" method does allow the user to repair and pass the validator. However, Redshift will still enforce the Cryptomatte (EXR) and after repair will actually spew out Maya errors whenever you select the Cryptomatte AOV with the Attribute Editor visible - this is due to that particular AOV not havingt he
OpenEXR
file format entry available.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should just allow the Cryptomatte (EXR) file format to be set for cryptomatte AOVs.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
[cuID:2hz0tnq]
The text was updated successfully, but these errors were encountered: