Event Tick FPS Drops and Framerate-Independent Timers and Movement in UE5 Blueprints

Table of Contents

Works in Unreal Engine 5.0 to 5.8. Updated November 2026.

Quick answer:

  1. Anything you change every frame, multiply by Delta Seconds from Event Tick (or Get World Delta Seconds). Speeds become “per second” instead of “per frame”.
  2. Logic that doesn’t need every frame (distance checks, regen, AI decisions) goes on a looping Set Timer by Event instead of Tick.
  3. Turn Tick off, or slow it down, on actors that don’t need it.
  4. Type stat unit in the console to see whether the game logic or the rendering is slow.

Why it runs faster in the packaged game

Event Tick runs once per frame. If you move something 5 units per Tick, it moves 300 units a second at 60 FPS and 600 at 120 FPS. A packaged build often runs at a higher framerate than the editor, so everything speeds up.

Delta Seconds is the time the last frame took. Multiply by it and the speed is the same at any FPS:

  1. Make a float variable Speed in units per second, for example 300.
  2. On Event Tick, multiply Speed by Delta Seconds.
  3. Use the result in Add Actor World Offset (as a vector, for example in X).

Interpolation nodes work the same way. Plug Delta Seconds into the Delta Time pin of FInterp To or VInterp To.

Characters already handle this. Add Movement Input goes through the Character Movement component, which uses delta time for you. Don’t multiply it by Delta Seconds.

To test, type t.MaxFPS 30 in the console, then t.MaxFPS 144. Your game should behave the same at both.

Timers or Tick?

Tick isn’t bad. What runs on it is what costs time. Use each for what it’s good at:

UseFor
Event Tick × Delta SecondsSmooth movement, rotation, camera, anything visual every frame
Looping Set Timer by EventThings that happen every X seconds: checks, regen, spawning
Events (overlap, hit, dispatchers)Anything that only matters when something changes

Timers run on frame boundaries, so they aren’t millisecond-exact. A looping timer that falls behind runs several times in one frame to catch up, so it keeps the right count per second. That makes a fast timer a poor way to move things smoothly; use Tick with Delta Seconds for that.

Avoid Delay in loops for timing. Use a timer you can clear with Clear and Invalidate Timer by Handle.

Turn off Tick you don’t need

  • In the actor’s Class Defaults, untick Start with Tick Enabled, then turn it on only when needed with Set Actor Tick Enabled, for example when the player comes near.
  • Or set Tick Interval (secs) to 0.1 or 0.2 so it ticks a few times a second. Delta Seconds still gives the right time between ticks.

FPS drops after a few minutes? Find the cause

Framerate that falls over time usually means something is piling up. Check these while playing:

  1. stat fps shows the framerate. stat unit shows the time per frame for Game (your logic), Draw and GPU. If Game is the highest, look at Blueprints.
  2. Watch the actor count at the bottom of the Outliner. If it keeps rising, something spawns actors and never destroys them.
  3. Look for Create Widget, Spawn Actor, Bind Event or Set Timer running from Tick. They should run once, not every frame.
  4. dumpticks lists every ticking function in the Output Log, so you can spot actors that shouldn’t tick.

For a deeper look, record a trace and open it in Unreal Insights.

FAQ

Is Event Tick slow in Blueprints?

Blueprint logic runs slower than C++, but a little work on Tick is fine. Heavy loops on many actors every frame is what hurts.

My timer is set to 0.01 seconds. Is that faster than Tick?

No. Timers are checked once per frame, so a 0.01 second timer can’t run more smoothly than Tick.

Related articles