Getting "thread0" in TCL expression in Nuke from root.name

Deadline
1

Hi there,

does anyone know why the TCL expression [value root.name] returns a “thread0” (i.e. C:\folders\filename_thread0.nk) in the actual file name on the farm, but doesn’t on a workstation?

The idea is to be able to re-cycle a Nuke script so that all the read and write nodes have TCL expressions so that I can source the dir path and file name off of it and thus get different files under different folders.

But deadline reports of this nonsense when the Nuke script gets submitted to the network!

Does anyone have any experience with dealing with such TCL expressions in Nuke and Deadline?

Thanks a lot in advance!

2

Hmm… ok, I managed to work around the issue:

[string trimright [string trimright [file tail [value root.name]] .nk] _thread0]

but still, it’s kinda interesting that Deadline adds those names as well as actually moves the Nuke script file to the local directories.

Why?

3

In order to support Path Mappings in Nuke, we have to edit the Nuke script before rendering. We create a local copy so that we aren’t editing the original, and we stick the thread number on the end so that slaves that are rendering concurrent Nuke tasks don’t run into conflicts.

You can disable Path Mapping in the Nuke plugin. If disabled, Deadline will no longer create that temporary file.

4

No! I love the path mapping feature! :slight_smile:

I was just curious about what was happening there behind the scenes. I managed to work around the “limitation” already, so, I’ll stick with that.

Thanks!