Issue Type: Display Impact: Very High Frequency: Constantly Date First Experienced: 2021-03-22 14:03:00 (+00:00) Date Last Experienced:
Reproduction Steps:
Simply join a game that is on a new server (we tested VIP servers) that already has players in it, then look at the characters of those players.
Expected Behavior:
Players characters should load in correctly, regardless whether or not you joined before/after them
Actual Behavior:
In new servers only, if you join a server that players are already in, you will notice that the players that were previously there’s characters look almost humanoid-less, with no clothes, etc. This does NOT apply to players who join AFTER you have joined the game, only players who were already in the game before. I’ve tried this on multiple games, and it appears to be Roblox-wide.
Frequency: Constantly Date First Experienced: 2021-03-22 / Around 11:00 AM PST
I am encountering this EXACT issue listed in the post with a group I develop for across all our games.
Our system and places where working before the issue started and weren’t updated at anytime near the start of when I started experiencing this issue.
Error found sent multiple times on the client: “exception while signaling: LoadAnimation requires the Animator object (Animator) to be a descendant of the game object”
Encountered this problem a couple of hours ago, same error code. As OP states, the bug seems to occur on existing characters. It loads properly on players that join the server after you. And can be “fixed” when the existing characters reset themselves.
Sorry about the bug! We recently reverted a change that we think may have caused this bug, and if we’re correct, this bug should no longer occur in new servers. Please let us know if the issue persists and we will investigate other potential causes!
Update: the change we think causes this bug just got activated again in a bulk revert - we’ve re-reverted the buggy change, but these changes take some time to apply, so some users may see the issue may pop up again briefly. So sorry for the inconvenience!
The change that we think caused this issue was reverted - you may still see it on old servers that are running on older settings, but new servers should not have this problem. Please let us know if you find that this issue still happens with new servers.