Whoever produced this node graph needs a good telling off.
I've always been of the opinion that, unless you're a one-man-band, the
script is as important as the final pixels you're delivering (if not
more so), and working within a team, a compositor should be responsible
and take care that anybody can open, tweak and render their scripts
without too much pain.
I have seen far worse than the attached image though :-D
Makes you want to write a callback that refuses to render if their are
too many pipes that aren't horizontal or vertical ;)
On 10/4/12 10:13 AM, helmsie wrote:
Thanks Howard. I stand corrected.
Having the ability to quickly walk through and reorder a stack can add
speed and organization to the workflow. I'm constantly seeing Nuke
node graphs like the attached that could be significantly simplified
with a stack node as a precomp. A pick your poison. So far, looks like
most folks agree with you.
Helmsie
[quote="mrhowardjones"]It was the multiLayer node - see attached.
I remember it became an issue on the list at the time as it was
thought of as a bad idea, and the consensus was if you used it with
one operation only then
it was useful. So we ran it as a multiScreen, multiOver etc...
Howard
[quote]
_______________________________________________
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
