I’m curious why you guys kept this script in Perl and not rewrite it in Python?
It’s one of those “if it ain’t broke, don’t fix it” kind of things. 
Also, I don’t think the earlier versions of modo that we still support have a python API.
Cheers,
Ryan
Ah I see, that makes total sense.
This does bring up an issue that I have when upgrading. It’s not an issue with Deadline or you guys. But I have heavily hacked the submission scripts for Modo. Whenever I upgrade to a new version I have to go through and merge the two scripts. The more I’ve modified them the more work I have to do lol. I was curious if you guys have any input as to any methods to make this easier. I’m not a 100% coder, more of a technical artist. So I don’t a true coding environment setup with version control and all the goodies that comes with it. It’s not a big need. Just more of a convenience thing.
Merging code is an everyday situation here, and unfortunately it’s just a necessary evil when it comes to coding. Having a diff viewer though can be quite helpful, since it will allow you to easily see the difference between two files. You can google Diff Viewers to find one that you like. I typically use TortoiseGit’s diff viewer, since it’s included in the TortoiseGit installation on my machine.
Cheers,
Ryan
Yeah, it has gone long way to helping me understand what you guys are doing in the code. Thanks for the diff viewer suggestions. I’ll check those out.
I’m seriously considering an internal Mercurial repo for our submission scripts etc and treating new updates as a Thinkbox commit.
So I’ve been trying to implement the outputFileNamesFromScene into my scene but when I include it in the list of arguments for the deadlinelauncher it fails to launch. I’ve attached below a sample of the code I’m using to put the list of paths and file types together.
But just to test things out, I ran the base DeadlineModoClient.pl to see what exactly the outputFileNamesFromScene is doing. But when I ran it, the launcher didn’t run either. So I’m wondering if there is some bug in the base code that’s keeping the launcher from executing.
EDIT: Also adding the relevant changes I’ve made to the modoSubmission.py
modoSubmission_snippit.txt (2.39 KB)
getRenderOutArgs.txt (1.73 KB)
OK, feeling a little sheepish. But my code had a flaw. I counted my array length wrong. So I’m able to get the submit window to open. But now, when I press the submit button and nothing happens. This goes away if I comment out the part where I am populating the outputFileNamesFromScene array from the modo renderOutput info. I’ll have to look close at the Thinkbox method a little closer tomorrow.