x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[Closed] Editor right click/drop down menu invisible

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.

I need your help. Thanks.

Product Version: UE 4.13
Tags:
more ▼

asked Sep 07 '16 at 11:33 AM in Bug Reports

avatar image

Dolomo
61 2 3 5

avatar image Ed Burgess ♦♦ STAFF Sep 07 '16 at 05:40 PM

Hello Dolomo, I was unable to reproduce your issue while testing on my end. My steps were: 1. Open a blank 4.13 project 2. Right click in content browser and check if menu pops up 3. 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?

Thanks,

Ed Burgess

avatar image Dolomo Sep 08 '16 at 01:51 AM

Hello Ed Burgess.

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.

avatar image Angel Tsvetkov Sep 08 '16 at 02:26 PM

I also have this bug- no drop-down menu of File Menu, or toolbar buttons with down arrow.

Little trick to show drop down menu on File Menu: click on FIle and then press SpaceBar.

I have Windows 10.14915.1000 1607 Pro Insider Preview, UE4.12.5 and UE4.13. On the same PC, but with WIn 8.1 Pro and UE4.12.5 there are no problems

avatar image Matthew J ♦♦ STAFF Sep 08 '16 at 06:12 PM

Hello Dolomo & Angel,

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.

avatar image Angel Tsvetkov Sep 08 '16 at 07:51 PM

There is not "rs1_release" or "RS_PRERELEASE" in Start > Settings > Updates and Security > Advanced Options

avatar image Dolomo Sep 09 '16 at 01:28 AM

My Start > Settings > Updates and Security > Advanced Options is the same as Angle Tsvetkov.

But there is a version on the right bottom corner of desktop:

alt text

capture.png (49.9 kB)
avatar image Matthew J ♦♦ STAFF Sep 08 '16 at 08:03 PM

This is what I'm seeing inside of the Advanced Options:

alt text

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.

avatar image Angel Tsvetkov Sep 08 '16 at 08:24 PM

I stopped my insider preview. Before that it was on fast, then slow. alt text

alt text

avatar image Matthew J ♦♦ STAFF Sep 08 '16 at 08:45 PM

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.

avatar image Angel Tsvetkov Sep 09 '16 at 05:01 AM

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.)

avatar image GitNick Sep 12 '16 at 04:52 PM

Exact same issue here. Wish it was easier to move off of Insider Preview. Apparently I need to wait till they push another public release, then exit?

avatar image Angel Tsvetkov Sep 12 '16 at 05:25 PM

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

