*URGENT* Recent Studio/Roblox Update has Broken our Game

Hi all, my game primarily uses custom R15 rigs for our “morph” system – essentially cosmetic bodies that players can get into on their own

Prior to yesterday - we have had no issues with our morphs, latency, or network compatibility of the morphs. However, whatever update happened yesterday (November 14th) has changed that fundamentally - or broken it at it’s core


To describe the issue, it’s almost like there is some sort of network disconnect between the morphs and the client. Some individuals with better connection to the server seem to not experience it, and no player sees the issue happening to themselves

The bodies and heads seem to be entirely out of sync, as if the player’s body is lagging behind. This has NEVER been an issue prior to yesterday, and no code changes were made to the morphs at all. Once some sort of Roblox update went out this started happening, and we never pushed any new code changes to the live game


Videos of what’s happening, as a reminder, we have pushed NO changes to the game – this has happened to a version published a week ago. Restarting the server does NOT fix the issue

In all 3 of the above screen caps, you will see the heads are not lagging in any capacity – and seem to be true to where the player is meant to be. It is the body that is lagging behind

Once again, to emphasize, we have made NO updates to the game – the current version of the game was published a week ago, and this did not happen prior or at any stage of development. It ONLY started occurring on November 14th


Expected behavior

I anticipate when a humanoid/player is placed into an R15 compatible body, that the body and head/humanoid are in sync. This was perfectly fine prior to whatever update happened on November 14th

Everything was working correctly prior to November 14th, and no update to the game has gone out in over a week - so no code changes happened yesterday

Restarting the game/server does not fix it

4 Likes

What place is this? If you could send a rbxl that reproduces the issue, that would help us investigate. You can send a direct message

Closing this out, as we have not received information from the Creator with ways to reproduce.