Frame Time significantly exceeds the weight of other values such as Game, Draw RHIT, GPUTime

Frame Time significantly exceeds the weight of other values, such as Game, Draw RHIT, GPUTime. This occurs if you remove the frame lock from 60 fps and assign it, for example, to 144 (It is stable when locked on 60fps). In this case, every 0.5 - 2 seconds there is a huge drop in fps (from 100 to 20). Also, the problem worsens if you increase the resolution scale.

Unreal Engine 5.4.4. And it is happening in the built game (not in editor, can be shipped for development or shipping).

1 Like

Frame time is the total, so it’s always going to be greater:

Which one of the other values is jumping at the same time? It looks like Draw.

You might have some luck if you take a look at insights

My question is not about why frame time is larger than other things. It is more like why is it stable at limited 60fps but it turns into a mess when it is limited for example at 120.

1 Like

If you lock ( or smooth ) the framerate, and the target is achievable for the GPU, the total frame time will be pretty consistent. That’s what you’re asking for.

If the target is too high, I assume it behaves like its unlocked, which could expose spikes. And that could very easily be different between editor and packaged game.

Finding out what’s causing the spikes is not a bad idea, but then you need insights again.


I made a profiling. Here is how it looks - frames drop to 8 fps.


As I see CullPipe takes too much time for some reason (probably it is because of distance culling on the scene but I don’t understand why everthing is stable at 60 fps)

Here is a file if you want to explore it yourself.

1 Like

I see a lot of Oodle stuff going on here ( texture encoding ).

Are you using the latest engine? I recall there was an issue ( recently ) where Oodle had some sort of cache handling bug. It caused spikes like this.

You can try upgrading ( if need be ), or turn off Oodle ( plugins ).

Otherwise, I’d recommend this, particularly the asset tagging which help you find the culprit

Solved. I updated the project from 5.4.4 to 5.5.4

1 Like

I had that exact problem :rofl:

1 Like