ID 515401 - Setting defaultViewingLUT to OCIO LUTs no longer loads the OCIO luts into the Viewer Process

Follow

Problem summary
Setting defaultViewingLUT to OCIO LUTs no longer loads the OCIO luts into the Viewer Process
 
Customer reported version
nuke.13.0v2
 
Customer reported platform
rhel7
 
Steps to reproduce
 
1) Open / create an init.py in your .nuke directory
 
2) Add the following lines the the Python file and save it:
 
nuke.knobDefault('Root.defaultViewerLUT', 'OCIO LUTs')nuke.knobDefault("defaultViewerLUT", "OCIO LUTs")
 
3) Launch Nuke and check the Viewer Processes, it should list the names of the OCIOs configs, like sRGB (default), not the Nuke color managed colorspaces, like sRGB.
 
Expected behaviour
For the OCIO config color spaces to be listed in the viewer process:

 
Actual behaviour
The original Viewer processes are listed:
 
 
Workaround
You could create a knob changed callback to set register the same processes, for example:
def replaceViewerProcessLUTs():    import nuke, ocionuke       ### Remove existing Viewer Processes    for name in nuke.ViewerProcess.registeredNames():        nuke.ViewerProcess.unregister(name)    ### Add the OCIO Display viewer processes for the loaded config        ocioConfig = ocionuke.config.getOCIOConfig()        DISPLAY_UI_FORMAT = "%(view)s (%(display)s)"        for display in ocioConfig.getDisplays():        for view in ocioConfig.getViews(display):            name = DISPLAY_UI_FORMAT % {'view': view, "display": display}            nuke.ViewerProcess.register(name, nuke.createNode, ( "OCIODisplay", 'view "' + view + '"'))def callReplaceAction():    from PySide2.QtCore import QTimer    QTimer.singleShot(0, replaceViewerProcessLUTs)nuke.addKnobChanged(callReplaceAction, nodeClass='Root')
 
Reproduced by support
This bug has been reproduced in:
Nuke 13.2v3 - Windows 10, CentOS 7, macOS Monterrey 
Nuke 13.0v2 - Windows 10, CentOS 7, macOS Monterrey - regression
Nuke 12.2v11 - Windows 10
Nuke 12.2v6 - Windows 10 - regression
 
Unable to reproduce bug in:
Nuke 13.0v1 - Windows 10, CentOS 7, macOS Monterrey 
Nuke 12.2v5 - Windows 10
 
Earliest version tested
Nuke 13.0v1 - This issue doesn't appear in this version and has regressed

    We're sorry to hear that

    Please tell us why