"...please add it as an arg to nuke.execute" (I also requested that it become
default, but...)
It's now logged as request #27141...
I sent this in as a feature request. But I think also that there really
isn't a need for a render order. If a write node has another write node
in it's dependencies, then the most final write node's render render
order should naturally be after the write node it's dependent on. And so
on... If this flag is calculating the render order based on
dependencies, then it makes precomping a lot simpler and setting render
order a non issue.
I haven't tested, but without the flag, it should still behave as
default and obey render order?
jrab
Peter Pearson wrote:
On 04/05/12 06:33, Frank Rueter wrote:
I find this a little curious.
Why is this behaviour not the default like it used to be (i.e. obeying
the render order)?
If I remember correctly, we made the decision because in certain
situations it might have slowed down rendering as it has extra stuff
to do in terms of tree traversal multiple times...
Peter
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
