iClone Live Link to UE5 Chaos Cloth Issue: Ballooning Lehenga, Degenerate Triangle Error, and Render Crash

Hi everyone,

I am facing a severe issue when bringing a Character Creator 5 / iClone character into Unreal Engine 5 using the Live Link plugin. The cloth in question is an official dress asset purchased directly from the Reallusion Content Store, but it is causing multiple issues in UE5.

Here is a breakdown of the problems:

  1. Ballooning / Inflated Dress Physics: Upon loading into UE5, the bottom portion of the lehenga/dress inflates into a large spherical shape.
  2. Degenerate Triangle Error on Live Link: Whenever the character is transferred via Live Link, UE5 displays the notification: Failed to generate clothing sim mesh due to degenerate triangle, found coincident vertices in triangle.
  3. Bone Structure Distortion on Modifying Collision Capsules: When I attempt to resize or adjust the collision capsules in the character’s Physics Asset to prevent the dress from inflating, the entire bone/skeleton structure becomes completely distorted or deformed during Sequencer rendering.
  4. Crash During Render: Even after baking the animations and sending them via Live Link, rendering the scene in Sequencer / Movie Render Queue causes an instant system/GPU crash due to the Chaos Cloth simulation.

What I have tried so far:

  • Baked animation before sending through Live Link.
  • Tried scaling down physics capsules (which distorts the skeleton structure).
  • Tried adjusting cloth parameters, but simulation calculation still overloads and crashes UE5 during rendering.

Has anyone encountered this issue with official Reallusion dresses or Live Link Chaos Cloth binding? Is there a specific workflow to clean up the degenerate triangles or safely adjust the Physics Asset without breaking the bone hierarchy?

Any advice or workarounds would be greatly appreciated!

Hi prs20091303,

Here is a tutorial for cloth physics which may help you in transferring your content.
Also, would you be able to let us know which content did you used for us to replicate your issue in our part.

Thanks