There are hundreds of "NametagBackgroundMaterial" in the material list when viewed with the inspector.

[Aitolda]

This COULD be contributing to slowdowns as the inspector appears to shows hundreds of materials being used, despite just a handful in the scene. Needs further investigation on a locally run client.

Worth noting there quite a few "skybox" materials appearing as well.

[Gigabyte5671]

We may not be correctly destroying old materials when their parent meshes are removed from the scene. How many of these duplicate materials are there when you first open the app?

[Aitolda]

We may not be correctly destroying old materials when their parent meshes are removed from the scene. How many of these duplicate materials are there when you first open the app?

There's no way to shift-select and get a count, but it's likely hundreds and immediately.

[Gigabyte5671]

Yikes, that's not fantastic. Roughly how many chairs (or other interactive meshes) are there in the world?

I think it's the case that we're creating a new instance of the NametagBackgroundMaterial for every nametag/label in the scene. This is necessary for player nametags since the display name is in the texture itself. However, for generic labels on chairs (etc) we could memoize and reuse the materials. I'll have a look into this as soon as I can.

[Aitolda]

Yikes, that's not fantastic. Roughly how many chairs (or other interactive meshes) are there in the world?

I think it's the case that we're creating a new instance of the NametagBackgroundMaterial for every nametag/label in the scene. This is necessary for player nametags since the display name is in the texture itself. However, for generic labels on chairs (etc) we could memoize and reuse the materials. I'll have a look into this as soon as I can.

Looking at the blend file with anything called "animate_" its 282. However it's worth noting the sit icon/image actually doesn't seem to appear in this world for whatever reason.

EDIT: Looking closer that might actually be the scale of the objects causing this (0.02). At some point we might want to decouple the scale of the sit/icon from the object scale. I can't foresee a situation where that would be beneficial.

[Aitolda]

Winner winner, chicken dinner! (That fixes it).