The “Started” event seems to have a weird delay, after it gets pressed once, I can’t press it again, for about a second or so, it sort of randomizes how long the delay is.
If i keep pressing the Shoot Right, really quickly, it will never reset and execute again, if i wait a second or two between shooting, it triggers.
the Old school inputaction shoot right works as intended, it’s something weird going on with the enhantedinputaction "started’ even, i tried “triggered” but it shoots really fast (i am using an oculus touch controller)
not sure what it could be…
Hey @Werewolven!
Yeah the delay is because “Started” needs to be different from “Triggered”. It’s meant to keep your input from spamming. So that’s what Triggered is for!
My suggestion: Use a “Do Once” node before your “Set Active”,
and a “Set Timer by Event” after the “Do Once” node.
Make a custom “Fire Ready” event, and connect your timer to that, down below.
That custom event: All it will do is plug into the “Reset” of your “Do Once” node.
And now you can promote the “Time” variable on your Set Timer and have that be your “Fire Rate”! Customizable and settable per gun! 
This doesn’t work with chorded actions and the results are genuinely nonsensical.
I have a 2D mouse XY input for orbiting the camera. This is a chorded action that depends on a bool input for RMB.
If I am not moving my cursor, then Started and Completed for RMB trigger as expected. If I am already dragging the mouse when I press RMB then EVEN THOUGH the chorded action immediately triggers, there is a noticeable delay on the RMB event triggering. “Started” never triggers at all.
I have been troubleshooting this for three hours and I’ve narrowed it down to this absolutely bizarre delay.
