DeadlineModoClient.pl often fails

[TallGuy]

I’m running Modo 701, latest SP and Deadline 6.1.

I use the DeadlineModoClient script to submit renders, which sometimes doesn’t work. The only way to get it to work again is restarting Modo. When it’s not working, I get the following error message:

The ModoSubmission.py script could not be found in the Deadline Repository. Please make sure that the Deadline Client has been installed on this machine,that the Deadline Client bin folder is set in the DEADLINE_PATH environment variable, and that the Deadline Client has been configured to point to a valid Repository.

I did check and everything the error message mentions seems to be fine, the ModoSubmission.py is in the right place and so on.

[dwallbridge]

Hello,

Could I have you open up “/Users/Shared/Thinkbox/Deadline6/DEADLINE_PATH” and verify that the correct path to Deadline’s install on the machine is there? If the file isn;t ther,e or the path is wrong, please correct it. Thanks.

[TallGuy]

@dwallbridge

Hello,

Could I have you open up “/Users/Shared/Thinkbox/Deadline6/DEADLINE_PATH” and verify that the correct path to Deadline’s install on the machine is there? If the file isn;t ther,e or the path is wrong, please correct it. Thanks.

I can’t even see a Users/Shared folder, let alone the rest.

By the way, I’m on Windows 7, in case that makes a difference.

[MikeOwen]

Hi,
Dwight assumed you were running Modo on OSX. See attached screen-grab for Windows. You should be able to see the DEADLINE_PATH in your sys env variables? If not, then perhaps the installer was not executed with a user with enough permissions (admin req.) to install the Deadline client software? Reinstalling using local admin rights should resolve the issue. If this env variable is indeed present on your system and contains the path where you installed the Deadline client software to (image depicts the default path location), then it may just be the case, you need to restart your machine since installing the software? If not, with local admin rights, you could manually insert this sys env variable onto your machine.
Mike

[TallGuy]

I see, thanks.

The answer is that, yes, the DEADLINE_PATH System Environment Variable is present and it is set to the correct path to my Deadline6 install.

[MikeOwen]

Deadline v6.2 released 28th May contains many Modo fixes including distributed rendering support and a new integrated submission script/UI:
thinkboxsoftware.com/deadlin … -2014.html

An updated v6.2 license is required, but is free if under annual support. Please do contact sales@thinkboxsoftware.com for the download links and updated license file to be created for you if applicable.

[Alcium]

I’ve seen that mostly happening when modo was not launched in a particular way before calling the script

Works when using pinned icon from the taskbar, recent program shortcut, or searching for modo in the start menu

Any over way of launching modo will result in failure of the script, “weird” will you say … I couldn’t say better

[TallGuy]

@Alcium

I’ve seen that mostly happening when modo was not launched in a particular way before calling the script

Works when using pinned icon from the taskbar, recent program shortcut, or searching for modo in the start menu

Any over way of launching modo will result in failure of the script, “weird” will you say … I couldn’t say better

Interesting. I may have to test that one out. That would put the problem in The Foundry’s camp.