ID 353294 - NukeStudio uses uistate.ini for colorspace defaults, when it should use %OCIO% environment variable configuration when enabled

Follow

​​Problem summary
When setting up a custom OCIO configuration through the %OCIO % environment variable, Nuke will use the the config.ocio for its "default LUT settings" as expected.

NukeStudio and Hiero do not use the %OCIO% environment variable location and will use the default .nuke/uistate.ini location for its "Default Color Config" instead.

As the environment variable is specifically set to a location, NukeStudio/Hiero should use the given config.ocio instead.

Customer reported version
nuke.10.5v7

Customer reported platform
fedora

Steps to reproduce

1)  Download the attached CustomOCIO.zip and extract to a temporary location.

2)  Set the Environment Variable to the config.ocio file within the downloaded folder path.


For Windows, copy the following into Windows command prompt:  ( Replace the folder path to your downloaded file directory )

setx OCIO C:\Users\CS_SYD_PC2\Documents\TestOCIODirectory\CustomOCIO\config.ocio
3)  Launch Nuke. Open Project Settings ( S ) and navigate to the Color tab. 

4)  Set color management to OCIO.

Values of default LUT settings will refer to roles in OCIO:  ( Custom OCIO is set to use 'raw' for all option fields )



5)  Launch NukeStudio\Hiero, Open edit -> Preferences via the toolbar and navigate to the Color Management tab.

Result: The values in Default Color Transforms do not use the %OCIO% environment variable custom settings and instead keep using .nuke/uistate.ini:

NukeStudio Preferences Window:

​​



Default Colorspace values within .nuke/uistate.ini:


​​

Workaround
Unknown, setting up the custom OCIO config through the .nuke/uistate.ini file unfortunately do not work.

Reproduced by support

This bug has been reproduced in:
NukeStudio11.1v3 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio11.1v1 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio11.0v4 - Windows 7
NukeStudio11.0v1 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio10.5v7 - Windows 7
NukeStudio10.5v1 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio10.0v6 - Windows 7
NukeStudio10.0v1 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio9.0v9 - Windows 7
NukeStudio9.0v1 - Windows 7 - Mac10.12 - CentOS6.9

Earliest version tested
- This issue appears to be in all versions of the product
Expected behaviour
NukeStudio/Hiero "Default Color Transforms" should use the OCIO environment variable configuration

Actual behaviour
NukeStudio/Hiero uses the .nuke/uistate.ini file, which is confusing for user's setting up custom OCIO configuration for both Nuke & NukeStudio

    We're sorry to hear that

    Please tell us why