In Preferences > Node Graph, there is a setting "new Merge nodes connect
A input" (the knob name being "goofy_foot"). I can't remember what the
default setting is, but I have it disabled, and a series of Merges is
created as I'd expect
However, the autoplace layout is indeed a bit strange:
The merge is placed under the right-most upstream node. I'm not sure
why, but I would guess it was considered more generally useful by
whoever wrote the function.. maybe..?
It'd be nice to have an implementation of the node layout code in
Python, to experiment with different layouts..
Somewhat tangentially, I played around with using graphviz's "dot"
command to layout a Nuke node graph. It was interesting, if over
complicated and a bit impractical (and I only had it working for the
entire tree, not the selected nodes):
http://i.imgur.com/f1mK7.png (left: graphviz, right: nuke's autoplace)
https://gist.github.com/dbr/1255776
On 18/05/13 11:35, randyv wrote:
Try this .... press m them again and again and again .... what do you get ?
A script with the merges going straight down - in a B stream . These are
the built in rules of NUKE node graph structure. Why aren't they applied
to the Autoplace function?
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
ben dickson
2D TD | [email protected]
rising sun pictures | www.rsp.com.au
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
