Tickrate has dropped significantly in 41.00

Summary

Ever since the 41.00 update came out, my map that ran at a solid 30tps now runs at around 15-20tps.
I haven’t changed anything, so I can only blame this newest update.
The image below is a before and after.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Stability

Steps to Reproduce

Update to 41.00.

Expected Result

A solid 30tps.

Observed Result

An unstable 15-20tps.

Platform(s)

Desktop.

Upload an image

image_2026-06-06_203445888.png

Additional Notes

If you too have noticed a significant tick drop, do me a favor and upvote this thread and comment down below. Thank you.

I have found this too, some people have it, some don’t.

I noticed this as well, overall performance seemed to have worsened but it is especially noticeable when spawning and disposing props with verse.

same here

I noticed this as well after 41.00, I was getting around 100 fps by the ingame counter but it was still extremely choppy. I changed my desktop resolution from 1920x1080 to 4096x2160 and it fixed it, it’s smooth as butter again. I decreased my resolution to take advantage of upscaling in another game but I couldn’t take the choppiness of fortnite while testing my map, so I went back to 4k. Might be something with upscaling, I’m on AMD CPU/GPU just for clarity.

This isn’t about framerate, but rather tickrate, which is how well the server is running.

Yep I’ve noticed this badly

Hi @RiYAN :slight_smile:

Could we please get your island code so we can take a look? Thank you!

Here’s a private island code: 8732-5233-6492

1 Like

Bump. Anyone else experiencing a slow tickrate?

Yeah, I disabled all Verse devices, so there’s 0 Verse code running besides some Scene Graph code and the TPS monitor. TPS still drops to 13 every 3–4 minutes. Same behavior in private playtest islands, Live Edit sessions

I forgot to mention that every 20 seconds or so, the whole server hangs for 5 seconds, which makes it even worse.

FORT-1113833 has been ‘Backlogged’. This is an issue that is in a queue to be addressed.