Generic Arcade Stick Controller Mapping -- PS4 touchpad?

[A-Log]

I have several arcade sticks that I use on PC for fighting games, and usually they're compatible with PS4, but not recognized as PS4 controllers in Steam.

For the Razer Panthera Evo, it's recognized as a PS4 controller and all buttons work out-of-the-box, including the touchpad.

For my custom fight stick w/ a Brook UFB installed, and for my Qanba Pearl, it's only recognized as a generic controller.

Now, I can go into controller settings, manually map all the buttons, and set it to be recognized as a PS4 controller (so that button guides in-game show up with PS buttons, for example). But the touchpad is the only input that isn't available on the mapping setup.

So what's the difference between these two cases? Why is one recognized as a full-featured PS4 controller, but the others aren't? Also, is there a manual way to set the mapping for the touchpad button (such as in an .ini file)?

Looking for more advanced info about the way Steam handles gamepad mapping, and controller recognition.

[CZI]

I'm not quite sure, but following setting works most of the case.

1) Set XInput compatible mode on controller
2) Disable Steam Input

If the game is newer and supported Xinput natively, it should work.
UFB should work this way as well.

Some older game does not support Xinput, you may need to enable Steam Input and configure.

[A-Log]

Yeah, I know. XInput isn't the issue here, I can *use* the controller fine. I just want to find a way to map the PS4 touchpad, which 1) isn't available on XInput and 2) doesn't *seem* to be available for the generic controller mapping you can configure in Steam's controller settings.

[CZI]

I have custom hitbox from UFB.
At least UFB has touch pad wiring.

https://www.brookaccessory.com/detail/06960737/
See the User Guide PDF.

I'm not sure other devices.
I'm using 5 of the MayFlash F300 Elite.
It is required to connect P4 pad as pass through.
It's extra wiring and annoying, but I can use touch pad button on pad.

[_I_]

generic controllers may not support all the features of the ds4

[A-Log]

_I_님이 먼저 게시:

generic controllers may not support all the features of the ds4

Yeah that's the impression I get. But the thing is, my Panthera Evo is recognized as a full-featured DS4 controller, but my other PS4-compatible sticks aren't. So if there's some way to force Steam to manually force DS4 mode (not generic controller labelled as a DS4) for a certain device, that's exactly what I'd be looking for.

[A-Log]

So I did a little more digging ... Steam uses the SDL2 library for generic gamepads, which explicitly doesn't support touchpads per this issue: https://github.com/JujuAdams/Input/issues/194

So manually configuring a touchpad is out. But still, if there was a way to get Steam to recognize a controller as a DS4 (which it should be), that would still accomplish what I'm trying to do.

[tintingaroo]

A-Log님이 먼저 게시:

_I_님이 먼저 게시:

generic controllers may not support all the features of the ds4

Yeah that's the impression I get. But the thing is, my Panthera Evo is recognized as a full-featured DS4 controller, but my other PS4-compatible sticks aren't. So if there's some way to force Steam to manually force DS4 mode (not generic controller labelled as a DS4) for a certain device, that's exactly what I'd be looking for.

https://steamcommunity.com/groups/SteamClientBeta/discussions/1/1649918688128349405/#c1649918688131578141 & following posts

[A-Log]

tintingaroo님이 먼저 게시:

A-Log님이 먼저 게시:

Yeah that's the impression I get. But the thing is, my Panthera Evo is recognized as a full-featured DS4 controller, but my other PS4-compatible sticks aren't. So if there's some way to force Steam to manually force DS4 mode (not generic controller labelled as a DS4) for a certain device, that's exactly what I'd be looking for.

https://steamcommunity.com/groups/SteamClientBeta/discussions/1/1649918688128349405/#c1649918688131578141 & following posts

heck that's exactly what I was looking for, the HID manual set, thanks a ton!

[A-Log]

The VID/PID setting in config.vdf worked perfectly! Didn't have to change the default Windows driver for the Pearl, all I had to do was add the line:

"controller_hid_ps4" "0x2C22 0x2300,"

and everything is detected as a fully-functional PS4 controller :)

[Cetty]

a