I haven’t been able to reproduce this in 4.7.6. Is that version of 4.7 you’re using? Does this happen with every interface you create? Are you able to reproduce this behavior in a new project? And just to eliminate this possibility: go to Editor Preferences > Blueprints and make sure Force Legacy Menuing System is disabled.
If you can reliably reproduce this, please list exact steps we can take to do so here. I can also take a look at a small test project if you upload it someplace like Dropbox or Google Drive and get me a download link.
I’m using 4.7.6 on Windows 7 x64 Ultimate (Максимальная) ru_RU.
It happens with every interface I create. I’ve reproduced it in a new project before writing this bug report. Force Legacy Menuing System is disabled. steps listed is exactly what I did, modulo names and fact that function had 2 inputs and 0 outputs. I’ve tested it with 1 output too. Removing starter content from that project crashed an editor (report sent).
I’ve created yet another project in same way, with same issue.
Found out that issue doesn’t persist across editor reloads. Here’s [a link to project][3].
I can’t reproduce this at all, even in project you attached. To test, I created a new blank project and created a new Blueprint Interface. I used default NewFunction_0 and gave it two Inputs, compiled and saved. Then I created a new Actor Blueprint, and implemented Interface in Blueprint Class Settings. Compiled and saved, and searching for this is what I see:
Am I missing a step somewhere, or taking too many? Are you compiling and saving between steps, as I did? When you say issue doesn’t persist across editor reloads, do you mean closing and reopening project suddenly makes this work? image you showed is what it looks like when an interface isn’t implemented in Blueprint, which is odd because I can clearly see it there.
I’ve been trying to circumvent issue in several ways, and one of ways I tested was exactly same as you described. only thing that managed to help is to close and reopen an editor. I don’t have any more details, probably I’m missing something.
Could memory dumps or remote debugger access help? I think I could try building editor from source and see if there is any difference in its behaviour.
I haven’t heard back from you in a while. Did you get a chance to build from source, and did problem persist? Could you also try in 4.8.0 and see if you still see it there? I’m going to resolve this issue for now, but if you’re able to provide more information please let me know. Thanks!
Just to be sure: are you searching for Interface name, or Function name? You’ll need to search for function name to get it to show up as an Event in context menu. And I’m sure you’ve checked, but is interface is still implemented, correct?
Otherwise, do you recall what changes you made that might involve BPI between yesterday and today? Perhaps a change to BPI itself, or in BP that’s using it? Does this now happen with new BPI/BP combos in your project, or just one you noticed it with? And does it happen in new projects as well?
Without a repro case, there isn’t much we can do. polkovnikov above mentioned that restarting editor seemed to resolve issue when this occurs, can you confirm? Thanks!
this happens when i add an output to an interface function. interface event doesn’t show up. if i remove output leaving only input event appears in context menu
i found this answer after i posted this.
it’s kind of a bug, but not really.
Looking over this, what is happening is that Functions from a Blueprint Interface with no output are considered Events by Blueprints that implement that Interface. Those won’t show up in Functions section of My Blueprints tab. What you would need to do to override their functionality is search for Event version of Function from right-click context menu and add that Event to your Event Graph.
Is this still not working? I’m currently stuck with this issue while following this tutorial. At 8:33 interfaces do not show on left. https://www…com/watch?v=EtUel02w3EM&t=190s
Running 4.16.3
To be clear. An interface function WITHOUT an output variable shows up fine in All Possible Actions dialog…
An interface function WITH an output variable does not.