Problem summary
Setting the default OpenColorIO config under Preferences>Project Defaults>Color Management will override existing projects.
Customer reported version
nuke.11.1v2
Customer reported platform
windows10
Steps to reproduce
1) Open Nuke
2) Create a simple Nuke script. Ensure in the Project Settings (Press S on the Node Graph > Color Tab) that Color Management is set to 'Nuke' and OCIO config is set to 'nuke-default'.
3) Create an OCIO_colorspace node, set to linear in linear out
4) Save the comp.
5) Close and then relaunch Nuke.
7) Open Preferences (Edit > Preferences).
8) Navigate to Project Defaults>Color Management and set the OpenColorIO config to 'aces 1.0.3' then click 'OK'.
9) Close and then relaunch Nuke.
10) Open the Nuke script that was saved in Step 4.
11) Notice that the OCIO Colorspace node will error due to 'Input color space index out of range'. The Project Settings are also incorrectly set to aces_1.03, overriding what was originally saved.
Reproduced by support
This bug has been reproduced in:
Nuke 11.2v2 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)
Nuke 11.1v5 - Windows 10
Nuke 11.1v1 - Windows 10
Nuke 10.5v7 - Windows 10
Nuke 10.5v1 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra) - Regression
Unable to reproduce bug in:
Nuke 10.0v6 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)
Earliest version tested
Nuke 10.0v6 - This issue no longer appears in this version and has regressed
Expected behaviour
Changing the default OpenColorIO config setting should not affect the state of existing projects.
Actual behaviour
Changing the default OpenColorIO config setting does affect the state of existing projects and may cause errors in existing scripts.