Deadline 6.1 -- 3dsmax isTileJob error

Deadline
1

Hello,

We are in the middle of transitioning from Deadline 5x to 6x and started receiving the error below. I was curious if someone might have an idea what could be wrong?

[code]

Error

Error in StartJob: AttributeError : ‘MaxPlugin’ object has no attribute ‘IsTileJob’ (Python.Runtime.PythonException)
[’ File “none”, line 71, in StartJob\n’, ’ File “none”, line 808, in StartMaxJob\n’]
at Deadline.Plugins.ScriptPlugin.StartJob(Job job, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException[/code]
`
Full log @ http://pastebin.com/fv9wB4tN

2

Also forgot to mention, we are using a custom submission library based on the functions that ship with deadline 5x. Have there been any changes to the way jobs are submitted to the deadline 6x repositories?

3

Just noticed that we are able to render a test 3dsmax job on Deadline 6.0; however, once we’ve upgraded to 6.1, the same test job failed. Has there been any major updates to the way 3dsmax works in Deadline 6.1?

4

Hi Brett,
There is a real mix up of versions going on here. From that slave report I can see that you are running the Deadline shipped v6.1 Max python plugin code, but you are running this on a v6.0 slave and also trying to use the v5.2 Lightning dlx plugin at the same time. This is going to cause major issues and I would recommend re-running the repo installer or starting a fresh to ensure all the correct version software is running together here and then once verified, look towards merging any custom code in your studio into the v6 platform. Going forward, the newer “custom” directory in the repository will really help you here as it allows you to keep your custom copy of a Deadline script, plugin, event plugin, etc separate from the versions we ship which will always be updated by us in each new release. This will help to ease any initial errors/bugs whenever a studio looks towards transitioning to a new version, as you can use a diff/compare text editor to carry out the code merge between our shipping version to all customers and any customisation a particular studio may have carried out.
Any questions on particular lines/functions, please do let us know.
Thanks,
Mike

5

Good to know! I didn’t realize that the slaves wouldn’t be receiving repository updates unless launched from the launcher application. It was just a matter of telling the slaves to restart in order to get everything upgraded and working again.

Thanks!