Input System 1.1.1 always return 0 with readValue<float>() in player

Unity Engine
1

Hi,

when try to read a value from an Axis control type

7598794--942844--upload_2021-10-24_20-1-28.png
7598794--942844--upload_2021-10-24_20-1-28.png841Ă—423 26 KB

7598794--942847--upload_2021-10-24_20-1-53.png
7598794--942847--upload_2021-10-24_20-1-53.png847Ă—414 24.7 KB

playerInput.actions["Move"].ReadValue<float>()

always returns 0, but it works perfectly in build. Same problem with Vector2 values. With Buttons works correctly.
If I downgrade to 1.0.2 it works perfectly in player and in build.

Thanks

2

Hi @hugofreiregil ,

This is a known issue and will be fixed in 1.1.2: Unity Issue Tracker - Input Action ReadValue&lt;float&gt; always returns zero when called from FixedUpdate()

1 Like
3

I have the same issue, any idea when when 1.1.2 is coming out?

4

this still happens in 1.3.0?? with me if you use more than 2 actions the second will always return ZERO

5

I filed a bug report about this (some inputs receiving a value of zero when read a second time). Unity marked it as a duplicate of the following issue (linked), so I voted on that issue to be fixed. You should too if it’s causing you problems (in my case I’m postponing upgrading to newer versions of Unity and the Input System) else who knows if Unity will ever consider it important enough to be fixed.

6

I fixed it by just updating the package InputSystem to 1.4.4.

Hope it helps!