I’m fairly new to Deadline and I’m still learning it’s ins and outs. I’m working with Deadline 5.2, Modo (all versions), and Windows 7.
The issue is that I’m not understanding how the list of executable paths work with the different Modo service packs.
For example this is what I have set in the Modo 6xx Render Executable box:
C:\Program Files\Luxology\modo\601_sp5\modo_cl.exe
C:\Program Files\Luxology\modo\601_sp2\modo_cl.exe
C:\Program Files (x86)\Luxology\modo\601_sp2\modo_cl.exe
/Applications/modo.app/Contents/MacOS/modo_cl
Is this a stable set up that will allow me to render with any version of Modo 601 that I want or need to? Or is it wiser to have this pointed to only one service pack executable per version?
Thanks!
For modo, Deadline is only looking at the major version number when choosing which version of modo to use. The way the paths list works is that the Slave running on a machine will use the first path that exists. So if all of your machines have C:\Program Files\Luxology\modo\601_sp5\modo_cl.exe, then that’s the only version that will ever get used. Unfortunately at this time, Deadline doesn’t have a way to distinguish between service packs for modo (or any application it supports for that matter).
Cheers,
Thanks for the clarification Ryan. You’ve been a great help today. 
I wanted to dig up this old thread. I’m doing some tests with a beta version of Modo 801 sp2, while our studio is currently on 801 sp1. The problem I have is that I still would like to use Deadline and our render farm to run jobs. But from the way I understand it, I can only give Deadline one path:
C:\Program Files\Luxology\modo\801_sp1\modo_cl.exe
It won’t accept something like:
C:\Program Files\Luxology\modo\801_sp1\modo_cl.exe
C:\Program Files\Luxology\modo\801_sp2\modo_cl.exe
In this later situation it will only ever look for sp1 because it is on top is that this correct?
Thanks
James