Massive Performance Drop on 4.10.3 Update

Just updated from 4.10.2 to 4.10.3 and I am getting super lag when playing in editor and I had none before. Using an i7 6700K and gtx 980, so I really shouldn’t be having performance problems at all. Anyone else getting this?

I’m suddenly getting crashes whenever opening new levels…and a lot of my previously fine blueprints no longer work as intended. Not really sure what’s going on since it shouldn’t have changed this much.

The kind of thing I’d expect from going up a full version or two.

**EDIT: ** Just noticed the Answerhub post with many suers unable to switch levels since the hotfix (issue I’m having)

What I am noticing is when I start playing my disk usage starts shooting up from UE, then System and Compressed Memory starts shooting up in disk usage until it is at 99%. I tried to hop to 4.11 but I am getting the same issue with preview 5, which I hadn’t tried before now.

Ok. I definitely have a lot of weirdness when running UE now. My disk usage climbs to 99% but the actual speed only totals around 3MB/s

Oh dang, other people are having the switch-levels crash? I updated to 4.10.3 today and had that problem, but thought it was just because of my project and something weird going on.

Now I don’t feel bad at all for staying on 4.10.2 :smiley:

I figured out what it is. Procedural mesh components have taken an ASTRONOMICAL sized performance hit. I was making a total of 12 tris in my tick and even that low of a poly count was too much. Please fix asap, Epic.

Hi everyone,

If you were experiencing the switch levels crash, the 4.10.4 hotfix was released today with the fix for it. What was occurring was an error with console commands that caused the editor to crash when attempting to switch levels during PIE. Please let me know if the fix does not address your error. For , it would be best to post this information to the answerhub in the bug reports section (link in signature) so we can better assist you. Please include in your bug report the specific steps you are taking to reproduce this on your end, whether this occurs in a clean project or is limited to one project, and what error in specific you are seeing when it occurs.

Cheers for the update