Problem summary
When creating a new project within a Nuke Studio session, the new project will not inherit the OCIO colorspace correctly if it is from a custom directory and config file.
This only occurs in Nuke Studio/Hiero releases after 11.2v2 releases and over all three major operating systems.
This also only occurs with custom OCIO's and not when selecting a preset colorspace.
Customer reported version
nuke.11.3v1
Customer reported platform
windows10
Steps to reproduce
1) Open a new Nuke Studio session (11.2v3 or later)
2) Open 'Edit/Preferences' menu
3) Locate the OCIO settings in the 'Project Defaults/Color Management' tab
4) Select 'custom' in the OpenColorIO config area
5) Select a custom OCIO config using the 'Choose...' button. This will change your default transforms to the allocated OCIO config file.
6) Click 'Ok' to close and apply the OCIO
7) Create a new project using 'File/New Project'
8) Open the Project settings for this new project in the 'Project/Edit Settings' menu
9) Locate the 'Color Management' tab and view the OpenColorIO Config. Result: This should be referencing your custom OCIO directory and config file, not the nuke-default setting.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Nuke Studio 11.3v1 - Windows 10 - Centos 7 - MacOS 10.13.6
Nuke Studio 11.2v5 - Windows 10
Nuke Studio 11.2v3 - Windows 10 - Centos 7 - MacOS 10.13.6
Unable to reproduce bug in:
Nuke Studio 11.2v2 - Windows 10 - Centos 7 - MacOS 10.13.6
Earliest version tested
Nuke Studio 11.2v2
- This issue no longer appears in this version and has regressed
Expected behaviour
When creating a new project within a Nuke Studio session, the new project should inherit the custom OCIO directory and config file
Actual behaviour
When creating a new project within a Nuke Studio session, the new project does not inherit the custom OCIO directory and config file and references the nuke-default setting.