Custom Cage Baking broken when you have multiple texture sets

[Leslie315441796xa1]

I tried using a custom cage again today and noticed its still broken
The preview window will show the custom cage properly but when you bake and have multiple texturesets it will give you a jumbled bake results .
However when i tried importing the same meshes just excluding ones that were a second textureset and did the same for the custom cage file the baking worked properly

its a bug within the software that has been there for a while now

[Leslie315441796xa1]

i tried to replicate it with simpler geo but it seems to work without issue on it having the same conditions as i mentioned before,
unfortuneately i cant share the meshes that do cause the issue but i think ive run into this before . i`ll update here if i find a better example that i can share

[leslie22587453hzfn]

ok i have a visual example left is the cage disabled and right is with the cage enabled
once the cage is enabled it is for some reason baking the second texturesets uv into the first ones

textureset 1 - ts2 - both of them overlapping to show that its the artifacts youre seeing on the cage bake corresponding where the hairuv overlaps with the body

triangulation and naming of both meshes is consistent
material assignment on the cage is also the same as it is on the lowpoly so theres no mismatch there

in the cage preview when enabling Use cage it also loads the second texturesets cage in the preview of the first

Use Cage disabled- Use Cage enabled (note the hairstrands cages which are part of a second textureset)

[kindhearted_beekeeper2580]

I've come across the same problem and managed to fix it by exporting separate cage files, one per texture set/material ID and assigning them independently in SP, rather than having one "master" cage file and assigning the same to all the sets. I think it's simply an issue of SP not being able to use the same cage file for two different sets.

[leslie22587453hzfn]

oh i havent tried it. might be a good temporary solution until this bug gets fixed then

thank you, hopefully someone from the support team has a look at this thread again