We just upgraded to 7.1 last week and we have run into a show stopping bug with Modo. When we try to render any of our scenes that are referencing another modo scene the job fails out pretty quickly. The logs say that the referenced file cannot be found but it is in the same directory as the main scene file:
015-05-13 13:46:48: 0: STDOUT: ! (messageDialogs) [Yes/No/No To All] - File Not Found | refScene_01_v001_JB.lxo not found; select alternate file?
At this point I am forced to reinstall the previous version since we have a project which relies heavily on referencing. This was working in the previous versions of Deadline and nothing has changed in our scenes so I’m pretty sure it’s Deadline.
I’ve attached the job log and some test scene files. We are using Modo 801 sp03. We launch jobs into Deadline using a modified version of ModoSubmission.py. I have not yet updated our script with the 7.1 version of ModoSubmission.py.
Deadline_Job_log.txt (6.22 KB)
Reference_Debug_01.rar (17.8 KB)
Seems that the 7.1 submission script works on it’s own. So This isn’t a bug, it’s more of an incomplete update. 
I’m going through and updating our custom script now so hopefully once that’s done everything will work as it should.
OK this is really weird. So we ran a test launching a Modo job from the Monitor using the default submission script. Our job ran fine in that test. But when I run the same test on another machine the job will fail out with the same error from my initial post.
I’ve also updated my custom script to match the standard code from the 7.1 ModoSubmission.py. Unfortunately my custom script is refusing to launch the job so there must be some crossed wires somewhere.
But more importantly, the fact that I’m getting two different results from two different machines is just weird. I’ll look more into this in the morning, but I might need some guidance on this matter.
Quick update:
Seems that having the “Submit Scene” box checked is causing the errors. Even with my old 7.0 script this works. So something is not jiving submitting the Modo scene file with the job and scenes that have referenced files in them.
Hello James,
Can you confirm if the assets are relative or absolute? It looks like the scene is submitted with the job, and if the assets are relative, they won’t be found. Let me know.
Frankly I don’t know. Modo doesn’t display the referenced path like say Maya does. We aren’t doing anything special beyond Modo’s generic “Import Reference” function.
Based on our cross platform recommendations, it looks like you need to do few things to make this work. First, make sure path mapping is turned on in the plugin config. Second, make sure you have path mapping as per the instructions at docs.thinkboxsoftware.com/produc … iderations. If you can disable the submit scene, that might have better results though.
I already had both of those things set in Deadline and the jobs still failed. But for the moment, turning off “Submit scene” works fine for us. It would be nice to know why submitting a scene with references is causing these errors. The reason we use “Submit scene” is to reduce latency on larger scene files. It hasn’t been much of an issue since we upgraded our network. But it’s nice to have that in your back pocket.
Hello James,
It sounds like the asset paths are saved in the scene as relative to the scene file, which when submitted with the scene causes the assets to be presumed as local to the scene on the slave. What’s really odd is that you would think that with the option for path mapping, that the assets would be saved in absolute paths, albeit in their quirky formatting, but everything I have read says otherwise.
Yeah, Luxology is doing some weird things with their referencing. We’ve been having similarly weird issues with Alembic files as well.