avatar image GitNick Sep 13 '16 at 05:10 PM

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. :(

avatar image Matthew J ♦♦ STAFF Sep 13 '16 at 05:23 PM

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.

avatar image GitNick Sep 13 '16 at 06:34 PM

Thanks 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.

avatar image GitNick Sep 13 '16 at 06:47 PM

In case they are useful, I'm adding some images illustrating the issue below.

Unreal Launcher New Project Settings

avatar image Angel Tsvetkov Sep 14 '16 at 09:22 AM

GitNick, very good job with these screenshots!

avatar image rubenst Sep 24 '16 at 12:16 AM

To me this behavior looks like some sort of render state isn't cleared properly anymore in Win10 14915+ hmm, curious

avatar image Angel Tsvetkov Sep 14 '16 at 12:31 PM

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?

avatar image Matthew J ♦♦ STAFF Sep 14 '16 at 01:00 PM

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.

avatar image GitNick Sep 14 '16 at 04:32 PM

Thanks for looking into this Matthew. Due to the nature of this bug, I know that I can't expect a resolution soon, and the better bet is for me to just do a reinstall of Windows. I've noticed at least one other application behaving the same way (non-Epic), so I'm feeling pretty sure that we are just waiting on Windows for this one.

avatar image Matthew J ♦♦ STAFF Sep 15 '16 at 07:47 PM

Hello GitNick,

That's some interesting news. I still plan to bug it if I can get it to occur, but what other software was it that you experienced this issue in if you don't mind sharing? If he is able to share it, Angel, could you give it a try as well, if you haven't already switched back, to see if you see the problem?

avatar image Rakosman Sep 15 '16 at 11:45 PM

I have experienced this bug with no other software. While it's clear that something changed with Windows in the insider preview, the fact that it's only happening in UE (for me) makes me inclined to say that it should be considered a problem with the way UE does it's menus

I've tried various other software, such as Adobe programs, FL Studio, Blender, even one's that use a more "custom" menu, rather than the tradition win32 style.

The bug is still present in Windows 14926.

Something really interesting, though, is that the update that happened to the Epic Launcher today brought back functionality to the settings and friends menu, which previously did not work. It also seems that the UE menus are more likely to work, albeit after some serious hang time. It may also be worth mentioning that certain menus do work, such as the dropdown on the "Launch" icon and the category filter in the UE marketplace in the launcher, and all the drop downs in the details and settings, and similar, panels.

I think I forgot to mention before, but the CPU usage ramps up like crazy when the menus are being used.

avatar image Angel Tsvetkov Sep 16 '16 at 10:53 AM

This BUG is confirmed and in W10.14926.1000 Pro Insider Preview 1607. All File Menu is broken + DropDown Menu not work in any window (Toolbar, Viewport, anywhere where is placed drop-down arrow)

P.S.: Definitely Microsoft changed some part of UI (which is very probably to present in the next final release) and now the ball is in Epic's court

Check avi file in zip attachement link text

avatar image DarkLichNY Sep 29 '16 at 10:38 PM

I also have this problem with 4.12 and 4.13 on w10 Dev Preview 14936.rs_prerelease.160923-1700

I have to run the editor in openGL mode in order to get any menus... I have the same issue in the launcher now, can not get any menus...

avatar image RobMilliken Oct 02 '16 at 06:08 AM

I am currently an insider and had another update last night to Build 14936.rs_prerelease.160923-1700. I have also updated to editor version 4.13.1. I am still having this issue, though there appears to be a one line fix (per the answer below by manoelneto). I did try running the editor per this last comment in openGL (I hadn't thought of that - thanks DarkLichNY!) and the menus are completely responsive now, though the project I tested this on had to recompute shaders (takes a while) and it took a while to load. So this is a good workaround if you want to keep your Win 10 insider build and remain productive. There isn't an option in the Epic launcher to start in openGL (that I could find), so it turns out you have to create a shortcut first:

Click on Launch then select Create Shortcut

Then on the new shortcut on your desktop, right click and select properties. Add the -opengl to the target AFTER the quote:

...\Binaries\Win64\UE4Editor.exe

I am hoping this gets fixed before this insider preview build becomes public to everyone. Those who aren't following this thread will certainly become upset if not. My understanding is that this is a one line fix - it shouldn't be too difficult to push it to the source, test it ASAP and be put on the next release. Otherwise, perhaps the Epic launcher should launch the openGL version of the editor (this should make all versions work, I would think) by default with a caveat to the load time the first time this is done.

shortcut.jpg (13.5 kB)
edittarget.jpg (8.2 kB)
avatar image Dakunier Oct 08 '16 at 12:29 PM

Im on the latest Insider Preview 14942 and i started the Editor with the -D3D12 parameter. All menus work just fine :)

avatar image mikedulberg Apr 20 '17 at 05:56 PM

Awesome! I just started having this issue earlier this week after a windows update. I had to migrate my project to 4.15, but not all the content went correctly... this saves me a lot of rework. Kudos

(comments are locked)
10|2000 characters needed characters left

The question has been closed Apr 20 '17 at 07:03 PM by Matthew J for the following reason:

The question is answered, right answer was accepted


5 answers: sort voted first

I was able to get updated to the following prerelease build:

Build 14936.rs_prerelease.160923-1700

I was able to reproduce the issue and have entered a bug report as a result. You can find the bug report here: UE-36752. This should let us start looking into fixing this. I included manoelneto's fix in the description so that can be taken into account but it may not be the same as the resulting fix.

more ▼

answered Oct 03 '16 at 07:30 PM

avatar image

Matthew J ♦♦ STAFF
31.8k 526 91 417

avatar image RobMilliken Oct 06 '16 at 12:06 AM

So, this bug report has, at this writing, been logged as 'cannot reproduce' and given a RESOLVED date... can you follow up, Matthew? Maybe they didn't read that it involves Windows Insider builds. Maybe in the meantime everyone can up vote the bug so it'll get more notice?

avatar image Matthew J ♦♦ STAFF Oct 06 '16 at 07:16 PM

Hello RobMilliken

I've left a comment for the person who marked it as Cannot Reproduce to ensure that they were using the correct environment when testing. Upvoting an issue is always a good thing, it'll show more community interest in the bug.

avatar image Matthew J ♦♦ STAFF Oct 10 '16 at 03:30 PM

The person reviewing it didn't notice that it was preview, as we had guessed. A fix has been entered for the issue on one of our internal streams. It's different from manoelneto's fix and should be visible on Github whenever the fix is merged into our Main branch.

avatar image manoelneto Oct 10 '16 at 05:05 PM

My fix was actually a crude one-liner to aid those in a pinch since the "composited" window style is intertwined with a whole lot of code involving window transparency and desktop composition which sole purpose is decide if that flag is enabled or not. A proper fix would involve a review of all that (for example, if things still work on Windows 7, where desktop composition can be turned off).

avatar image Maggese Oct 15 '16 at 04:39 PM

I have the same bug, but I'm not a windows insider, neither have windows pro (indeed the update installed itself forcefully).

My windows version is: 1607 (Build 14393.321).

I use the Epic Launcher version of the engine, is there a way to avoid this bug? Or we have to wait for new engine version?

avatar image Matthew J ♦♦ STAFF Oct 17 '16 at 02:10 PM

Hello Maggese,

If you're willing to use a source build downloaded from Github, you could apply the change that manoelneto mentioned above and then recompile the engine itself. This should fix the issue in that source built engine. Otherwise, you'll need to wait for the next version of the editor or revert to an earlier build of Windows, which I'm not sure is an option in some cases.

avatar image Rakosman Nov 04 '16 at 11:56 PM

The bug report indicates the issue is "fixed." I'm assuming this refers to it being fixed on the GitHub version, as it is still an issue as of today (4.13.2)

Does the "Target Version: 4.14" imply that 4.14 is when it will probably be fixed? If so, is there any estimate on when that will be released? I have no idea how to go about using the GitHub version.

avatar image Matthew J ♦♦ STAFF Nov 07 '16 at 02:41 PM

That's correct. When a bug is fixed, it's committed into our internal branches and then released later in a newer version of the engine. This particular one is available in 4.14. Based off the commit number, the fix should be available in 4.14 Preview 2 from the Epic Games Launcher or the latest Github build in the 4.14 branch. If you're interested in using the Github build, you can find out more about setting it up here.

Please note that developing on Preview builds is not suggested as they could have new issues that we're not aware of. If you do decide to upgrade, please be sure to keep a copy of your original project prior to conversion.

avatar image RobMilliken Oct 20 '16 at 04:03 AM

Maggese,

You may also want to check out the openGL method of running the editor, listed earlier in this thread until Epic releases 3.14. It is working well for me - no issues and fixes the pull down menu problem - and from the comments, it appears, others. That way, if you don't want to compile the source, or back up your build, you can still have a workable version.

avatar image Maggese Oct 21 '16 at 06:29 PM

Thank you RobMilliken, unfortunately in my case using opengl is even worse. I don't know why, but right click and drop down menus remain invisible and the other menus are transparent :-/

I guess I'll have to use the Git build...

avatar image RagingFire Oct 31 '16 at 03:04 AM

I changed the theme to a high contrast theme and the menus are back. windows looks ugly now but at least i can work with ue4.

(comments are locked)
10|2000 characters needed characters left

I nailed down the cause of the problem to the "WS_EX_COMPOSITED" extended windows style used by the pop-up child windows. Removing it causes the popup menus to work properly.

The problem can be "fixed" with a small change to the source code. Open Engine\Source\Runtime\Core\Private\Windows\WindowsWindow.cpp then locate and comment the following line:

 WindowExStyle |= WS_EX_COMPOSITED;

...then compile the editor.

From a quick glance I haven't seen any abnormal side effects.

Also, remember to report/upvote this on the Windows Feedback Hub, because it does sound like a bug on their side (I've been reading about WS_EX_COMPOSITED and it doesn't have a very pretty history, compatibility-wise).

I haven't done extensive tests to determine if this is a bug with all windows that use WS_EX_COMPOSITED or if it's something related to a particular combination of flags with WS_EX_COMPOSITED.

EDIT:

The more I read about WS_EX_COMPOSITED, the more I think it shouldn't be used the way it's being used. It seems to have a purpose only with DWM disabled (to prevent flickering by using double buffered painting on windows), but currently UE4 enables it only if DWM is enabled (which in Windows 8.1 and 10 means "always).

more ▼

answered Sep 24 '16 at 08:08 PM

avatar image

manoelneto
353 8 11 25

avatar image Angel Tsvetkov Sep 25 '16 at 07:01 AM

manoelneto, you are the men!!! Right in the center- the BUG is down. Congratulations for your clear work.
Tested and confirmed on W10.14931.1000 Pro Insider Preview 1607 and in UE4.12.5+UWP and in UE4.13. Perfect work

avatar image Dolomo Sep 26 '16 at 10:01 AM

The binary version of engine can't compile the source code, so i get the GitHub version then comment this line, another step is switch engine version in my project. It's done! Thanks for your help.

avatar image Matthew J ♦♦ STAFF Sep 26 '16 at 01:56 PM

Thank you for the research manoelneto. Would you like to make a pull request for this change on our Github repository? If so, this would allow the change to be reviewed by one of our developers that cover that field and determine if it is an acceptable change or would cause issues elsewhere, as users not on this version or with other setups may see other problems by removing this line.

Otherwise, I'll put in the report myself once I get a reproduction, mainly so I can confirm that it happens now and that the fix given fixes the issue.

Edit: Currently, there's an issue with Github where new pull requests are not able to be entered along with existing ones not being able to be edited other than adding comments. If you wish to make a pull request, let me know and I'll post here when this is fixed.

avatar image Snake.Pliskin Oct 02 '16 at 05:22 PM

Confirmed this will fix this issue. Running Win 10 Pro 14936.rs_prerelease.160923-1700 and UT 4.12.0-3101884+++depot+UE4-UT-Releases

avatar image Matthew J ♦♦ STAFF Oct 03 '16 at 06:31 PM

I'm glad to hear that you all have a fix for the moment. I managed to get a hold of a drive with Windows 10 Pro and have signed it up for the Insider Preview builds, now all I have to do is wait until the build is delivered and then I'll be able to reproduce this (hopefully) and get a report in. As far as those Github issues I mentioned previously, they've been fixed so if you would like to enter a pull request for this change Manoelneto, you can feel free to do so.

(comments are locked)
10|2000 characters needed characters left

Just thought that I'll add up on the topic.

Recently got Windows 10 Creators Update (version 1703 "Redstone 2") and encountered this bug.

I am using UE4.12. Removing WindowExStyle |= WS_EX_COMPOSITED; helped.

more ▼

answered Apr 17 '17 at 09:05 AM

avatar image

kirdaybov
78 3 9

avatar image Matthew J ♦♦ STAFF Apr 17 '17 at 06:00 PM

Hello kirdaybov,

Please be aware that this fix is a workaround and could cause other issues. As shown in the bug linked above, the issue was fixed in version 4.14.

avatar image VSZ Apr 20 '17 at 05:23 PM

Same issue here with the Creators update. To fix I used this git commit (from UE-36752). Thanks Epic for making the issue tracker public, makes finding stuff like this easy :)

(comments are locked)
10|2000 characters needed characters left

This BUG is confirmed and in W10.14931.1000 Pro Insider Preview 1607. All File Menu is broken + DropDown Menu not work in any window (Toolbar, Viewport, anywhere where is placed drop-down arrow)

more ▼

answered Sep 22 '16 at 12:36 PM

avatar image

Angel Tsvetkov
272 26 35 52

avatar image Dolomo Sep 24 '16 at 01:05 PM

This bug in my windows10 14931 still exists.

(comments are locked)
10|2000 characters needed characters left

some other solution ??

more ▼

answered Jan 11 '17 at 06:50 PM

avatar image

braian05
1

(comments are locked)
10|2000 characters needed characters left

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question