Which OS is this under? I don't see that behaviour on Linux.
- Jimmy On 13/02/15 13:39, Sebastian Kral wrote:
Hi John, we have a similar experience in Nuke. We launch Nuke with a custom Launcher to set up some stuff e. g. environment variables. When opening a new instance from within Nuke we loose the set environment. It seems Nuke / Nuke Studio is starting the process with the OS default environment instead of passing through the custom one. Didn't have time to look into this further or contact support. Perhaps somebody can comment on this one? Cheers, Sebastian On Thursday, February 12, 2015, John Perrigo <[email protected] <mailto:[email protected]>> wrote: Hey, I need a little help with this one. I'm using Nuke 9 Studio to create .nk scripts, and have OCIO environment variables configured. Studio creates the .nk script correctly, but when I launch Nuke with the created .nk file from Studio, it prompts me with the following error: "Viewer.viewerProcess: Bad value for viewerProcess: no_look (sRGB)" I then have to change the Project Settings > OCIO > viewer process LUTs to "OCIO LUTs" to get access to the correct LUT, I can then save the file and no longer get errors. If I just open a new Nuke session, it will correctly default to OCIO LUTs, but when opening a .nk script created in Studio it will set it to Nuke Root LUTs and I get the error. This is also annoying as Nuke Studio won't import the .nk script until I open in standard Nuke, change the viewer process and save. -- Sent from mobile device _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
