> 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…) Try attaching something between the Mirror and the Viewer so that the Mirror doesn't end up owning an output cache and see if the behavior is the same. > Oh.. and P.S.? Why is it calling _validate twice on exactly the same data? > Something bizarre with the Viewer I expect. That I can answer definitively - check the state of 'for_real'. Nuke should call _validate(for_real=false) first so that an Op can get it's output configured correctly, then a second time with for_real=true for when engine() is about to be called so that the Op can prepare itself for data processing. Bill was never happy about the two-pass thing but we never came up with a better scheme that kept _validate() as simple as possible (we didn't want two separate virtual calls that did almost exactly the same thing most of the time.) -jonathan _______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
