In the editor if I click on standard “win32”-type menus (such as those on the main toolbar) they do not appear. My best guess is that they are rendering behind the main screen.
If I move the editor window they pop on top (but sub-menus still are not visible when they are opened)
If a menu opens below the window, such as “View Options” does sometimes it will be visible.
If I use the search function (typing when the menu is open) the menu becomes visible.
Drop downs in the Details pane, for example, do open; but the drop down in the main window by view modes is not visible.
Additionally, the menus in the launcher (e.g., profile, settings, etc) are not visible. The drop down for the Launch button in the installed engine version area does work.
There was a similar, resolved post about this, but the link to the solution redirects to a page-not-found.
I am using the most current version of the editor/launcher; Windows 10 (another computer with the same OS version does not have this problem); current Radeon drivers; a machine that easily meets the recommended specs for the engine. This is the first time I have used UE on this system and I have never had this problem on my last system that used the same graphics card and OS.
This issue has been reported a few times and is usually related to graphic cards settings. Are you using a laptop? If so, the fix posted here may be able to help you
Otherwise, does your computer also have an integrated graphics card that you’re using? If so, that previous post may still be able to help but you should try to ensure that the correct graphics adapter is being used.
I have a Radeon R9 280 on a desktop. There are integrated graphics via the i7 processor, but it is disabled in the BIOS and, indeed, does not show up in the device manager.
I did search for this problem but I didn’t see any thing that helped.
I’m going to try to see if I can ge this to reproduce on our end. Would it be possible for you to upload a copy of you dxdiag information so that I can try to get the setup as close as possible? Partially because I also need to know the Windows 10 version that you’re on and need to match your graphics drivers.
I am running the newest Windows 10 Insider build (14915.1000) and the newest Radeon drivers (16.9.1)
The problem was happening before either of these versions. Additionally, it is not a problem on my other machine that is also running the current Window 10 version.
I have had suspicions that it might be related to Windows 10, however it is not ubiquitous because I have another computer on the same version that does not have this problem.
Regardless, this is a problem that I have seen in no other application or game (old or new) and should be considered a bug with the Unreal launcher and editor in my opinion.
As Angel has pointed out, there are a few users who are saying that this issue is tied directly to the latest preview builds of Windows 10 and that report can be found at this link. I’m currently waiting to get my hands on a drive with Windows 10 Pro so I can try this myself. If you think this may be the same issue, it would be best if we kept all of the information in one place and referred to that post for further discussion. If not, please let me know and we can try to nail down a repro here.
I am aware of, have been directed to, and have already posted in the other page.
I know that it was caused by the Windows update, I was just saying that in my opinion, since it seems to be exclusive to UE, despite a change in Windows causing it to not work properly, it should be considered a problem with UE.
A big thanks for your continued support on this issue.
I’ve already posted in the other page, but I figured I’d post here too so we can resolve this issue. I’ve entered a bug report for the issue as I finally was able to get a hold of the correct environment and reproduce the issue. You can find that report here: UE-36752
I experience this problem on 4.12 , after Windows update (KB2538243) , (KB2993928) , (KB4017094) and (KB4020821)
But the (KB2538243) is for Visual C++, so I thinki it had something to do with that.
had to add -opengl in the new shorcut added to desktop. And after that the problem went away