In more recent versions of OpenColorIO, OCIOFileTransform (and other nodes) have a 'reload' button. http://opencolorio.org/ChangeLog.html
Nuke is currently shipping with OCIO 1.0.0. In a future Nuke, when the foundry updates to a more recent plugin/library version, this functionality will automatically be exposed. The foundry is aware of the need to bump up OCIO versions, but it never hurts to +1 them on this issue... In the meantime, you can force OCIO to re-read luts using the python console: OCIO.ClearAllCaches() and then *also* flushing the internal nuke images caches. -- Jeremy On Wed, Sep 19, 2012 at 11:33 AM, Dan Rosen <[email protected]> wrote: > Hello all, > > I have been (happily) using the OCIO nodes. In doing some testing, > I've just noticed that there are some significant caching bugs. If I > write out a lut to disk and read it in with OCIOFileTransform > everything is fine. If I change the look and overwrite the lut file on > disk, the OCIOFileTransform ("read") it won't necessarily update. If I > get a new OCIO node it's still out of sync showing the old lut. If I > delete the lut file on disk the UI still thinks that it's there. > > I have cleared buffers and disk cache (Cache menu), but it's not until > I fully quit and relaunch Nuke that I can see the changes. Is there > another buffer/cache clearing mechanism? Is this a GPU issue? Any > other thoughts or help? > > thx, > Dan > > I am on MacPro Quad-Core Intel Xeon (2.66GHz), NVidia Quadro 4000, OSX > 10.6.8, and Nuke 6.3v8 > _______________________________________________ > 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
