It appears that, when using the ExecuteScript option with deadlinecommand, it is prepending the current working directory to arguments that look like file names.
So, I have a command line getting generated that looks something like this:
deadlinecommand -ExecuteScript <jobWriter> --batch-name comp_script.v9.nk
But the JobWriter script recieves the batch name argument like c:\Program Files\Nuke\...\comp_script.v9.nk where the prepended path is where Nuke was launched from.
If I remove the “.” from the batch-name value (comp_script_v9_nk), it doesn’t occur. Is this intentional, and is there some way I can disable this behaviour?