FPS Drop In Viewport When an Editor Window Is Visable

This seems to be a issue newer Nvidia drivers have brought in, and seems to affect all editor versions, now if you have the editor open then open a window, it can be a blueprint or material editor window, the viewports FPS will drop from 120fps to 70-80fps even lower depending on your GPU it seems.

Hello,

Could you send me your full dxdiag information. If you are unsure how to get this just type in “dxdiag” into your windows search bar. Once the DirectX Diagnostic Tool window opens hit the “Save All Infomation…” button and just post that text file. In the meantime you could try rolling back your drivers and see if you are still having this issue.

Thank you.

Hi Jeff, Yeah i will probably roll back until this issue is fixed.thanks

DxDiag

Hello,

Whenever Nvidia releases their next full driver update could you respond here and let me know if you are still having this issue. That would be a great help, thanks.

Hi Jeff, yep sure thing.

No change with 388.31 WHQL FPS drop still remains.

After looking through our internal documentation regarding approved drivers for NVIDIA GPUs I found that the approved driver for the engine is Version 388.00 which was released on 10/23/2017. Any newer driver than that one is not supported for use with the engine. Unfortunately this means that if you are using a driver that is not the one stated above there really is not much I can do for you. The process to which newer drivers are tested and added to the list of approved drivers happens fairly regularly so that should be updated soon. I apologize for any inconvenience this may cause.

388.00 has the issue even 384.76 has the same problem, ill have to test back even more to be sure.

At this point what have you tried outside of drivers? Have you tried completely uninstalling the engine and then reinstalling it?

I am unable to reproduce this issue on my end. When opening a project and then navigating to other editor windows I have no issues with framerate.

When I click out of the editor completely into a separate window say the desktop or a web browser the framerate will drop. This is intended however as it puts less strain on the machine since the editor is no longer the active window.

I hope this helps.

This seems to happen with all the engine versions i have installed, UE4 Editor FPS Drop - YouTube the drop seems to very depending on whats open, the drops not there when looking at datatables or enums, minimizing the window also brings back the FPS as well. thanks

Hello,

I needed to reply to this, it’s an extreme fps drop he have and i have the same issue, allthough mine drops even lower…
I’ve created a new blank project just for testing and showing purpose with starter content only in it and in viewport at startup it shows 120+ capped fps which is great.
As soon as i open a window as stated above, mine actually drops from 120+ down to 30 fps!
(I have “use less cpu in background” unchecked too, but wether checked or unchecked doesn’t make any difference in this case).
In another project with a little more scripting done in blueprint it drops down to 16 fps…
This happens to me also in different engine versions and it’s the same issue in everyone.
It’s probably something with the drivers as you say and you’re probably working with this allready.
I just needed to tell you that it drops three times as much for me and it could be good to have along the bug report.
I have a GTX 1080TI as gpu so that’s quite a huge drop for that powerful card…

I’ve attached 2 screenshots of the drop.

Thanks for looking into this!

Best Regards!

Hi ,

As stated above this is a known issue with Blueprints and a ticket for it has already been created.
Feel free to check the link above to follow the status of the ticket.

Thank you.

That says it happens with two monitors, when the drop happens if two windows are open monitor doesn’t mater as my video shows.

Yes that ticket does state that it is for two monitors but the issue as you have seen is prevalent regardless of a dual monitor setup or not. This is known and has been classified as a Blueprint issue. It seems to be tied in with the amount of nodes in the Blueprint, so more nodes cause a more significant drop in FPS.

Sadly this isn’t our issue i always disable the overlay as it interferes with Photoshops keybinds.

This issue seems to be related to how complex your project is has in a empty project the issues hardly there.

I just experienced this issue after updating my Nvidia drivers. After rolling back, going further back to the recommended drivers, then forward again - no solution.

Turns out it was the GE Force Experience share overlay. I must have turned it off previously, and updating that crappy piece of software reset it to ON. I turned off the share overlay completely - and the problem is solved. back to 120 fps regardless of how many windows I have open, or which monitor they are on.

Hope that helps.

I just experienced this issue after updating my Nvidia drivers. After rolling back, going further back to the recommended drivers, then forward again - no solution.

Turns out it was the GE Force Experience share overlay. I must have turned it off previously, and updating that crappy piece of software reset it to ON. I turned off the share overlay completely - and the problem is solved. back to 120 fps regardless of how many windows I have open, or which monitor they are on.

Hope that helps.

Hello,

After looking at the video that you have posted it seems that the project you are working in is rather large. When it comes to working with Blueprints that have a large amount of nodes in them it is actually expected that you would get some drops to FPS in the viewport. The Blueprint editor is rather resource intensive in its own way so when you combine that with a large project some frame drops are expected. However an extreme drop in FPS is not intended and there is a current bug report out on that currently. You can check that one out here. UE-37659

I hope this helps to shed some light on this for you.

Jeff after some more testing i have some more info on this issue, it seems to have nothing to do with blueprint nodes, please watch this short video, the issue seems to be map related. - YouTube

Wow…
That actually solved my problem…
I’ve also turned it off usually, but as you said it maybe sometimes actually turn it ON in an update (probably if it includes updates for features in “share”).

In my bigger project i got 16 fps in, i now get around 90 - 100, so sure it’s a drop of like 20-30 fps still, but when testing with only starter project (same as my pictures above) i get the exact same drop, so from that i’m guessing it actually is becouse i have two windows opened when i’m checking the fps drop, and now acts as it “should” do.

I won’t myself state this a “correct” anwser, just couse OverRated_AU still has his issue unresolved, but for anyone else checking into to this thread, be sure so doublecheck your “share” as Alwaysusa stated, it may have been turned ON without you knowing to.

Also OverRated_AU, i know you said you’ve always turned it off so you probably have, but just double check. In my case, it isn’t called “share” in my native language but more similar translated it’s actually called “in game overlay”.
Hope it will solve your issue aswell!

And also thanks alot Alwaysusa!

Best regards