State:Closed|icon_bug|icon_nuke|database:public|Resolution:Fixed|TargetRelease:12.0v3|BugID:407751|
Problem summary:
An error is given when the OCIO environment variable is set and viewing the OCIOFileTransform node.
Customer reported version:
Nuke 12.0v1
Customer reported platform:
CentOS 7.4
Steps to reproduce:
1) From the command prompt/terminal, set the environment variable OCIO= C:/Program Files/Nuke12.0v1/plugins/OCIOConfigs/configs/aces_1.0.3/config.ocio
2) Launch Nuke from the command prompt.
3) Press Tab and type OCIOFileTransform then Enter to add the node.
4) View the node and any errors given.
Expected behavior:
The OCIOFileTransform node should be unable to error when the OCIO environment variable is set.
Actual behavior:
The error "BuildColorSpaceOps failed, null srcColorSpace" is given when the OCIO environment variable is set. This error has also been seen to occur when setting a custom OCIO via the Project Settings (S) Color menu.
Workaround:
Ensure the colorManagement knob in the script Project Settings is set to ‘OCIO’.
Reproduced by Support in:
Nuke 12.0v1 - Windows 10, CentOS 7, macOS 10.13 - regression
Unable to reproduce bug in:
Nuke 11.3v5 - Windows 10, CentOS 7, macOS 10.13
Earliest version tested
Nuke 11.3v5 - This issue doesn't appear in this version and has regressed
We're sorry to hear that
Please tell us why