How Do I Fix the Lag on Timeline "Finished"?

I built a simple camera transition from third-person to first-person and back again. This transition takes place over two seconds, and my keyframes in the transition timeline are on 0.00/0.00 and 2.00/1.00. The timeline itself is set to 2.00 seconds. Yet, there’s a lag when the timeline finishes. I have an event that fires off the “Finished” pin, but it always takes a second.

Has anyone run into this?

And, if so, how do you fix it?

If anyone can shed some light on this, that’d be very helpful.

Dammit!

Setting the position of the cameras from the tick increases the speed of the lerp transition, putting it ahead of the timeline completion. Luckily for me, players in my game can only transition from third-person to first-person when standing in a certain location. There’s no need to transition on the fly, so I set the world location for my camera variables on interaction instead of the tick, and that seemed to do the trick.

However, what if I did want my camera to transition from third-person to first-person on the fly. How would I get around the problem of the lag off the “Finished” pin?

If you use a smooth curve, there does seem to be a bit of a lag before the finished pin fires. Solution is just to add an event on the timeline about .5 secs before the end and use that pin instead.

Reviving thread for some solutions:

  1. You probably didn’t set the length of the timeline.
    Either you need to set the length to your last key that you want the timeline to end on or set “Use last keyframe” to true in timeline (the button right next to the length), so it would do it regardless of the length.
  • As explained here.
  1. You’re probably trying to lerp current location to new location.
    What you need to do instead is use a static variable for the current location, basically save the location in a variable and then lerp it to the desired location.
1 Like

My low level understanding of TL’s is they fire once a local frame and the finished execution happens on the following frame.

Essentially it checks each frame if the current alpha is equal to the end value (1.0). If not process an update. If so fire Finished.

Sooo… Pull off the “Alpha” pin and check the value every update. If == 1, fire your event.

You’re talking about firing and event on finished(might as well use a delay node), OP needed to change a value over time.