1D axis not working for keyboard input in version 1.4.2

Unity Engine
,
1

As the title says, 1D axis inputs seem to be broken in input system version 1.4.2. Here is the axis:

8373765--1103784--upload_2022-8-19_8-30-22.png
8373765--1103784--upload_2022-8-19_8-30-22.png1920×1080 113 KB

The Roll action’s Action Type is ‘Pass Through’ and the Control Type is ‘Axis’.

When running the game, the Performed callback is never called, and the ReadValue() is always zero, even when the E and Q buttons are pressed.

Changing to a 2D vector works fine, and changing the keyboard buttons to mouse left/right clicks also works.

This issue does not occur in Input System version 1.2.0.

Anyone else able to reproduce this?

2

I swear im getting the same exact issue. Using the 1-D axis for A/D and Left and Right arrows for movement but my character doesnt move at ALL.
Seems to work perfectly fine if I use a controller though.

Weird think is that if I press both A and Left or D and Right at the same time, then the character moves in the respective direction.

I sure hope they fix this soon.

3

Same issue here. I was racking my brain trying to figure out the issue for two days.

I’ve noticed if you only have one Action Map referencing the axis, it suddenly works again. For example, I have an A/D steering axis for a car in my “Vehicle” Action Map. If I remove the WASD axis from my “UI” action map, it starts working again.

Anyone have a workaround or know how to revert the InputSystem version?

Edit: Changing the WASD axis in the UI Action Map to arrow keys seems to work, but I don’t want that.

4

I have this exact problem after updating. Arrow keys produce no callback, changing to other keys works.

5

A little more info…

The problem appears to be that if two action maps have the same keys (any keys) mapped to a 1d axis, only one of the action maps will trigger callbacks.

The input system is completely broken now because of this. Rolling back to 1.3.0 will ‘fix’ the issue but who knows what further problems that could cause.

This is not the sort of breaking problem you expect when simply trying to stay on the latest LTS minor version.

2 Likes
6

Suddenly my mousewheel doesn’t work! It’s also a 1D Axis, but it was working earlier. I didn’t change anything. It throws out of range exceptions now. What a mess.

7

This bug is still present in Unity 2022. I even deleted the input map altogether and recreated it, same result. I don’t understand how people are managing to work with the new input system without this blocking them. It’s completely broken for any solution that uses multiple action maps.

8

I’ve just hit this as well and -at least in my case- it was a side-effect of the “Enable Input Consumption” in Player Settings-Input System Package.

Looks like the “first” Axis bound to those keys consumes the key press and so it never makes it through.

Disabling that flag makes the axis work again (but now I need to handle consumption/filtering myself)

9

Official bug:

10

Finally fixed in 1.4.4

11

is it fixed? I was unable to get a 1d axis working where O set the float value to -1 and P set the float value to 1… when pressing P it would work, but O while did callback did not present a value, always 0?? this on 1.4.4

12

Check your code guys cause this really was fixed. The underlying problem was the ‘consume input’ variable having a new default of true which they reverted.

13

Check if you have saved the Input system