Problem summary:
OCIO config files stored in ~/.nuke/OCIOConfigs/configs are disconnected and not found when Nuke Studio is relaunched
Customer reported version:
Nuke Studio 14.0v3
Customer reported platform:
macOS N/A
Steps to reproduce:
1) Open the Nuke installation directory and copy the /plugins/OCIOConfigs/configs/nuke-default/config.ocio file.
2) Paste the file into the ~/.nuke/OCIOConfigs/configs directory and rename it "dotnuke_config.ocio".
3) Launch Nuke Studio and open the Project Settings with Project > Edit Settings
4) In the Color Management section, change the OpenColorIO Config to the dotnuke_config file:
5) Close the Project Settings, and save the project with File > Save Project
6) Exit Nuke Studio, then relaunch the program.
7) Open the saved project and observe the error message, "Could not load OpenColorIO config file, using previous config":
8) Navigate back to Project > Edit Settings > Color Management, and observe that the dotnuke_config is no longer selected but is still an option:
Expected behavior:
Nuke Studio should retain the Project Settings between sessions and be able to locate config files consistently.
Actual behavior:
Nuke Studio attempts to locate the config file from the Nuke installation directory instead of from the ~/.nuke/OCIOConfigs/configs path defined in the .hrox file:
Workaround:
Setting the OpenColorIO Config to custom and selecting the desired config file seems to work without issue, pictured below:
Reproduced by Support in:
Nuke Studio 14.0v3 - Windows 11, CentOS 7
Nuke Studio 14.0v2 - Windows 11, CentOS 7 - Regression
Unable to reproduce bug in:
Nuke Studio 14.0v1 - Windows 11, CentOS 7
Earliest version tested:
Nuke Studio 14.0v1- This issue doesn't appear in this version and has regressed
Additionally, this feature (loading OCIO configs from ~/.nuke/OCIOConfigs/configs) did not exist before Nuke 14.0v1.
