Hi all. I’ve been having this weird and very annoying issue with UE5 for the last few days and haven’t been able to troubleshoot it yet. I thought one of you might have encountered something similar before, or might at least have some leads on how to try and solve it.
So, I’m developing a 3rd person RPG. I’m not developing on a high-end GPU, so many times I am struggling with performance and optimisation. A few days ago I was trying to optimise the project, and suddenly the game started feeling very slow, in a way that it didn’t feel before. Let me explain. Even when I manage to have some decent fps, in the range of 30-40fps, the character’s movement and the camera feel as if they’re in slow motion. Above 40fps it’s fine. Attaching a screenshot with some basic profiling, when this problem is already present.
In the past I used to have normal-feeling movement, even at quite lower fps, in the range 20-30fps. This issue seems to be affecting specifically things that have to do with player input (movement & camera), but I’m not sure if it’s affecting only these.
I don’t know if I have changed any setting that might have caused this, or if it has to do with my PC for some reason. Any ideas?
Does it produce a different feel once fiddled with?
There are also 4 tick groups in the engine, each actor can live in any of those groups. Their effects can be dramatic; updating the UI later may feel super laggy, for example. Updating it too early may have you work with stale data and feel even worse.
On top of that, the TL can also have its own update scheduled differently:
Hi @Everynone, you’re the best, that was it! I had ticked ‘fixed frame rate’ (because I realised that the ‘feel’ of some aspects of the game, like driving scenes, where totally different if you played at different PCs with different framerates. In the high end machines, it felt much quicker, almost high speed.
But indeed, apparently this introduced the laginess I described, I don’t really understand why. I just reset it to default and it solved it.
As a follow up, do you know what would be a good way to cap the fps without introducing this unresponsive behaviour?
Thanks again for the help
I now realise that I was confusing ‘capping’ with ‘fixing’. I wanted to cap at 50fps, but I was actually trying to fix at 50fps, which I was not reaching with my machine, and aparently it was introducing this problem.
