Maya: Bug fix the file from texture node not being collected correctly in Yeti Rig

[moonyuet]

Changelog Description

Fix the bug of collect Yeti Rig not being able to get the file parameter(s) from the texture node(s), resulting to the failure of publishing the textures to the resource directory.

Additional info

Make sure you have Yeti installed in Maya (with the license, too)

Testing notes:

1. Launch Maya via launcher
2. Create Yeti Rig Instance with your pgYetiMaya node.
3. Publish
4. It is supposed that the resources folder showed in your publish folder and the image search path would show the resource directory from the published folder.
   

[ynbot]

Task linked: OP-7463 Maya: Yeti publish textures

[LiborBatek]

Did tests in legacy OP for now but no luck...the publish being produced but without any trace of folder resources with any groom image maps...

And the texture path on the left Attribute pane:

[moonyuet]

@LiborBatek
Which version of maya are you using?
I am using same Yeti version with you, but I can extract the Yeti rig with resources folder in my side.

yeti_demonstration.mp4

[LiborBatek]

@LiborBatek Which version of maya are you using? I am using same Yeti version with you, but I can extract the Yeti rig with resources folder in my side.

yeti_demonstration.mp4

My being maya 2023 ...but as seen on your scrn capture, u have prefilled the path to your source folder with image map...this I didnt done....I have kept it blank (I was thinking that it get filled by the new asset/publish/ver/sources/.. just as soon as loaded into empty scene via loader overriding those present paths in the actual Yeti graph as sort of override...

So it makes sense to keep it empty (without user needing to care about it).

The Yeti addon has it just for cases when textures couldnt be find straight from the graph image nodes...which is the case with our Published yeti assets...

[LiborBatek]

I was refering to this one> Image Search Path

[LiborBatek]

When user prefills the texture path in Search Image Path slot it all works and publishes well with all resource texture maps!

Working fine when loaded into empty workfile as yetiRig asset and with correct path set to the publish folder version.

Approve!

[BigRoy]

So it makes sense to keep it empty (without user needing to care about it).

The Yeti addon has it just for cases when textures couldnt be find straight from the graph image nodes...which is the case with our Published yeti assets...

This should still be fixed right - so that it behaves like you describe? Making it work even if in the work scene the user had image search path empty?

[LiborBatek]

Now it works even when Image Search Path being left blank in the source workfile / yeti setup.

Also been successfully tested in both Legacy mode and AYON mode ...all working fine and without any issues!

[antirotor]

haven't tested it, but code looks good

[azhagurajpandians]

I'm experiencing issues with UDIM Textures. It's not recognizing or reading the textures with UDIM tags. Multiple texture tiles are not being found. I've checked the path in the Image Search Path slot as well and tested in both legacy OP and Ayon, but I'm encountering the same issue.