Hello there.
I’m using the 5.2.1 editor and it is running extremely slow and hitches hard while using spline BP’s and editing foliage and landscapes. I’ve tried turning my settings down to nothing but it still hitches really bad. Frame rate is fine otherwise. Any insight on what can be causing this will be much appreciated.
Greetings @nghia59
Is this happening on one specific project or all of them that you’ve tried? Also, can you provide your system specs for me? That’ll help going forward. I’ll be happy to look into this with you!
Here are my specs. This is the only project I have in 5.2. Both 5.1 and 5.3 work fine and for the most part my FPS is good. Its only hitching really hard on landscape and foliage painting and editing the spline BP’s.
Mostly depends on what is on the map, if that is heavy for your device to process then yes. Is it a laptop or desktop? On a laptop you will want to set your battery settings to “best performance” and plug in the power cord or you will experience lag. Does your GPU meet the requirements? Did this problem happen in older versions of UE?
I’ve got a full workstation with a 1000W power supply and an RTX3080 running on an SSD. Performance isn’t an overall issue with UE5 for me as other version run just fine. Both 5.1 and 5.3 are good for the most part and my FPS is roughly 60 when I’m not using certain tools.
Painting foliage in large volumes can be slow for me too but on a GTX 1070. Splines give me no problems on 5.2.1. Editing a spline is no heavy calculation unless it is being used for one, for example procedural generation along the spline where this might be expected to cause a slowdown.
Is your spline + foliage tool problem only present on 5.2.1 and not on 5.1 / 5.3, or is this happening on all versions?
Yeah, it works fine in 5.1 and 5.3.
The best solution might be to make a copy / backup of your project, then upgrade to 5.3 to see if everything else runs fine as well, then stay at 5.3. Downgrading a project is not supported.
Because so many things change per version it is common that a newer version fixes one thing while breaking another. Reporting a bug on an older version has little use since it works fine on 5.3. EPIC does not look back to older versions. If EPIC would release an LTS version of the engine (long term support), we could stay on the same version for much longer and request fixes for that version:
Yeah, I can’t do that because the company project is in 5.2 for various reasons.
Alright, you could try to diff the engine source code of both versions and try to find / debug what causes the issue on 5.2.1 and modify source yourself from there, but I can’t tell if you find the reason of the issue within hours or days. modifying engine source is probably more trouble than it’s worth. Another thing you can try is run 5.2.1 on another machine and see if that machine runs it without trouble. I have a spline based game project running on 5.2.1 without performance hitches in the editor. Or, maybe more people posted a similar problem online on the forums or reddit with a workaround.
I figured out the issue. Its the number of foliage instances making everything slow including the BP splines. This wasn’t an issue before in earlier versions so this is probably a bug they introduced in 5.2.
