Skip to content

External components when copied erroneously combine #106

@Reploidsham

Description

@Reploidsham

This is embarrassing to say, but in its current state at this time, using Pumkin's tools to copy VRCFury components from one avatar to another... if you have multiple sockets at the same point in the hierarchy, Pumkin's seems to erroneously merge them, resulting in the fine adjustments being lost and the default position of the socket being reset to a single gameobject with multiple conflicting SPS socket components.

So, Copying from Avatar A to Avatar B, as an example
Avatar A

Hips

Socket A
Socket B
Socket C

Avatar B

Hips

Socket with components of all 3 at default position

I'd like to append or clarify any options there are to prevent it from merging these external components, if possible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions