Re: Reloading Context's env
Jeremy Selan <jeremy...@...>
toggle quoted message Show quoted text
Thanks for the note. I was actually just looking at addressing this issue on our end! (if you had waited a week you may have never noticed).
The issue is actually two-fold.
First, I really dont want to consider the envvars themselves to be mutable. (The envvars are just the context defaults.) So what we're going to do is on all the nuke nodes add a "context" group, where you have key value string pairs open by default. So in your case, you could for example set
context.name1 = "SHOT"
context.value1 = "ab-123"
and these will take priority over the default values, allowing you to change SHOT (or any other envvar) as needed dynamically.
The second issue is actually this one:
The nuke node's cacheIDs only are built based on the knob values, not the underlying OCIO cache ID. What this means is that if you load a common image (marci), render with a default display node, quit nuke, change the OCIO to a similar config but with a different film lut, relaunch nuke, and view marci... You'll get the old image if it's still in the disk cache. (Note you can avoid this with the clear disk cache menu option). But the better solution is to feed nuke the real cacheid, then everything will work automatically.
On Tue, Mar 1, 2011 at 3:25 AM, dbr/Ben <b...@...> wrote:
Today I've configured OCIO for a small project at RSP. It was perfectly straight forward, but I encountered a problem..