I'm beginning to make a game and decided to use an input map to better support remapping and controller. Here's the issue, when I use the analog stick vertical axis for "movementup" and "movementdown" it reads out as a 0 at the extremes. So if you are halfway between the bottom and the middle, event.getactionstrength("movement_down") returns ~0.5 as it should. However if it is all the way at the bottom, instead of a 1 it returns a 0. This means that the player will stop moving if the analog stick is at any extreme, when in reality it should be moving at its fastest. Windows reads the gamepad successfully, and I've tried this with two different gamepads, getting the same result. (I'm on 3.2.3 stable if that helps pinpoint a patched bug or something)
I've done some more testing, and have some more to report. The issue also occurs on both a Switch Pro controller and a Xbox Wireless Controller, either wired or wireless. I don't have any PS4 controllers but from what I've gathered so far it would be the same. Curiously, the switch pro controller seems to have a range of 0-0.7, before zeroing out at the extreme, while the xbox controller has a range of 0-0.9, zeroing out at the extreme. Windows itself still reports the joysticks as functioning properly (can get the full range in the built-in tester). With this happening on three controllers from two different manufacturers I can confirm that this is some sort of engine issue.
Attached here is a video that should document the issue: