[BUG-234350] There is still a significant number of users whose damaged attachment names are not updating from 'object' to their inventory names on attach.

[sl-service-account]

Information

I'm still seeing a significant number of agents who have relogged since the roll back of the bug reported in BUG-234277 where attachment root link names were changed to 'object'. This includes no-mod content such as name-brand mesh heads, bodies, clothing and accessories, even companions/breedables and HUDs.

This content is supposed to update its root link name to that of its user inventory name upon attach from inventory, but this is not happening.

Please investigate why this damaged content is not being updated correctly when it is attached from user inventory. Thanks.

Links

Related

• [ ] https://github.com/secondlife/jira-archive/issues/11234

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-234350 | | Summary | There is still a significant number of users whose damaged attachment names are not updating from 'object' to their inventory names on attach. | | Type | Bug | | Priority | Unset | | Status | Needs More Info | | Resolution | Unresolved | | Reporter | Lucia Nightfire (lucia.nightfire) | | Created at | 2023-08-29T15:35:20Z | | Updated at | 2023-08-30T15:05:17Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2023-08-29T12:26:24.687-0500', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': "I'm still seeing a significant number of agents who have relogged since the roll back of the bug reported in BUG-234277 where attachment root link names were changed to 'object'. This includes no-mod content such as name-brand mesh heads, bodies, clothing and accessories, even companions/breedables and HUDs.\r\n\r\nThis content is supposed to update its root link name to that of its inventory name upon attach from inventory, but this is not happening.\r\n\r\nPlease investigate why this damaged content is not being updated correctly when it is attached from user inventory. Thanks.", 'What were you doing when it happened?': '?', 'What were you expecting to happen instead?': '?', } ```

[sl-service-account]

Maestro Linden commented at 2023-08-29T17:26:25Z

[~lucia.nightfire], to be clear, the affected attachments appear with some other name when in inventory, but appear to be named 'object' when attached, correct? Do the same objects appear rezzed as 'object' when rezzed unattached as well? Could you send me a copy of an affected item for investigation?

The name of the item in agent inventory should of course take precedent over the name set in the object asset, so that any rename operations in inventory are reflected once the object is rezzed in-world.

It's possible that some script in an object remembered the name was 'object' previously and call llSetObjectName("object") on rez - there is nothing we could do about that case.

[sl-service-account]

Lucia Nightfire commented at 2023-08-29T23:11:32Z

If you look at pic 4 on BUG-234277 you will see many different creator's content is affected.

This is still the same content I'm seeing affected currently.

Mesh heads, bodies, clothing, accessories, etc.

Much of the content in that pic that is affected is no-mod.

I can't imagine some, let alone, all of them using any llSetObjectName() protocol on said content.

I did not have any of my content affected as I did not relog or detach anything on the server channel in question.

I will try and contact creators about this so I can get input from they or their scripters.

I will also try and engage with affected users directly as well.

 

[sl-service-account]

Maestro Linden commented at 2023-08-30T00:00:22Z

To be clear, what have you tried to restore the original object names of the affected objects? I assume relog while wearing the affected attachments has already been tried. Have you tried a manual detach & reattach while in a region, and does that work? The important thing is to not drop the attachment, since at that point the in-world object name will be the only one left.

[sl-service-account]

Lucia Nightfire commented at 2023-08-30T14:08:19Z

Again, this doesn't affect me. It affects many other users.

I have bots and scripted objects traveling the grid scanning attachments to maintain a database of the most popular mesh heads, bodies, mods.

I wear a scanner on my person as well so I also see directly when someone's attachments are damaged.

Anyone with a "What is she wearing?" or similar gadget can also see this.

I estimate somewhere between 5% - 15% of users that were online last week were affected.

These agents have relogged or detached and reattached their affected attachments already as their attachment rez times suggest so.

Most of these attachments are mesh, so no dropping would have occurred.

I have only seen a handful of legacy prim only content affected. Mostly HUDs, gadgets, bumpers and players.

Any content affected will show 'object' chatting or creating dialogs to their users.

This problem also impacts those who saw content of interest either via selection or gadget, wished to purchase their own copy, but couldn't because they couldn't identify it.

I did testing with manual (at object level, not inventory) & scripted attachment name change followed by either manual relog, scripted detach & manual reattach and each had their changed back to what the inventory name was. This includes attachments changed to 'object'. So it is curious why these names aren't getting fixed on their own.

I still can't buy the all of this content is using intermediate name changing protocols, which are only typically done with HUDs/gadgets such as translators or RP devices which temporarily invoke "personalization" inbetween chatting or dialog generation.

[sl-service-account]

Maestro Linden commented at 2023-08-30T15:05:17Z

These agents have relogged or detached and reattached their affected attachments already as their attachment rez times suggest so.

The thought is that when attachments are rezzed at login time, the item name set in agent inventory is not used on the rezzed object - instead, the object asset's name is used instead. The object asset's name would typically agree with the name in inventory, as the object asset would've been created at last logout time, but due to BUG-234277 there could be a mismatch. So if an agent has simply relogged a few times, any attachments that were exposed to BUG-234277 (with 'object' names) would continue to reference whatever name had been stored in the object asset.

In contrast, when objects are manually attached after login time, the item name takes precedent - as you see after renaming something in inventory before attaching it. That's why I suggest manually detaching and reattaching - it should fix the objects.