360 controller input not recognized by gimx-config

[hoshi88]

Hey there.

First of all, thanks for the awesome work. I bought a G27 because of it, and I'm glad to report I got it to work just fine on PS4.

I've read that it's possible to use other input devices so I tried to make a config replacing the G27 mappings by a wired 360 controller (MadCatz TE fightstick), but the config program doesn't recognize any of its inputs. I've tried a different wired 3rd party 360 pad, also replacing its driver by libusbk's, no go.

Am I missing something, or is that not possible?

I'm using the latest Gimx, under Windows 10.

[Mrgonuts]

Hi I think you would need to reflash with different firmware as you've used the EMUG29PS4

[hoshi88]

The issue is that the fight stick inputs aren't detected by the config app. I don't even get to the point they're sent to PS4, so the firmware flashed doesn't matter at that point.

I did manage to make it work by using joy2key. Joystick inputs emulating keyboard keys through j2k, then gimx-config receiving fake keyboard inputs. That works with either DS4 or G29 firmwares, but that surely adds some latency so I'm still looking for the right way to do it.

[Matlo]

Hi,

also replacing its driver by libusbk's, no go.

You are going the wrong way. The only case where libusbk has to be used is system instability due to USBDK. I suggest you to remove and delete the libusbk driver.
There may be issues with some specific controllers. First make sure Windows is able to detect your controller. Go to the Device and printers and check the controller is listed. Right-click on its icon, and navigate to the test tool, and check that the inputs are detected.

[hoshi88]

I've rolled back to the default 360 controller driver. Both controllers have their inputs detected by the test tool, and they work on other games and joy2key.

Not sure if it's relevant but I did get them to work on a RPI setup I've done afterwards, just not on Windows.

[Matlo]

Is directx up-to-date?

[hoshi88]

Yup, DX12 up to date.

[Matlo]

I think there is a problem with the SDL library. I'll try to provide your a test program to further investigate.

[hoshi88]

Sorry to bump an old post, did you have a chance to look at this?

[Matlo]

Sorry, I forgot to open a new issue for this. Here it is: #368.
I'll try to update libSDL to version 2.0.4 for the next GIMX release. Hopefully it will fix the issue.