DimplesApplePie Spicy
Description:
When importing a Collada (.dae) file from Blender into Second Life, one or more objects within the mesh linkset frequently get renamed incorrectly, even though all object names are clearly and uniquely set in Blender prior to export.
This issue occurs systematically:
All objects are properly named in Blender.
The .dae file is verified to contain the correct object names.
However, upon import into Second Life, at least one object's name is arbitrarily replaced by the name of another object in the linkset.
This results in duplicate names in the final imported mesh, despite no such duplication existing in the original .blend or .dae.
This bug makes it extremely difficult to manage and script mesh components reliably, especially when using scripts that rely on precise object names via llGetLinkName().
Steps to Reproduce:
Create a multi-object mesh in Blender with uniquely named objects.
Export to Collada (.dae) using SL-compatible settings.
Import into Second Life using the Mesh Uploader.
Observe that one or more objects are renamed incorrectly during or after import.
Expected Behavior:
Each object should retain its unique name exactly as defined in Blender.
Actual Behavior:
At least one object name is replaced by another object's name, leading to incorrect duplication.
Notes:
This happens regardless of naming conventions (e.g., simple vs. complex names, underscores, numbers, etc.).
It's not caused by Blender's export; inspecting the .dae shows correct names.
The issue seems to originate during SL’s import processing stage.
Please investigate and correct this persistent and highly disruptive behavior.
Just a final note: it's been this way for years. It's annoying having to check each object name one by one just to find the one that's not named properly.