On Mon, May 14, 2012 at 3:23 AM, Jonathan Egstad <[email protected]>wrote:
> > What the *HECK* is Nuke doing, constructing a *second* Mirror Iop on a > single-view Node? > > My guess is that it's the relatively new multi-frame caching system which > is attempting to cache multiple frame's worth of Op tree data. If the > input of Mirror was a Constant I doubt it would have created the add'l > instance (I hope…) > > By the way just to clarify Jonathan's earlier comment about the multi-frame caching system ( aka 'aggressive caching' ). This feature is not implemented by multiple ops, but rather by having the caches for each op live in a global pool rather than directly on the ops. Pior to Nuke 6.3 if an op had a cache it lived directly on the op and was destroyed for each context change. Eg a frame change. After 6.3 and with the aggressive caching feature turned on the caches now live in global pool and are not destroyed when an op is reused for another context. So now when an op is set up for the new context it checks the global pool to see if a cache already exists for that op, if so it reconnects to that cache. This can make it much faster to re-render when flipping to and from frames Nuke has already rendered.
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
