Axis value not right?

I am developing a platformer game (as said in previous post) and it’s going very well. However, I have just created a new axis value to determine whether or not the S key is being held down at any time for a blueprint, I have enabled player 0 input on the blueprint, but when I tried using it (if the axis value is not 0 then it will launch you, otherwise not) but it was still launching me, so I printed out every tick what the axis value was, and it turned out the the first value was 1, then the next 3 were zero? So every time I tried to stop the player from launching, it launched anyway because 3/4 of the time it wasn’t being told not to?

Does anyone know how to stop this annoying bug?

Thanks :slight_smile:

[EDIT] I also tried using an action mapping; when it’s down set boolean to false when it goes up set back to true, and when I debugged that every tick when it didnt work (debugged the boolean value) when the button was held down the first one was false then the next three were true?

Howdy Warlord,

Thank you for your bug report. I just have a couple more questions on your setup. Would you be able to provide a screenshot of your current blueprint setup? I am hoping to compare your setup and the one that I am currently using. Could you also include any logs associated with the game and your DXdiag? Any additional information that could help reproduce the issue would be greatly appreciated.

Here is the current setup that I am using to test the issue:

Thanks and have a great day!

Thank you for responding :slight_smile:

This is what my blueprint was like (I have since changed the ‘Can Launch’ function to the player and it works)

And this is my DxDiag

Hey Warlord,

I am going to promote your above answer of enabling the Can Launch check box to an answer. If you experience any other problems, please do let me know.

Thanks!