Does the path mapping wrangle reference scenes or just images? I could imagine this gets complicated because the reference scenes themselves could need adaptation based on image references within them, and a hierarchy of references within references causes problems. Nonetheless, it seems needed and absent right now based on a simple test here (one reference scene):
0: INFO: Executing plugin script /Users/phil/Library/Application Support/Thinkbox/Deadline7/slave/dizzy/plugins/56d0e6a44041212dece300cf/Modo.py
0: INFO: About: modo Plugin for Deadline
0: INFO: The job's environment will be merged with the current environment before rendering
0: INFO: Performing path mapping on '/Volumes/Phil/Documents/modo/Scenes/dl_pathmappingTest/ref_tp.lxo'
0: INFO: Found mesh
0: INFO: Found camera
0: INFO: Found environment
0: INFO: Found groupLocator
0: INFO: Found translation
0: INFO: Found translation
0: INFO: Found rotation
0: INFO: Found rotation
0: INFO: Found scene
0: INFO: Found shaderFolder
0: INFO: Found shaderFolder
0: INFO: Found shaderFolder
0: INFO: Found shaderFolder
0: INFO: Found shaderFolder
0: INFO: Found shaderFolder
0: INFO: Found advancedMaterial
0: INFO: Found mask
0: INFO: Found defaultShader
0: INFO: Found renderOutput
0: INFO: With file name: /Volumes/Phil-1/Library_Annex/modo/Framestore/renderTest/ref
0: INFO: Raw path: /Volumes/Phil-1/Library_Annex/modo/Framestore/renderTest/ref
0: INFO: Massaged path: /Volumes/Phil-1/Library_Annex/modo/Framestore/renderTest/ref
0: INFO: Found renderOutput
0: INFO: With file name:
0: WARNING: Relative path detected
0: WARNING: Unable to find file /Volumes/Phil/Documents/modo/Scenes/dl_pathmappingTest/
0: WARNING: Not able to fix relative path
0: INFO: Raw path:
0: INFO: Massaged path:
0: INFO: Found polyRender
0: INFO: Found lightMaterial
0: INFO: Found envMaterial
0: INFO: Found sunLight
0: INFO: Starting monitored process: modo0
0: STDOUT: Received command: EXECUTE: !scene.open {/Users/phil/Library/Application Support/Thinkbox/Deadline7/slave/dizzy/jobsData/56d0e6a44041212dece300cf/thread0_tempcLxiS0/ref_tp.lxo} normal
0: STDOUT: ! (messageDialogs) [Yes/No/No To All] - File Not Found | teapot.lxo not found; select alternate file?
path mapping in Modo, as of Deadline 7, is a bit of an odd duck, as the code was provided to us by The Foundry. As I understand the code, when it does path mapping, the first pass is looking at relative paths to the original source location, and changing them to absolute. If it does not find the referenced asset near that location, it will try to do path mapping via the repository settings if it can. Can you share the full error report so we can get better context? Thanks.
Most of our path mapping is only on the original scene file, references are going to break. You’re right that it opens up a heck of a lot of complexity.
The only exception is in 7.2.1 Maya can now use dirmap to map things.
The current Modo plugin only rewrites videostill items, ie image files. It doesn’t account for any other file type. I’ve been reworking the script and I am waiting for more info from Conrad Wiebe @ Thinkbox and Simon Lundberg @ The Foundry to fix this.
Probably, I can’t find a download link lol. It’s difficult to keep on top of your releases and make sure you have the latest version.
My 7.2 links don’t go anywhere.
If you can let me know where to download the update from, I’ll have a look. - EDIT – Asked Kim Devloo for the links and a new beta license, so should be good to check this out now.
Very promising to hear it’s all been updated anyway.
First test with 7.2.2.1 and it’s still failing on .lxi irradiance cache files. The new plugin script (Monitor submission) is collecting all the other external file info and correcting the filepaths, but the render still fails. .mdd, .ies, .ldt, image files inc. psd
So yes, new version does work except for lxi irradiance cache files.
Please see my thread in the 7.2 beta forums for more detail and logs.
Just out of curiosity, is there scope for this to be addressed in 7.x, or 8.0? If 8.0, even if I’m just running the license-free mode, is there a way to sign-up to test changes here in alpha/beta?
There is an option in Modo to consolidate the scene, which will give you the option of merging reference scenes into the main scene. If Deadline doesn’t support it, then Modo already has a work around.
Path mapping on recursive scenes should be possible, you would probably need to retrieve the scene name, then add that to a second run of the math mapping script section.
I’ve added this to my thread in the V7 beta forums and copied here. I have a solution to the irradiance cache files not being found and paths massaged/mapped. Posting because of my previous test in this thread.
Irradiance cache files are now recognised and paths massaged after adding a tiny section of code to one line:-
V7.2.2.1 modo.py monitor submission plugin script /DeadlineRepository7/plugins/modo/modo.py
Line 673 is currently:-
if name == 'filename' or name == 'file' or name == 'pattern':
and needs updating to:-
if name == 'filename' or name == 'file' or name == 'pattern' or name == 'irrLName':
The same addition of 'or name == ‘irrLName’ will also work in V8.0.0.62 beta version if added to line 765.
v7.2.2.1 log for confirmation:-
2016-04-13 13:47:47: 0: INFO: Found polyRender
2016-04-13 13:47:47: 0: INFO: With file name: SERVER:Modo_Repository/Test_Scenes/Car_Anim_rebundled_22-13-29/assets/Drive_by_Cache.LXI
2016-04-13 13:47:47: 0: INFO: Raw path: SERVER:Modo_Repository/Test_Scenes/Car_Anim_rebundled_22-13-29/assets/Drive_by_Cache.LXI
2016-04-13 13:47:47: 0: INFO: Massaged path: //SERVER/Modo_Repository/Test_Scenes/Car_Anim_rebundled_22-13-29/assets/Drive_by_Cache.LXI
2016-04-13 13:47:47: 0: INFO: Found lightMaterial
2016-04-13 13:47:47: 0: INFO: Found lightMaterial
2016-04-13 13:47:47: 0: INFO: Found lightMaterial
2016-04-13 13:47:47: 0: INFO: Found envMaterial
2016-04-13 13:47:47: 0: INFO: Found envMaterial
