PS2 Controller Problem Please Help!!!

[Mofo]

So I got joystick mapper right and connected a ps2 controller to it now when I want to scan any buttons it's perfect but only 3 buttons don't get scanned at all like the program doesn't find the input at all the buttons are circle, square and cross. Please help me I have even tried manualing adding the binds because I know the button numbers for those three buttons (b13, b14 and b15)

Please help

[Rodrigo]

does your controller work with a ps2? it may be a hardware problem

[Mofo]

yes i tried with a ps2 and the three buttons work i dont know if this is a problem or not but when i connect my controller joystick mapper thinks it is a PS3 controller just wanted to say that just in case

[Rodrigo]

I have no idea what it could be... if all buttons works in your ps2, it should work on your mac :/
It is a genuine controller? what kind of adapter are you using?

[ed209]

I confirm this problem. Some more info:
- PS2 Dualshock connected by this style of generic controller: https://www.ebay.com.au/itm/302714365098
- There are no drivers available, it *almost* just works.
- Almost == All axes and buttons except the ones the OP described - cross, square and circle, designated as 13,14,15 in your app.
- Same issue exists in the competing app "Controllers Lite"
- Problem appears to be that MacOS USB support is recognising the hardware as:
PLAYSTATION(R)3 Controller:
Product ID: 0x0268
Vendor ID: 0x054c (Sony Corporation)
Version: 1.00
Speed: Up to 12 Mb/s
Manufacturer: Sony
Location ID: 0x1a121000 / 7
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0

So on the surface it seems that the adapter is hardcoding the controller type without actually discovering it.
BUT..... the controller and every button and axis work fine in RetroPie on a Raspberry Pie, so it's not as cut and dried as this.

This is a cheap anonymous adapter from China, but works really really well. There's zero hope of support or a fix as there's no eeprom/flash/microcode or update mechanism.

As a workaround, would be possible for Chibata to add a manual software override to coerce the device to be treated as a Dualshock 2, or does this discovery/classification happen prior to any visibility in code (ie opaque to your app)?