Okay, this one’s got me stumped.
We’re using deadline 2 and Fusion 5.3.
With a straight out of the box installation of the render slave, everything seems fine…as soon as we change the preferences to load the plugins from our network repository, deadline is no longer able to process the job (it simply times out…we have a timeout of 120 seconds)
Having mucked around a bit, it would appear that eyeon is getting stuck at “Initialising Texture Manager”
I’ve written a debug utility that basically mimics the deadline process by launching the console slave and then feeding the startJob and renderTasks scripts to it. This works.
Okay, still testing…
I’ve updated one of our renders to point to it’s local repository (as per it’s default installation) it it seems to be working fine…
Now I now that the console slave CAN render using our “network” paths, as I’ve got the debug tool (and your scripts) to prove…soooo, something else is interfering.
Not know the workings well enough, it is difficult to point the figure directly at an issue, but at moment, deadline is been bad
Shane
Never let an artiest install software…
I tracked down the issue to a misbehaving plugin. And while fusion showed an error while loading it (in the logs), deadline seemed to get tripped up on it for some reason…as my test rig didn’t seem to be bothered by it.
Shane
Glad to hear you figured out the problem. I wonder if you would have run into the same problem if you had used Renderslave instead of Consoleslave… we still use Renderslave here without any issues, mind you we’re still on Fusion 5.2. We’ll keep an eye out for this when we eventually upgrade to 5.3.
Cheers,