Problem summary
Nuke crashes when opening .nk scripts that have the OCIO Config set to "custom" but the OCIO config path is empty.
Customer reported version
Nuke 13.0v4
Customer reported platform
Windows 10
Steps to reproduce
1) Open Nuke.
2) Open the Project Settings (
Edit > Project Settings) and open the
Color tab.
3) From the
color management dropdown, select
OCIO.
4) From the
OCIO Config dropdown, select
custom.
5) Save the script.
6) Close the comp (
File > Close Comp)
7) Reopen the comp that was saved in step 4.
Expected behaviour
Nuke should not crash when opening any .nk script.
Actual behaviour
Nuke crashes when opening .nk scripts that have the OCIO Config set to "custom" but the OCIO config path is empty.
Workaround
In order to open the script, you can edit the .nk file in a script editor and remove the lines which contain the
colorManagement and
OCIO_conifg settings. In the example below, the lines in bold should be deleted:
Root { inputs 0 name C:/temp/113964/13.0v5.nk format "2048 1556 0 0 2048 1556 1 2K_Super_35(full-ap)" proxy_type scale proxy_format "1024 778 0 0 1024 778 1 1K_Super_35(full-ap)" colorManagement OCIO OCIO_config custom defaultViewerLUT "OCIO LUTs" workingSpaceLUT scene_linear monitorLut sRGB monitorOutLUT "rec709 (default)" int8Lut matte_paint int16Lut texture_paint logLut compositing_log floatLut scene_linear}
Reproduced by support
This bug has been reproduced in:
Nuke 13.0v5 - Windows 10 - macOS 10.15 (Catalina) - Linux CentOS 7
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10 - macOS 10.13 (High Sierra) -
Regression
Unable to reproduce bug in:
Nuke 9.0v9 - Windows 10 - macOS 10.13 (High Sierra)
Earliest version tested
Nuke 9.0v9
- This issue doesn't appear in this version and has regressed