Hi ,
It is because you can Fire from either of those, Trigger box or F.
You have got 2 Exec going to one point.
I would set bool on trigger overlap
Then On F check that bool, if bool good, fire the EXEC
I created a blueprint for a door that opens when the player is in a trigger box volume and presses the F key. For some reason, when I first start the level in PIE mode, I can open and close the door from anywhere in the level. In other words, I don’t have to be anywhere near the door. However, once I move into the trigger box volume and then leave it again, it works the way it’s supposed to. Any idea what could be causing this?
Thanks for the advice! I’ll give that a shot as soon as I get home from work.
Actually - the more I think about it the less I understand what the problem is. I don’t have the trigger box enabling the door timeline. I have the trigger box set to enable controller input OnComponentBeginOverlap and to disable input OnComponentEndOverlap. It doesn’t seem like replacing that with a bool would help.
To me it seems like for some reason controller input is visible to the door blueprint by default as soon as PIE mode starts. Then, when I enter the trigger box and leave it, controller input is disabled (as it should be). Is there some way to ensure that controller input is disabled at the start? Maybe add a node to OnBeginPlay that explicitly disables input?
Either way, I will still try your solution when I get home to see if it works. Thanks again.
You were totally right. I got home and made the change you suggested (along with some other stuff because the logic wasn’t quite right with my blueprint) and it’s working perfectly now. Cheers!