Hi everyone I have a big problem that I can not solve … I followed a tutorial on how to read a document by pressing a button, everything works fine if I build one, but if I want to create another, the documents are confused and if I press on one of they are shown to me the other one and vice versa.
if I assign two different keys everything works, but with the same key, it does not work.
I’m a beginner, how can I do?
Sorry for my bad English, I hope you can help me.
Not sure. Maybe your E key event needs to be set to not consume input. That is a checkbox in the right-hand pane when you have the node selected. But if input is disabled it shouldn’t matter, so I am just as confused as you.
I don’t see the point of you having a Gate if you never Close it.
Have you tried setting Breakpoints and watching the code progress by Stepping Over it? Or placing PrintString nodes to confirm whether an expected execution path is being used or not?
As for the gate I do not know, I simply followed the tutorial.
I repeat, if (for example) I assign the E key to a document, and another letter to the other document works fine, but if I assign the same letter, it does not work well.
Being inexperienced in blueprint, I have tried but I can not find the solution and many times, I can not quite understand if not with the screen.
Thanks for the reply anyway.
So did you try turning off the Consume Input checkbox on the E event node?
yes, but it does not work the same.
This is the tutorial…link text
in the comments I read that several people had the same problem.
I wonder if it is happening because other actors trigger the overlap begin/end events, other than the intended one. You could test for that.
I’m not sure what is wrong, but there are some other ways to get the same effect, then the one in the tutorial. Maybe one of those would work better for you, like using Blueprint Interface to trigger interaction availability.