Hi guys,
We've just looked into this and it is a bug.
Normally when using a custom OCIO config the 'Use OCIO nodes when
exporting in Nuke' checkbox in 'ProjectSettings->Colour Management' gets
automatically set. When setting an OCIO config in the environment this
isn't happening.
As a temporary workaround checking this should fix the problem.
We've logged the bug:
Bug 47711 - 'Use OCIO nodes when exporting in Nuke' checkbox not set
when setting OCIO config environment variable
Hope that helps,
Peter.
On 17/02/2015 15:29, Sebastian Kral wrote:
Windows 7
On Friday, February 13, 2015, John Perrigo <jpe...@gmail.com
<mailto:jpe...@gmail.com>> wrote:
Ubuntu 12.04, Nuke 9.0v4
John
On 13 February 2015 at 23:15, Jimmy Christensen <ji...@ghost.dk
<javascript:_e(%7B%7D,'cvml','ji...@ghost.dk');>> wrote:
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
<jpe...@gmail.com
<javascript:_e(%7B%7D,'cvml','jpe...@gmail.com');>
<mailto:jpe...@gmail.com
<javascript:_e(%7B%7D,'cvml','jpe...@gmail.com');>>> 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
Nuke-users@support.thefoundry.co.uk
<javascript:_e(%7B%7D,'cvml','Nuke-users@support.thefoundry.co.uk');>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk
<javascript:_e(%7B%7D,'cvml','Nuke-users@support.thefoundry.co.uk');>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
Sent from mobile device
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
