Hi John,
Do you mean passing the actual max .exe additional arguments beyond what Deadline does already? If so, nope, though I’m sure it’d be possible by amending the plugin’s python file in deadline.
If you mean passing the job generic information that can then be used by other Deadline plugins/events/whatever then what an amazing coincidence. I don’t come on this forum often, but I have today to post about a bug in the 3dsMax submitter which meant that adding key pairs of data via Maxscript didn’t actually work.
If you apply my fix in that thread, they’ll work fine and then you can stuff all sorts of arbitrary data in there which can be read by other plugins or events. In my case, we have a simple python script that runs on each job completion which conditionally moves some of the output files around from where they’re originally rendered to. The conditions can (now) be supplied in the Max Job, so our custom submitter can basically say “move=true” and it’ll move them, or “move=false” and it won’t. Naturally you could add whatever information you want in here, and then pass that information to a function as an argument.
As for examples, if you follow my link to the other thread, I posted a link to the Documentation where it’s mentioned (right at the bottom) how to do it. Of course, it won’t work if you don’t apply the fix but actually adding the data is a piece of cake.