State:Closed|icon_bug|icon_nuke|database:public|Resolution:Fixed|TargetRelease:11.2v3|BugID:281553|
Problem summary
After setting a custom OCIO enviroment variable, project settings are populated with proper LUTs. Although, they are still missing in Nuke Color Management. It does not cause problems when exporting / creating comp as settings are taken from project settings.
Customer reported version
Nuke Studio 11.0v2
Customer reported platform
Linux CentOS 7.4
Steps to reproduce
1) Open a new terminal mode and paste the following environment variable, if you don't have Nuke 10.0v1 installed, then change the path for another custom OCIO config:
Reproduced by support:
NukeStudio 11.0v2 - CentOS 7.4
NukeStudio 11.0v1 - CentOS 7.4
NukeStudio 10.5v6 - CentOS 7.4
NukeStudio 10.5v1 - CentOS 7.4
NukeStudio 10.0v6 - CentOS 7.4
NukeStudio 10.0v1 - CentOS 7.4
Earliest version tested
Nuke Studio 10.0v1 - Nuke Studio did not exist prior.
Update:
After going through this bug, I believe that once the user has set the env var and checks their Color Management from the preferences,
Expected behaviour
Nuke's Color Management Project Settings and Preferences would be the same.
Actual behaviour
Despite having an environment variable set Nuke's Project Settings as well as Color Preferences are very different, and the Default Color Transform settings are missing.
We're sorry to hear that
Please tell us why