Problem with Deadline 5 and RPM 4.608

hmm… this is a fresh machine… I installed the latest RPM, Deadline 5, and RPM scripts for Deadline 5…

after telling RPM to use the Custom Submit script (Deadline 5)… I get this error:

Hi Joe,

This is a side effect of SMTD being unable to figure out its Home Directory, most probably because the command line call times out.
We have had some other users reporting the same and we are unsure what is causing this (beyond Ryan suggesting to make sure Windows and DotNet are up to date).

If you open a Command prompt and enter

deadlinecommand.exe -gethomedirectory
how long does it take before you get a return value?
(On my machine the return value is “C:\ProgramData\Thinkbox\Deadline” and it takes less than a second).
If it takes longer than 10 seconds, most commands used by SMTD like collecting pools, figuring out the Repository location and other similar operations will time out and the tool won’t work.

Hey guys,

We’ve also been having a small issue with RPM 4.608, it seems that sometimes the pool dropdown menu goes empty and doesn’t list anything. It tends to happen when you create a new pool in Deadline. We are also using Deadline 5

Roy

I wonder if SMTD or RPM cache the pools/groups, and then when a new one is added, it screws things up. Does the problem go away after restarting 3dsmax?

No the problem doesn’t go away after restarting 3dsMax. The other thing is that, it only happens randomly on some of the passes in RPManager.

I have a feeling that it might also have something to do with the StickySettings.ini in the 3dsMax SMTD?
I’m going to experiment with this, I have adjusted the StickySettings.ini PoolName to false, and in the SMTD_defaults.ini I’ve put PoolName=none
I’ll let you know if the 3dsMax guys are finding it a bit better or not.

By the way, there are two LimitEnabled=true in the StickySettings.ini file.

Thanks!

Thanks for testing that. I’m a little surprised that a 3dsmax restart doesn’t help the problem. Have you checked to see if the problem occurs in SMTD when it’s not being used within RPM? Maybe it’s something specific to the RPM integration.

Cheers,

  • Ryan

I’m getting the following error with Max 2011, win7 64, deadline 5, and RPM 4.608:

“FileIN of custom submission rollout failed”

It only happens on this one machine when I try to set the custom submission for Deadline 5 in RPM. Setting the submission to Backburner works fine FYI.

That’s interesting that it only happens on one machine. If you haven’t already done so, maybe try reinstalling RPM, and then reinstall the Deadline scripts.

I did that, and even tried rolling back–no luck. I should say, we only have 2 machines running RPM and Deadline in workstation mode. :slight_smile:

Any other ideas?

Hmm. Is there anything in the maxscript listener that might explain why this error is occurring? You can open the listener in Max by selecting MAXScript -> MAXScript Listener, or by pressing F11.

We’re having a problem where it sometimes doesn’t record changes in the SMTD tab in rpm. eg. priority, tasks per frame. It’s hard to track down.