Massive performance drop after updating to 4.14
Hello! I updated to UE 4.14 from 4.13.2 today and was playing through my current project testing if everything transferred correctly. As I was playing I noticed some serious framerate drops. Enough to make me stop and investigate. I did a comparison between versions and the discrepency is clear, in some areas I'm losing up to 50% performance.
I ran the particles demo in both versions as well. While the discrepency isn't as drastic, it's still certainly there.
There isn't anything in the scene that should cost too much other than a planar reflection actor. The hit is the same with or without it. I've tried multiple other scenes from my library, there is always a performance drop. Bear in mind I changed nothing between versions, the scenes are exactly the same. I figure maybe I'm missing something that was added that I don't need turned on.
The scenes are blueprint based, I get the loss in both the editor and standalone.
My specs are as follows:
Geforce GTX 970 AMD FX 8320 @ 3.7~ Ghz
Is anybody else hitting performance issues with UE4.14? Any help on the matter will be greatly appreciated.
There is a minor bug in 4.14 about material compiler failing to re-use duplicate material networks and calculate them several times. It is likely to be responsible for most of performance regression. It is due to be fixed in 14.1 and for those of you, who can compile the engine themselves, the fix is posted here.
answered Nov 19 '16 at 12:11 AM
I noticed myself that InstancedStaticMeshActors that are using a masked material seem to blend regardless of making and cause overdraw even in the opaque areas. I can't say for sure this started with the new version but I am seeing it on 4.14, perhaps this could be part of the issue? You can visualize the overdraw in your scene with the Quad Overdraw view mode in Optimizations.
answered Nov 17 '16 at 08:57 PM
As others have stated, there is an ongoing bug when compiling materials causing the engine issues.
I personally have had to resort to previous versions until the Github community sorts it out.
Until then, I'd recommend 4.13 or even a version before that.
answered Nov 19 '16 at 04:32 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here