Any reason you guys can think of why Draft’s Event Listener wouldn’t be getting triggered?
I have a job with a DraftTemplate KeyValue… used to work fine in D5 and now nothing is spawned… I can see that the key is there on the job.
Also I tried overriding the SubmitMayaToDeadline.mel file by placing my own in the custom/scripts/Submission folder and it didn’t override the one in submission/Maya/Main.
Same goes for trying to override events/Draft/Draft.py. I put a Draft folder in custom/events and got no love…
The files in \your\repository\submission don’t support the “custom” folder overrides in the repository. The custom folder only supports the events, plugins, and scripts folders in the repository. That’s why the Maya submitter override isn’t working.
For Draft, do you just have the Draft.py file in \your\repository\custom\events\Draft? You need to place all the plugin files in your custom folder, so if you just have the Draft.py file, that would explain why it isn’t working. You basically need to override the entire plugin, not just individual files.
That was is… once I made the full event plugin it worked. Thanks…
Is there any way in the future to have the custom dir override the submission scripts? Would be nice to keep those seperate rather than chasing them down on every update? Or maybe even a place in the db that says these scripts have been customized so don’t overwrite on update?
The thing with these submission scripts is that they’re “outside” the core Deadline system. The other scripts, plugins, and events are all executed by Deadline applications, whereas the submission scripts run in the context of their individual applications. To make this work, we would have to edit the Client script to check for a custom Main script, and then call that one if it exists, otherwise default to the original. However, there are some cases, like Lightwave, where there is ONLY a Client script because lscript doesn’t seem to be able to run another lscript in the way that we need it to.
Since you are using modified submitters, perhaps you could just change your paths in your Client scripts to point to another script that will never get overwritten. You could even place it in the custom folder if you want. If you did this change though, note that you would have to push the Client script back out to all of your workstations.
