I find this a little curious.
Why is this behaviour not the default like it used to be (i.e. obeying
the render order)?
On 3/05/12 3:18 AM, Peter Pearson wrote:
On 02/05/12 15:01, John RA Benson wrote:
I just noticed this from "nuke -h" (6.3v7):
--sro force Nuke to obey the render order of Write nodes such that Reads
can use
files created by earlier Write nodes
Looks like it's new with 6.3?
Is there a magic way to do the same with nuke.execute(...), or is it the
default?
Hi,
It's not currently exposed via Python I'm afraid...
You'll have to get in touch with [email protected] and get them
to raise a feature request...
Peter
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
