Copy Skin Weight Error: Skin Node

Copy Skin Weight Error: Skin Node

cmills7920
Advocate Advocate
3,700 Views
4 Replies
Message 1 of 5

Copy Skin Weight Error: Skin Node

cmills7920
Advocate
Advocate

Hello All,

 

Thanks for your time. I am attempting to copy skin weights from one mesh to the mesh's clothing, but I am encountering an error. It says a skin node cluster should be selected with the -desinationSkin/-dsflag. I am unsure what this means. In tutorials it snaps to without much fuss. Any advice would be appreciated.  Image example attached.

0 Likes
Accepted solutions (1)
3,701 Views
4 Replies
Replies (4)
Message 2 of 5

Anonymous
Not applicable

Hi

I think one history in your cloth node. So delete history and rebind the  cloth, then copy the skin from body to cloth.

Message 3 of 5

cmills7920
Advocate
Advocate

Hey thanks for the response. Upon deleting the history of the cloth and eliminating the ncloth assigned  I still receive the error below. I mimicked the settings you have attached and it did not make a difference. I'm not seeing anything about this error online.

 

// Error: line 0: A skinCluster node should be specified with the -destinationSkin/-ds flag.

0 Likes
Message 4 of 5

cmills7920
Advocate
Advocate

You're definitely on to something. I had previously messed with the shirt and pants meshes as ncloths. Now, even when I delete their history and the ncloth in the outliner they still won't accept the copied skin weights. The shoes that I did not experiment with ncloths copies the weights fine. Thanks for helping me narrow down the problem, but if history deletion and ncloth deletion doesn't work idk what to do. Export and reimporting the mesh doesn't work either. 

0 Likes
Message 5 of 5

cmills7920
Advocate
Advocate
Accepted solution

I found a solution! It's not pretty though. I exported the mesh as an obj with nothing but its materials and it's normals, nothing else, then reimported it. I bound it and it copied the weights fine. Still no idea what the original issue was but at least I found a workaround. Thanks for your help!

0 Likes