Game Input MultipleXer

Yes, you understood that correctly, I might open a bug report on there mainly because I've found a workaround and if anybody would experience same bug, they'd know what to do.

Thank you for your help finding and understanding the issue here.

So my theory was correct with it being out of bounds, I edited the config like this: <?xml version="1.0" encoding="UTF-8"?> <root> <controller id="1" dpi="1200" type="DS4"> <configuration id="1"> <trigger type="" id="" n...

Actually…now that I think of it…since it shift by +1, it means that dpad left is now button ID 17 and it is out of bounds, correct? so I either need to somehow shift all the button IDs by -1, so that after this bug hits it it will leveled out correctly, or…find the issue in gimx itself lol

Okay, so using the script you linked I managed to get this: button_id: 40 button_type: 22 value: 8 overflow: (1, 1, 0) button_id: 24 button_type: 23 value: 8 overflow: (0, 1, 0) button_id: 162 button_type: 45 value: 8 overflow: (1, 1, 1) button_id: 136 button_type: 46 value: 8 overflow: (0, 1, 1) bu...

Sorry for the late response, was a bit busy. Yes, I have tried that before and I was able to set it up for every button except the dpad left, I also can nnow add that when I open gimx-config and use auto detect feature it detects inputs according to the config itself (for example, dpad left is butto...

Now, I don't understand what the defines you've sent actually mean, but your guess is absolutely correct it is off by one, (dpad down - shows up as dpad left, dpad right - shows up as dpad down… so on and so forth, but dpad left is inactive…like if I press it, it literally doesn't react) so… if it i...

ohhh…okay…I understand what the problem is on a larger scale at the moment, I am using raspberry pi - and it has the problem I was describing, but now I used windows 10 virtual machine on my laptop just to check it, and the official configs works flawlessly, so there's that…

I get what you mean, but the thing is, I dunno why, but for some reason if I press…say square and assign square to it, it assignes square to cross instead, does that makes sense? so literally, each and every button is shuffled for some reason, and I don't understand why? I had to open gimx with the ...

So…I kinda fixed it? problem was that button_id isn't corresponding to the actual button location on a controller, so I had to use the "text" option in GIMX software to find which button is which, so that I could change it all to the *actual* buttons. Now I have another problem… there is n...

oh actually…I think the config is kinda dunked, I was looking in a debug and when I'm pressing PS button it sees it as r3, so I'm gonna redo the config and we'll what happens