This system works beautifully. If…. You use one finger at a time. If you mash both input actions or hold one and flick the other one. This rapidly causes the float value to spiral uncontrollably.
Not entirely sure how to fix this? Or is there a tick box I’ve missed stopping multiple inputs or to only take the last input at a time or something.
It seems to rapidly multiply against itself until it explodes.
Omg.. Yeah… I guess because I’m holding it down and mashing the other Key. It’s not the mashing, It’s the length in which I’m holding the key to do the test to prove the mashing, lol. I got positively bamboozled.
But You can still hold backwards, Push forwards and Itll suddenly go from -1 to 1 with no interpolation between them.
This feels like one of those times when multiple inputs is allowed, and I want it turned off. So I need only the last input on that enhanced input to be accepted.
Yeah, just tested. You can hold down S = -1 and then push forwards, and it doesn’t change the value to 1. it just sits at -1 till I release S.
So when I hold S, It prints -1
But While I’m holding S, I push W. The W doesn’t overwrite the S.
It ignores the W input, Until I release the S.
But weirdly, the opposite isn’t true.
If I hold W, And it’s printing 1, If I push S, It does Overwrite the W.
It feels like key shadowing Kind of (I did go into notepad and check for this in case It was a hardware issue)
Update:
So I changed the accumulation behaviour to cumulative. So it cancels itself out now. Which Is better than the opposite. But I’d be really curious what in the heckers is happening.
Must admit, I’m not a Enhanced Input hacker. There may well be something in the options to tune this, or you might need to do something in the blueprint to get the functionality you want.
Started and completed are linked to every key as a whole. Eg. If you Hold down one key to get the started print. And then hold both. You can swap what key you hold as many times as you like, The completed command will only happen when both keys are released.
Using triggered and action values, Whatever Key you assign the negate modifer is always the one overwritten or “Shadowkeyed”.
Changing accumulation behaviour to cummulative does somewhat fix the issue. But If you need the started/completed like I do. It wont solve that.
For me however. I need to figure out a better system that doesnt use the started or completed triggers.
Well, for anyone in the same boat as me, Welcome to my monstrosity.
xD This is the very definition, it’s not stupid if it works.
I split them up to stop it getting confusing. But Essentially, it’s the world’s silliest way to introduce tilt to a vehicle. There are loads of better ways I’m sure, But for my…I guess specific niche use. This is one of them xD
Update:
This is the final Overall Node system I used and works really well. Enjoy
