V-Ray Proxy missing textures due to UVsets with different names

[seq]

Hello,

in the past days some of our V-Ray Proxys rendered totally or partially without textures. After hours of error searching we found out that if you have two objects with UVsets that are named differently (e.g. UVSet and map1) and you export them together as one V-Ray Proxy, the textures are missing.

As we found no hint neither in the web nor in the forum, we hope that this information might help someone in the future.

Nice day
Lars

[yolov]

Seems to work fine in a simple test on my end.
Can you share an example (or send it off the forum)? Or maybe recreate it from scratch in a simple scene/proxy?

[seq]

Hi Alex,

attached a simple scene (Maya 2022.3 + V-Ray 5.2, Windows 10) with two spheres and two cubes with a grid texture. When you export the four objects as a proxy (Use the new VRayProxy node enabled) and render the scene, some textures are missing.

The UVset of the spheres is named "map1" and of the cubes "UVset".

Hope that helps,
Lars

[yolov]

Right, thanks for the files. This is something we'll look into, but until we figure something out, I can propose a solution.
After importing the proxy, find the 2d placement node of the texture and add extra V-Ray attributes to it - choose "2D placement options".
Enter -1 for the index and this will make V-Ray take the first UV set it sees for each proxy sub-object.

[seq]

Thanks Alex for the solution / workaround. Amazing how many unknown options slumbering within V-Ray!

[yolov]

We've made a note to document this, as it's actually a special case where the intended behavior is a negative-1 index to link the first uv set in the list.
As for the number of options - we try and maintain a reasonable and manageable amount, but they are usually added based on user requests

[seq]

Can imagine that every user wants his / her favorited options added. So you make a great and wise job everyday! Thanks.