Be able to activate accept-input state, but not to assign anything

[Miepee]

Describe the bug In Controllers -> Compatibility mode -> controller configuration, you can use the keyboard [Accept] in order to for the game to assign your next input to that button. However none of the keys or controller buttons actually work, and waiting for a timeout is needed

To Reproduce Explained above.

Expected behavior Keyboard should not be able to activate that state.

Platform (please complete the following information):

• OS: Linux
• Version: Arch, Mint 19.03

Game Version: 1.5.2

[Lojemiru]

This seems like an Arch-specific input bug rather than a general AM2R issue - have you tried this on both the AppImage and with a native install? What controllers has this been tested on?

I'm interested in troubleshooting the lack of controller input, but the "expected behavior" will not be changed. The keyboard must be able to enter this state because there are situations where a controller may not have default binds that allow for menu navigation, and the keyboard must be used to help configure the controller.

[Miepee]

have you tried this on both the AppImage and with a native install?

Yes, happens on both

What controllers has this been tested on?

Xbox One Controller. If I initiate the "accept-input" state with the controller, I am able to assign a different key to it.

I can try testing it on my Mint machine real quick.

[Miepee]

Tested on Mint 19.03 with the same Controller. Same behavior occurs there. The controller works fine, I can assign my keys, if I just do everything from the controller, but if I initiate the "accept-input" state from a keyboard, then neither keyboard nor Controller is able to assign keys and I have to wait for a timeout.