Mapping a combo involving the dpad disables the dpad for the original controller

[zany130]

Discussed in #890

^{Originally posted by zany130 May 12, 2024}
I am trying to map hotkeys on the input -remapper controller on top of the original controller for example: start + dpad up to be vol up start + dpad down be vol down etc

but each of the buttons when pressed by themselves should come from the original controller

this, for some reason, disables the dpad in the original controller. Is this intentional?

no other button exhibits this behavior. For example, I have start + y set to alt+f4, and both start and y work normally when pressed by themselves. meaning they come from the original non emulated controller

I can create a dpad mapping in the emulated controller and that will work but I want all normal gamepad inputs to come from the original controller

bug? @sezanzeb

the creating dpad mapping in the emulated controller no longer works. If I make any mapping involving the dpad. the dpad no longer works at all while that profile is in effect

https://gist.github.com/zany130/301c548addc078bc7d32111babcb1d6d

[amigthea]

I can confirm the behaviour

[voronind-com]

I also experience this. It also weirdly disables it. I.e. if I only create a mapping with a dpad-up, then dpad-down gets disabled and vice versa. Same goes for sticks. RT/LT etc.

[alxns7]

I have something similar, where mapped dpad buttons stop working on the original controller when the injection is applied.

For example, I have START + DPad-X Left mapped to Super_L + Shift_L + Left and same for Right (to move windows around displays)

I have Steam big picture running, the dpad works normally. When I apply the injection, dpad right/left stop working, but dpad up/down still work, while I can move my windows left/right.

As soon as I stop the injection, dpad left/right work again. It's really odd.

[sezanzeb]

Please install from the "fix_hat_mapping" branch (#1274) and give feedback if your problems are fixed