Layered clothing gets de-sync'd from avatar rig when in ragdoll state

Reproduction Steps
Currently, layered clothing has an extremely noticeable visual glitch that occurs when the player’s avatar enters a ragdoll state via physics constraints. When the player ragdolls, the layered clothing ‘explodes’ and gets completely desync’d from their avatar. Since layered clothing’s wrap is only computed once, this issue does not resolve itself until layered clothing is added/removed from their avatar. Attempting to force a recompute by quickly toggling the Puffiness properties only worsens the desync.
This issue only seems to occur after the player’s avatar is respawned with Player:LoadCharacter(). The player’s ‘first’ avatar does not have this issue.

Steps to reproduce:

  1. In the file I attached below, press the R key to ragdoll. Notice that the clothing remains in-sync with the avatar.
  2. Press the R key to unragdoll. Again, note that the clothing is still in-sync.
  3. Reset / kill the avatar. Wait for respawn to occur.
  4. Press the R key to ragdoll when the character respawns. Notice that the clothing is now desync’d from the rig.
  5. Press the R key to un-ragdoll. Notice that the clothing is still desync’d sometimes, and it just gets worse.

LC_Desync_Repro.rbxl (204.6 KB)

Expected Behavior
It is expected that layered clothing remain in-sync with the player’s avatar at all times, regardless of what the avatar is doing (emoting, ragdolling, swimming, etc).

Actual Behavior
Layered clothing gets desync’d from the player’s avatar in some cases (ragdolling, procedural animations such as footplanting, IK ‘headlook’, etc)

The workaround to this issue is to quickly add and remove a piece of layered clothing, which forces a recompute for the wraps of all of the clothing that is applied to the player’s avatar.

Issue Area: Engine
Issue Type: Other
Impact: Moderate
Frequency: Constantly
Date First Experienced: 2021-10-27 00:10:00 (-04:00)


Does this issue still occur for you ?

Yes, it still happens, I just tested it in the repro file I included in this bug report.

We’ve filed a ticket to our internal database and we’ll follow up when we have an update for you.