Sequencer.AllowPausedClock makes Audio/Platform-clock sequences evaluate at a negative time after any earlier game pause

5.8 added Sequencer.AllowPausedClock (on by default) in FMovieSceneTimeController_ExternalClock::OnRequestCurrentTime (MovieSceneTimeController.cpp). It computes PausedTime = World->RealTimeSeconds - World->AudioTimeSeconds and subtracts it from the elapsed clock time.

RealTimeSeconds - AudioTimeSeconds is the total time the world has been paused since it started, not since playback started. If the world was paused at any point before Play(), the first ticks return a time before the start frame.

ShouldStopOrLoop only checks the upper bound in forward playback, so the player evaluates at that negative time. Everything active at frame 0 is unlinked right after being linked. For example, IMovieSceneEvaluationHook::End fires one frame after Begin. The sequence then holds before its start until the elapsed time catches up with the total paused time. This affects the Audio, Platform and RelativeTimecode clocks.

Workaround: Sequencer.AllowPausedClock 0. This restores 5.7 behavior, but external-clock sequences then jump ahead by the pause duration when the game resumes.

Suggested fix: record the world’s paused total in ExternalClock::OnStartPlaying and subtract only the change since then. We apply this locally by offsetting ClockStartTime in OnStartPlaying.

Related issues in the same code

  • It reads the first PIE/Game world context instead of the player’s world, because built-in clocks are created without a context. As a result, Sequencer editor playback freezes while a PIE session is paused, and with several PIE clients every client uses the first client’s pause.
  • It ignores bTickWhenPaused. The tick manager keeps ticking those players during a pause, but the subtraction freezes their time anyway.

Could you confirm whether a fix is planned, and in which version?

[Attachment Removed]

Steps to repro:

  1. Create a Level Sequence with Clock Source = Audio (or Platform) and a section starting at frame 0.
  2. In PIE, pause the game for a few seconds (SetGamePaused true), then unpause.
  3. Call Play() on the sequence.
  4. With “log LogMovieScene VeryVerbose”, the “Sequence Offset Seconds” value in the TimeController log is negative, and the frame-0 section is torn down immediately.
    [Attachment Removed]

Hey there,

Thanks for raising this, I’ve logged an issue that you can follow:

https://issues.unrealengine.com/issue/UE-403947

What you’re suggesting seems reasonable. I would keep it if it’s helping you and follow the issue for a fix.

Dustin

[Attachment Removed]