While working on having my plugin produce the same result on a given frame, it was weirdly enough only then that I realized that Nuke probably doesn't cache the way I always thought it does.
It seems to me that Nuke displays cached images in the viewer but in fact, it recalculates the whole tree in the background whenever you change the frame you are on. And depending on the machine you are on or even the mood Nuke is in, you may even see evidence of that by not being able to see color values in the bottom right corner for a couple of seconds. Even though the cached image already shows in the viewer. So... what is going on here? As far is I understand, Nuke should, through its hashing system, understand when neither the input image, nor the node tree below it was changed in between going from one frame to another and back again? And forget about my plugin, I tested this with just a Median node with a big filter size on multiple machines.
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
