Modo Output Pattern - Deadline default limits functionality

[anon63403938]

I’m curious if there is a particular reason for the output pattern that is written into the Modo plugin (modo.py)? As it is right now it really prevents one from fully utilizing Modo’s rendering capabilities with Deadline. I’ve been able to go into the python file and change line 189: “self.SendCommand( “item.channel outPat “[][]””, True )” to “self.SendCommand( “item.channel outPat “[][][]””, True )”

My concern is that while I can change this line myself and have it work I’m afraid future versions may prevent me from making these changes myself. It would be nice to have Thinkbox incorporate the default Modo output pattern into the modo.py file before 6.2 is released. As Deadline is by default the Output name is not included into the image name. Any time you use multiple Output items of the same type (e.g. Diffuse Coefficient) the most recent saved pass will over right any prior Output.

My pie-in-the-sky request would be to have Thinkbox make it possible to type in a custom output pattern when submitting a Modo job.

For clarity:

current Deadline output pattern for Modo: [][]
Default and more useful Modo output pattern: [][][]

[rrussell]

It would probably make sense to have an option in the Monitor submitter to specify the output pattern, so we’ll add that to the wishlist for a future version (6.2 has already shipped).

However, 6.2 shipped with a new integrated submitter for modo:
thinkboxsoftware.com/deadlin … Submission

If you use this submitter, Deadline will pull the output information directly from the modo render settings, so you don’t have to worry about output paths getting clobbered.

Cheers,
Ryan