UE5.6.1 Sequencer Animation – Facial Curve Values Persist Between Plays

Hello,

After upgrading a project from Unreal Engine 5.5 to 5.6.1, I’ve encountered unexpected behavior in Sequencer animations involving facial curves.

Issue:

  • When playing a Level Sequence with a skeletal mesh animation that has facial animation driven by curves (morph targets), the actor briefly shows an incorrect expression at the very beginning of playback.

  • This “flash” of the wrong expression appears to be caused by curve values from the previously played animation persisting into the new sequence.

  • After a single frame, the correct expression from the current animation is applied.

Additional notes:

  • The animation assets already have 0 keys set at frame 0 for the facial curves.

  • It seems that the Sequencer evaluates the previous animation’s curve state before applying the new one, which did not occur in 5.5.

  • The issue happens consistently on multiple characters/assets after updating to 5.6.1.

Question:

  • Is this a known bug or intentional change in UE5.6’s Sequencer evaluation?

  • Are there recommended settings or fixes to prevent previous curve values from bleeding into the next sequence (without having to add function tracks to clear morph targets as a workaround)?

Thank you for any clarification.

This behavior occurs when running the game in the editor, but it does not occur in a packaged build. So fortunately it does not cause issues in the final product.

I just wanted to share this information. If there are no replies after a while, I will go ahead and close the thread.

I believe this is the same issue.
When placing a skeletal mesh with morph targets in the editor, the morph values are not applied and the mesh is displayed incorrectly.
In PIE, it may appear to work correctly, and the same goes for Shipping builds — however, the problem still occurs internally.
If the skeletal mesh has LODs enabled, the morphs are not applied for the first frame when an LOD switches, causing a brief flicker.
This issue also occurs frequently in Shipping builds, making it a particularly troublesome problem.
It can be reproduced in the Content Examples project.
It did not occur in version 5.5, but the same bug can be observed in 5.7 Preview.
I’ve already reported it, but since no bug ticket has been created yet, it’s unclear whether it will be addressed.

1 Like