My system is windows10 14915, graphic card is gtx760 with latest NVidia 372.70 driver, product version is 4.13 .
The right click/drop down menu often invisible in editor, both in viewport and content browser. Sometimes they show up with delay, also delay when mouse cursor hover or sweep over the menu content. Right click menu in blueprint event graph almost never show.
Tooltips will show when mouse above the invisible menu.
I have verified engine files, also add -opengl suffix to launch both launcher and project, but not work.
Hello Dolomo,
I was unable to reproduce your issue while testing on my end. My steps were:
Open a blank 4.13 project
Right click in content browser and check if menu pops up
Right click in Viewport and check if menu pops up
I just want to verify that I understand your issue.
When you right click an asset in the content browser after opening a 4.13 project the menu will not appear?
Are you experiencing this problem in only 4.13 or have you encountered this on earlier versions of the engine as well?
When right click an asset in the content browser, right click in viewport, click the dropdown menu above the viewport like play button, the menu sometimes appear, sometimes not.
When right click in blueprint event graph, the menu barely appear.
This problem not only in 4.13, but also in 4.12.5.
This happens after updating my windows10 version to 14915.
I’m currently attempting to get the Windows Preview build you’re both mentioning to see if I can reproduce this issue. When getting your preview builds, are you getting them from the “rs1_release” or “RS_PRERELEASE” branch? This can be found under Start > Settings > Updates and Security > Advanced Options.
Do you see something different? Are you getting your insider build directly from Windows Update or elsewhere? I’m not familiar with using the Windows Insider Preview program but this seems like the only method to update to me.
Edit: th2-release mentions that it is not set up for the preview builds so I neglected to mention that one.
Ah, that would explain the difference. Version 1607 is the Anniversary edition update. This isn’t available for the version I was using as it’s Enterprise. I’ll need to get a hold of a Pro version and get back to you.
By my opinion, there is no major difference in these version. Put any version or insider preview > 10.14393 and the BUG will rise. There is something base which disable main part of graphic UI as drop-down controls (File menu, Toolbar down arrows, viewport down arrows, etc.)
Insider Preview f…d us all and so bad …
This is huge BUG and I am wonder how it is not well known yet?!?!?!
I will remove Insider Preview and clean install of Win 8.1 or Win 10.14393 these days
Ya, well, I was thinking of doing the same myself, but unfortunately, I’m not ready to do a clean sweep and reinstall everything right now. So for the moment, I’m stalled.
Unfortunately, all of the editions of Windows currently available to me are Enterprise or are on Pro and not available to be updated. With the current ones I have, I’ve not been able to see the issue. I’m in the process of getting a Pro edition that I can freely update so that I can work on reproducing this, but in the meantime I would suggest rolling back.
As we mention with our preview builds of the engine, I would assume the same goes for Windows versions even more so due to the intricacy of the software, there should always be expected errors and blockers in pre-release software. We also don’t actively test on pre-release versions of other software than our own so we wouldn’t of come across this yet.
for trying. I realize that we take risks with this stuff. In my case, I just forgot to jump off once the Anniversary edition landed. It’s worth noting that this doesn’t just show up in the editor, the Epic Games Launcher has some drop-downs that do the same thing. I’ve reported the issue to Microsoft, so hopefully it’s something they have noticed and can fix.
Please be aware that this is Window’s preview build and not ours. As such, this isn’t something that we’ve run into as we do not test on their preview builds. I’ll be taking a look but can’t really go any faster than I already am.
Matthew, I have feeling that this bug will be present in the next final Windows 10 release. Why? Because why such enormous and obvious UI bug is available (but not fixed) in present insider preview?
