I honestly don’t know what could be the problem, no errors thrown, no warnings, no actions. But, I wrote a simple Event plugin to submit the same job that just finished, in 3ds Max, only with a few different options. Then when the second one is finished to submit a Nuke based off of that.
However, I’ve batch-submitted a ton of jobs (via another of my scripts) using the -drop flag, if that makes any difference, but the Event Plugin never does anything. It doesn’t throw errors, but it also doesn’t submit the jobs.
I double checked the conditions under which it should submit new jobs and they’re all fine.
Here’s the event plugin I’m talking about. It should only re-submit a 3ds Max job if it contains “GT_” in its name and “prepass” in the comments. And it should submit a Nuke job, if it contains “GT_” in its name and “beauty” in the comments. The rest is pretty much a modified rip-off of your submission scripts
I don’t see anything wrong with the script. Also, I don’t think a drop submission would matter here, since once the drop job is converted to a normal job, it should behave the same.
You can use ClientUtils.LogText( “blah” ) to log information to the log of the application that is running the OnJobFinished event. Note that if you requeue tasks and then mark them as complete from the Monitor, this will trigger the OnJobFinished event, making debugging easier. You can find the Monitor log by selecting Help -> Explore Log Folder. In Deadline 5.1, event plugin logs will be saved as regular logs for the jobs.
You can also use ClientUtils.ExecuteCommandAndGetOutput to return the stdout of the submission and write that to the log to see what the submission results were.
Man! Thanks a lot for the Log tips! I managed to make the event plugin work with those!
Which is another proof that the dev tools for Deadline scripting are a bit lacking, unfortunately
The problem was that the moment it found the max scene that matched the first criteria, it worked, but it never could have gone past that as I had the “return None” command in there, so the second test was never performed!
I fixed it only thanks to the logs as I completely missed this mistake of mine.
Thanks again, Ryan, your help is priceless, as always.