UE4 User Interface Unresponsive. Dropdown windows for File, Settings, ect do not work, new node window in blueprint node editor does not open
Windows 10, Intel i5-4670 processor, 8G-ram, NVIDIA GeForce GTX 1050 Ti
I have recently updated Windows 10 (or I should say, Windows irritatingly updated itself) and my NVIDA Graphics card drivers. After attempting to open my project in UE4 4.13 I noticed that none of the UI windows are functioning properly (See Fig 1). Also, when using the blueprint editor the new node window does not open up, or when it does the options are unresponsive when clicked on, and the search field is unresponsive (See fig 2).
When a new project is started in version 4.15 the windows work properly, however when i attempt to migrate my 4.13 project to 4.15 it crashes on startup.
When creating a blank project in 4.13 these issues persist. Both the UI window opening issue and the node creation issue occur in a blank 4.13 project file.
This has put quite a damper on my game progress, since Unreal's user interface is unusable in version 4.13 and my assets will not migrate to a 4.15 project without the project crashing on startup.
I have tried the workaround listed here with no luck:
From this forum post concerning the same issue: https://answers.unrealengine.com/questions/483838/editor-right-clickdrop-down-menu-invisible.html#answer-484658
Any suggestions would be greatly appreciated, please help!
asked Apr 24 '17 at 05:17 AM in Using UE4
I've moved the question out of bug reports since this isn't a bug report, rather asking for help with an older version of the engine.
As you've mentioned and as noted in the other post, there are some available workarounds but in the event that they are not able to help, upgrading your engine version is the only option. Instead of focusing on fixing this issue in 4.13, it would be best to focus on why your project is crashing when upgraded to a new version.
Have you tried upgrading to 4.14 instead of going directly from 4.13 to 4.15? Attempting to upgrade across multiple versions at once is much more prone to issues such as this.
As for the crash itself, can you provide the callstack? If you're getting a message mentioning that you don't have the debug symbols installed, just posting your LoginID and/or EpicAccountID that show in the crash reporter window would help, as long as you're sending your crash reports.
There is also the option of taking the commit that this fix was made in which you can find here:
If you get a 404, please ensure that you are logged into Github and your account is linked to your Epic Games account. I can't guarantee that this will work as it may rely on other changes/fixes but it could be worth a shot.
answered Apr 25 '17 at 05:06 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here