ID 238523 - Default viewerProcess set in init.py overridden by custom config.ocio saved in ˜/.nuke/uistate.ini

Follow

Problem summary
 
Default viewerProcess set in init.py overridden by custom config.ocio saved in ˜/.nuke/uistate.ini  
Affects switching between Hiero/HieroPlayer and Nuke when the former uses the init.py default and the latter has loaded a custom config.ocio.  You have to delete the ˜/.nuke/uistate.ini  created by Hiero/HieroPlayer in order to restore the init.py default Nuke was previously using.
Unaffected by 
project settings > color management
whether set in GUI followed by new Viewer, or in init.py knobDefault
Customer reported version
Customer reported platform
10.11
 
Steps to reproduce
 
1.
remove or hide from your 
˜/.nuke
preferences10.0.nk
uistate.ini
2.
unzip directory 
/IOD_setup
that contains init.py and OCIO files found here
/<share>/Testing/Bugs/238523/test_ticket_14172.zip
3.
open a terminal and set NUKE_PATH to point there
export NUKE_PATH=<path>/IOD_setup
4.
Launch Nuke 
Note the default Viewer LUT 
5.
quit Nuke
6.
Launch HieroPlayer, Hiero, or Nuke
without opening any project/script
7.
in 
 Preferences > Color Management > OpenColorIO config
set a custom config.ocio 
using
/IOD_setup/nuke-iod/config.ocio
and click OK to save the Preference
8.
quit without saving
10.
Launch Nuke 
Note the default Viewer LUT 
 
Workaround

Unknown. 
 
Reproduced by support
 
Nuke10.0v4
 
Expected behaviour
 
LUT set in init.py using nuke.knobDefault for Vewer.viewerProcess , and that worked before the OCIO config was loaded, would still be the default Viewer LUT
 
Actual behaviour
 
One of the OCIO LUTs became the Viewer's default LUT after a
custom config.ocio was saved in ˜/.nuke/uistate.ini  

    We're sorry to hear that

    Please tell us why