I previously tried getting modo working with Deadline 4 with no luck. One machine rendered, the others didn’t.
Fortunately, I got to try out the beta for Deadline 5 and those problems went away. I actually got it to render!
However, there is a new problem.
When I first submit a job, the log say’s it’s waiting for Modo to start… and it just sticks there indefinitely. It seems to hang for some reason. But, if I delete the job and resubmit, the job actually begins rendering on this second try. It works if I cancel the task on each machine, letting it restart by itself, and also when I delete the job form the monitor and resubmit. For whatever reason, on the second job submission, it always seems to work.
Any fixes I should be aware of or is it a bug?
Attaching the log on both machines showing where it just hangs.
This is a known issue. See the 2nd question under the modo FAQ for a couple known workarounds:
thinkboxsoftware.com/deadline-5-modo/#FAQ
We’re not sure why this problem occurs, but we have it logged as a bug and hopefully we can get to the bottom of it.
Cheers,
Just gave it a try, but still having the issue.
Just to be clear, I start Deadline Launcher (finder okay?). Then, from the launcher I start the slave. Then just submit a job as normal…
Unless, I’m missing something, doing this still causes the first submission to hang.
It’s not a huge deal, as I just cancel the current task on each slave and then they pick up the job on the next go round. It just means a few extras steps to get a job rendering.
Quick little update. It seems once I go through this “shutdown-resubmit” process, as long as I keep the slave running, all subsequent jobs render without pause. So I guess it’s just something that has to be done when deadline is first launched.
Hmm, I’m surprised that workaround didn’t work. Maybe try starting the slave from the command line instead. Just open a terminal and run “deadlineslave” with no arguments, and it should start up. We’re under the impression that the problem only occurs when the Slave is launched through Finder, and maybe that applies if the Launcher is also launched through Finder. If it also occurs when you launch the slave from a terminal, then the problem is on a larger scale than we thought…
Cheers,
Yeah, so far I can’t get deadline to start rendering on first submission… even if I open under terminal, both launcher and slave.
Basically, any machine that is opening deadline ‘fresh’ (hasn’t been previously rendering). I just need to make sure when I submit the job to let deadline hang on starting modo, then tell it to cancel current task. The next go around, deadline seems to work fine.
We are targeting this bug for Deadline 5.1. Hopefully we can get to the bottom of it…