Can't Move Character Forward/Backward

Impudent_Swine · April 21, 2026, 12:50pm

I just set up an enhanced input system but for some reason the W/S keys are just not working. I can move just fine right/left with the A/D keys.

This is my IA_Movement:

This is the input mapping context that I am using on the player character:

And this is the input setup in begin play:

I have tried absolutely everything from switching out project settings to checking for walk speed to make sure is isn’t zero but none of these things were the problem. When I printed the string for the Y-axis vector, nothing printed, which seems to indicate that the problem is the W/S inputs or just Y-axis vectors in general just not registering at all, or being blocked for some reason. I am fresh out of ideas and chatgpt can’t even figure it out

tyconner · April 21, 2026, 2:09pm

Hey there!

I ran into a similar issue and realized I had put my mappings in the mapping context under a different context other than “default”. Can you show the entire mapping context binds screen to ensure this isn’t the issue?

illspiritx · April 21, 2026, 4:04pm

For the mappings, try changing teh modifiers on w and s to Swizzle Input Axis Values with an order of YXZ (and a negate on S).

Since ia_movement expects a vector, it’s probably overriding your Y scalar with the 0 coming from A and D or something.

Impudent_Swine · April 21, 2026, 4:10pm

That was the whole mapping context, at least for the IA_Move with controls the player movement

This worked, though I admittedly do not know why. I cannot for the life of me find what is blocking the Y vector inputs with the scalar modifiers.

illspiritx · April 21, 2026, 4:27pm

Yea, it’s a bit odd it won’t report or print a phantom 0 coming from an inactive scalar, but I guess the input action event just doesn’t fire from null inputs.

tyconner · April 21, 2026, 4:44pm

That is not the entire mapping context asset, it is only where you have IA_Move. There are multiple profiles you can set inside of a mapping context asset, that’s what I was asking for.

Glad you got it fixed.

Swizzle Input on an Axis2d changes from using -1 - +1 on X for that input mapping to putting it on the Y (depending on the axis you select).