i am using an expression to automatically use the script’s name in nuke in the saver. So when i do save new version, all my write node are saved according to this.
X:/folder/[python {nuke.root()[‘name’].value().rsplit(’/’,1)[1].replace(’.nk’, ‘’)}].%04d.sgi
When i render local i get the proper filename like this: NAZARETH_013_comp_sl_V01.0001.sgi
Just wondering why when i render on the farm i get: NAZARETH_013_comp_sl_V01_thread0.0001.sgi
it adds a _thread0
any ideas how i could remove the _thread0?
using deadline 4.1 sp1 and nuke 6.0
The “_thread#” part is appended to the end of the nuke script file so that we can support concurrent tasks with Nuke. I guess one way to remove it would be to account for it in your saver:
When you say “support concurrent tasks”, does that mean, if I disable path mapping and render with concurrent tasks, that I get into trouble? Should Deadline not automatically give distinct frame ranges to each task? What is the worst possible scenario?
If you disable the path mapping feature in Nuke’s plugin configuration, you shouldn’t have any problems with concurrent tasks. This is because Deadline renders with the original Nuke file in this case. If path mapping is enabled, each of the slave’s render threads needs to create a unique copy of the Nuke file at render time, because it is going through the file and swapping out paths.
