Re: Force a refresh of context variables?

Tobias Pfeiffer <pixeld...@...>

Hi guys,
we were forcing Nuke restarts for a long time now just to make OCIO's context work for fresh opened scripts. This is really unconvenient and artist-unfriendly. Thats why I wanted to give fixing that problem a second try.
Im not a fan of using the Viewer Process, because than you are incorporating software specific color transforms that do not properly work in other software packages (Maya, Max, Houdini). Isn't being software agnostic one of the main reasons to use OCIO in the first place?
I fiddled around with the getCurrentContext method Mark outlined aboved and this seems to work quite easily. But how do I get Nuke to recognize that fresh and updated config?
Any tips?

Am Donnerstag, 16. Januar 2014 20:00:50 UTC+1 schrieb Mark Visser:

On Monday, January 13, 2014 6:35:29 PM UTC-5, dbr/Ben wrote:
If you only need a limited set of the env variables, you can set the Nuke node context tab up like so:

Brilliant, I hadn't thought of that. Just stuck that into our viewer process gizmos and it works like charm.

I wasn't aware of the metadata trick, neat.


Join to automatically receive all group messages.