Hi, I am migrating to 5.1 and trying to get my head around the enhanced inputs. I have been using some keyboard triggers but have noticed that it is firing my events multiple times from a single key push. I have tried playing around with triggers - in particular ‘Hold’ with one-hit ticked and a delay but this still seems to fire multiple events. Have also tried ‘pressed’ - same result.
I wondered what is the best input trigger to use for keyboard presses without getting multiple event triggers from one push of a button?
Also how do I get the unpressed trigger? Previously the input events had pressed/unpressed?
hello,
here is a little example of a button press and release, each will trigger an print text
if you hook up straight in trigger it will fire 2 times, i ran into this problem with my project… you can set up pressed and released events with respect to threshold
Thanks this is just what I needed, had not spotted the ‘released’ trigger - but as you say it fires twice for every press. I know I can get around that with a DoOnce node in the blueprint but it seems like this should be something that should be able to be made to work on the inputs side of things - Did you find a solution to it firing twice?
hi,
just messed around a bit with the triggers, i can only make them fire twice if i add another trigger to pressed. but if i do it will fire twice on trigger… i had in my old game pressed and released and hooked up trigger and completed and i had this bug firing twice. tried adding to mapping action key a trigger and to the key itself, but it only fires once as far as there is only one trigger.
I experienced the same issue where my action was triggering twice for each button press. I looked at the StakOBot project and noticed that for jumping, it uses ‘started’ rather than ‘triggered’, so I did the same and it fixed my problem. (the brief explanations of the different trigger events should have helped, but like so many of the engine comments it only confused me futher.)
So far my experience with Enhanced Input has not been a positive one. Such a complex, arcane system needs some proper explanation and comprehensive tutorials. The old system was so simple and I wish I had stuck with it, although considering it is deprecated I assume they will remove it from the engine sooner or later. On the plus side, I think I’ve finally got everything working as intended, after many days of working to migrate to the new system.
Just bumping this because I am hitting the same exact issue even though I have set it up like Rev0verDrive’s first screenshot. 1 push (and holding button a bit) = 2 input events.
