I had old event for debugging purposes, which changes player state on pressing K key. Just K, without binding or anything. And after I’ve deleted this event it keeps working. I’ve searched along all my blueprint and there’s no any other instances of K key event. Moreover if I create this event again with other nodes it does not work, old deleted event keeps firing. Also I’ve tried to create key binding via project settings, binding something to K, and then creating this event, this event also does nothing, and old deleted event keeps firing! Help! I need to get rid of this!
Search for Pressed and hit the Binoculars button in the upper right.
This will open a new Find in Blueprints windows with all results; double click each entry with a white dot, as seen above, and it will take you to the appropriate node. Hopefully you can find it like this.
yeah, that’s slick. but it gave no results for K, I also searched for the event on the “my blueprint” tab, which gaves all keyboard events in the blueprint, and guess what? there’s no K event at all, that’s kind of a bug in compiling or whatever
Ok, let’s say I just can’t find it. Then, I can create another event for K, and both events will fire when I press the key. Like when I have two events for J and them both firing at the same time. But when I create another K event it does nothing!
But did you search for Pressed or K? Search for Pressed and step through every entry.
Ok, let’s say I just can’t find it.
Then, I can create another event for
K, and both events will fire when I
press the key. Like when I have two
events for J and them both firing at
the same time. But when I create
another K event it does nothing!
By default input is consumed, and it’s consumed in a very specific order, too:
This can be overridden in the event’s Details panel.
Moreover if I create this event again
with other nodes it does not work, old
deleted event keeps firing.
This is in line with what I said; this K key is still hiding somewhere and consuming input. Check level blueprint. Check player controller.
it was in level blueprint left by other developer. thank you!