Hi all,
I’m using Yeti and Redshift with Deadline. I’m using a mixed environment, both Windows and Linux and my renders are stored on a network drive.
When Yeti attempts to render a job in Deadline, it fails as it’s it is not converting the Windows drive (in this case the P: drive) to /mnt/p.
Here is the offending line from the Deadline log:
Yeti 3.6.4: ERROR P:/project_name/04_production/02_3d/01_maya/scenes/02_shots/sr_001/ep_001/sq_001/sh_050//06_cache/yeti/v000/project_hair.fur doesn't exists, please check your input!
However, the rest of P: calls are successfully converted to /mnt/p by Deadline.
I suspect, this is a Yeti issue failing to recognise the repository options replacement, but just wanted to confirm here as well.
Thank-you for your time!
By enabling Text Replacement in the MayaBatch Plugin Settings, I was able to get a little further with this.
The scene does render some hair, but only the first node.
Here is the output from the log:
2021-09-20 15:59:09: 0: STDOUT: [Redshift] Potentially invalid/unexpected UDIM texture tiles in sequence '/mnt/p/project/04_production/02_3d/01_maya/sourceimages/02_characters/01_dolls/neonlicious/01_primary/4k/skin_diffuseColour_<UDIM>.tga'! Is this intentional?
2021-09-20 15:59:10: 0: STDOUT: [Mon Sep 20 15:59:09 2021] Yeti 3.6.4: ERROR Invalid texture request P:/project/04_production/02_3d/01_maya/sourceimages/02_characters/01_dolls/neonlicious/01_primary/hair_mask.png with error "file doesn't exists" ...
2021-09-20 15:59:10: 0: STDOUT: [Mon Sep 20 15:59:09 2021] Yeti 3.6.4: ERROR Invalid texture request P:/project/04_production/02_3d/01_maya/sourceimages/02_characters/01_dolls/neonlicious/01_primary/hair_mask.png with error "file doesn't exists" ...
2021-09-20 15:59:10: 0: STDOUT: [Mon Sep 20 15:59:09 2021] Yeti 3.6.4: ( mid_Clump in project_sr001_ep002_sq001_sh010_anim_master:neonlicious_rig_master:yeti_neonliciousShape ) No fibres found in second input, clumping will be ignored.
2021-09-20 15:59:10: 0: STDOUT: [Mon Sep 20 15:59:09 2021] Yeti 3.6.4: ( clumping2 in project_sr001_ep002_sq001_sh010_anim_master:neonlicious_rig_master:yeti_neonliciousShape ) No fibres found in second input, clumping will be ignored.
It then proceeds to finish rendering the scene with only two strands of hair.
1 Like
I’ve also tried symlinking P: in the root directory and home directory to /mnt/p to see if Yeti will grab that path instead.
Unfortunately, I’ve had no luck with that either.
Turns out the Text Replacement in the MayaBatch Plugin Settings wasn’t a permanent fix as this causes pathing issues with our Windows machines.
teemue
December 9, 2021, 12:37am
4
Having the same problem… Anyone found a solution?
teemue
December 9, 2021, 2:39am
5
Ok, for us it actually helped to change the Path Mapping Mode to Text Replacement. This might cause problems later down the line (for example geometry cache doesn’t work, but using alembic instead, this might be coincidence though).
Any thoughts on this anyone?
The issue as we understand it is that Yeti paths don’t get effected by dirmap changes which is the system Deadline uses by default. That’s why moving to text replacement works. However text replacement can’t dive into linked files and remap them, like dirmap does which may explain the issues you’re seeing when dirmap is disabled.
It’s a bit of a rock/hard place situation that I haven’t come up with a elegant solution for. So I don’t have an answer but hopefully that little bit of insight is helpful.
