Hi,
I have a feeling the render orders in Write nodes are not honoured when rendering in Deadline.
It used to happen automatically but now Nuke seems to insist on an adiditonal commandline argument to use render orders:
–sro force the application to obey the render order of Write nodes such that Reads can use
files created by earlier Write nodes
Can you make sure this actually happens? I keep getting renders that come back incorrect because the render order is not used.
Cheers,
frank
Hey Frank,
Go to \your\repository\plugins\Nuke and open Nuke.py in a text editor. Find this line:
Change it to this:
Save the file, and then submit a job that current fails to see if it makes a difference. If you could test 2 jobs actually, one with batch mode on and with batch mode off, that would be great. If this helps your problem, we should be able to get this in before RC2.
Thanks!
Thanks Ryan,
I’m just talking to the Foundry about this as I am of the opinion that this flag should not exist and Nuke should always use render orders.
If anything, there could be a flag for suppressing the render order values, but I have no idea when you would want that.
Anyway, I digress, I will test this on Monday and get back to you, and in the meantime try to convince the Foundry to get rid of this unnecessary gotach.
Cheers,
frank
interestingly, I cannot reproeuce this with a simple test script.
I will keep an eye out and let you know what I hear back from Foundry support about the “sro” flag. With my current test script, I don’t need to set it and it will still use the render orders (which is what I woudl expect).