Around 30 minutes ago, changes to a specific mesh in our experiences were made without our doing - and these changes were subsequently published to our production places. As far as we know, this issue has only occurred with one mesh across two experiences. In either case, the modifications made to the mesh file were published without our doing and players now see these meshes incorrectly.
There are no property differences between the two meshes, and through some testing, here’s what we’ve discovered about the incorrect behavior:
Rejoining a studio session where the correct visual behavior of the mesh occurs will result in only being able to see the invalid visual behavior.
Inserting meshes from a valid studio session and the invalid one, respectively, will result in only the invalid visual behavior being seen.
The affected experiences in question:
Expected behavior
Meshes should appear as they were inserted into Studio originally. Mesh content should not be modified after a mesh file has been uploaded to the website.
Same thing happened around an hour ago in ‘Rogue Lineage’, where I suddenly received an influx of bug reports about a weapon’s model size being changed.
ID of an affected mesh: rbxassetid://3141544527
It struck me as odd that this mesh was the only one (to my current knowledge) that had undergone any kind of change. An additional detail would be that in Studio, the mesh seemed to be larger than the restrictions of the MeshPart’s size, as I could not select the mesh if clicking outside of the size of the MeshPart. ParticleEmitters inside of this part only appear within the size of the MeshPart as well.
I assumed that this was possibly the result of a change to the Roblox client, as this error had suddenly appeared in servers that were days old as well.
I’ve been told that the behavior causing this issue has been reverted/fixed - try rejoining your places in Studio to see if the meshes are correct, now.
I’ve done this myself and the meshes were fixed, so I imagine the case is the same for players in our experiences. Have them rejoin, too.