Thanks a lot for the detailed tip :) Mike ----- Original Message ----- From: rd-nuke-quintaindustries <rd-n...@quintaindustries.com> Date: Wednesday, March 30, 2011 11:35 pm Subject: Re: [Nuke-dev] Cache invalidation from OFX To: Nuke plug-in development discussion <nuke-dev@support.thefoundry.co.uk>
> > Yes, I declared this property for the parameter the same way and > when I try to add/remove/modify value and/or time of a keyframe of the > parameter, no single bit of cache in Nuke is invalidated ..... > > > By default when you modify a parameter value, nuke re-render the > frame, > so the cache is invalidated ! And that's sure it works. :) > So, by default, the frame is invalidated only if a parameter value has > > been modified at this frame. > > I haven't tried if kOfxParamInvalidateAll correctly invalidate all the > > time range if the value is only modified for one frame. If it's not > the > case, you can do a work around with an "IsSecret" parameter not > animated > and increment it when you need to invalidate the render for the full > time range. With this hack, one param value has changed at all times, > so > the cache is necessarily invalidated at all frames. > > _______________________________________________ > Nuke-dev mailing list > Nuke-dev@support.thefoundry.co.uk > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev _______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
