This bug also happens eventually during every solo play test I do.
I do not know the trigger, but it seems to often happen when loading MeshParts, although it also happens seemingly at random. The MeshPart still successfully loads, and sometimes the same MeshPart does not cause the error on a different play test. This started about 2 weeks ago and originally was rare. It also happens on local server tests.
My play tests are now limited to 20-120 seconds because of this, requiring the play test to be restarted, greatly limiting development. It does not crash the test, but it causes things to stop working and the player to freeze, as if the connection was lost. It has not happened yet on a live server.
This occurs on different computers and in different games of mine that were previously fine on studio. I have re-installed studio and tested different connections.
Yep, this is happening to me now too. This started occuring after i enabled new beta features (specifically some of the new keybind controllers, ui styling, and sky rotating) and when I went to incorporate the rotating sky, I started getting this error. I thought it was because of the sky, but for some reason after a couple days it started popping up again even without the sky.
I would like to bump this topic as playtesting in studio in one of my projects has become completely unusable. I have to press play possibly 3 times in a row just to get it to work.
