Deadline path error

Deadline
1

I have an artist who is having trouble launching the Deadline Submit from his instance of Modo. Whenever he runs the DeadlineModoClient.pl he gets the error from the attached image. This is a really weird error because his path is set properly with Windows, Deadline 6 is installed on his machine, and he can access manually the directory which is holding the ModoSubmission.py. He doesn’t seem to have any other network connection issues, but he is the only one with this problem. I’m hoping that someone might have any idea of where else to look to find the issue. He is currently able to open up the Monitor and launch his scene from within there.

Thanks

James

Modo_path_error1.jpg
Modo_path_error1.jpg962×97 75.9 KB

2

Hey James,

I think I’ve seen this behavior before. I think it might happen if modo is started from a shortcut (like in the Start menu). Try using Windows explorer to browse to the modo installation folder (ie: C:\Program Files\Luxology\modo\601_sp5) and then just double-click on modo.exe to start it, then try running the script again to see if it works.

If it works this way, then that would imply that the modo environment gets mucked with when starting it from a shortcut. Why that would happen though is a mystery to me…

Cheers,

  • Ryan
3

Hey Ryan, so we just tried what you suggested and we are still getting that error. With Deadline 5 we all had a similar issue but we usually could fix it by restarting Modo. But with this particular artist nothing we do makes it work with Deadline 6.

4

Thanks for testing that. Can you launch modo normally, try to run the script again, and then check the Event Log in modo? The modo submission script should be printing out something like this:

modo_event_log.png

If you can send us the output you’re getting, we’ll take a look.

Thanks!

  • Ryan
5

Well I can see that it’s not finding the ModoSubmission.py. But that makes sense since it’s complaining about the DEADLINE_PATH. But I check his paths and they are the same as everyone else.

Modo_path_error_02.jpg
Modo_path_error_02.jpg1217×381 173 KB

6

Thanks. It’s strange, because this output would imply that the “deadlinecommand.exe -root” call is returning an empty string.

A workaround you could do for now would be to copy the modo perl script locally to their machine. Then open it in a text editor and find this line:

my $root = fix_path( `\"$deadlinecommand\" -getrepositoryroot` );

Right after this line, insert the following line:

$root = "//your/repository";

Of course, replace //your/repository with the actual repository path. This will hardcode the path into the script, and should work going forward as long as they use the locally modified script.

Cheers,

  • Ryan
7

Yeah it’s really weird that this is only happening to this one guy. I output the variables and he’s definitely not getting any path info. But for now I’ll use the hardcoded method. But hopefully I can find a fix for this.

Thanks!

James