Just noticed when I bring in the exact same character again the collection name is named opposite of blender default..

[Joe Morris @ FAST Animation Studio Toolz]

This is just a proposal for an enhancement you know but if it would match the standard blended way of doing things I think it would be a little bit better for users of your API … you know just when you bring in the same character again have a period 001 appended to the collection name….anyways take care and have a good Monday!!!

[Alessandro Padovani]

I too find it annoying that the old objects are renamed to .001 instead of the new ones, but I’m not sure if it is the addon or blender doing it.

[Thomas Larsson]

It’s the addon. It first creates an object, then sets the object name again to get rid of the .001. Same with collections, I think. I thought it was better this way, but I don’t have a strong opinion about it.

[Alessandro Padovani]

The default for blender is to rename the added objects rather than those already in the scene. Plus blender should do it automatically so may be no new code is necessary for that. If fixing this is not a trouble it would be nice to follow the blender default.

[Joe Morris @ FAST Animation Studio Toolz]

Yes that would work so nicely with the functionality of your API make it such a more smooth experience of course there are workarounds but thanks for discussing this

[Thomas Larsson]

Fixed in last commit. Both objects and collections retain their names, both when imported and when rigs are merged. All mesh objects have a name that ends with “Mesh”, to avoid name collision with the corresponding armature.

[Alessandro Padovani]

Commit b539354 works fine here, thank you for taking the time to fix this. I believe it’s what’s expected by the blender users how it works now.

[Joe Morris @ FAST Animation Studio Toolz]

Thank you so much for doing that !🙂🙂🙂