yes that comes from: http://hg.libsdl.org/SDL/file/e52d96ea04fc/src/joystick/SDL_gamecontrollerdb.h​ at LINE 234 ?

so a few more pointers (some of them are test programs, so u can see how to use it):

• have a look at the loop( ) function here: https://hg.libsdl.org/SDL/file/e52d96ea04fc/test/testgamecontroller.c​
• have a look here: https://hg.libsdl.org/SDL/file/e52d96ea04fc/test/controllermap.c​
• here: https://hg.libsdl.org/SDL/file/e52d96ea04fc/src/joystick/windows/SDL_mmjoystick.c​​
• here: https://hg.libsdl.org/SDL/file/e52d96ea04fc/src/joystick/windows/SDL_dinputjoystick.c​
• here: https://hg.libsdl.org/SDL/file/e52d96ea04fc/src/joystick/windows/SDL_dinputjoystick.c​
• aaaaand here: https://hg.libsdl.org/SDL/file/e52d96ea04fc/src/joystick/SDL_gamecontroller.c​

(if a link doesn't work, just copy-paste it manually into your address bar…)

it historically started here: https://bugzilla.libsdl.org/show_bug.cgi?id=2181​​ or here http://forums.libsdl.org/viewtopic.php?p=40677​

anyway this should get u goin'

that's it …. all the best ?

@Acharis

I found the same problem with the same controller. I don't know if the mapping is wrong inside SDL, or it's the fault of the controller (mine is a fake PS3 controller, - sold as genuine on ebay, but actually a fake). This fixed things for me:

const char* fakePS3Mapping = "030000004c0500006802000000000000,Fake PS3 Controller,a:b14,"
"b:b13,y:b12,x:b15,start:b3,guide:b12,back:b0,dpup:b4,dpleft:b7,dpdown:b6,dpright:b5,"
"leftshoulder:b10,rightshoulder:b11,leftstick:b1,rightstick:b2,leftx:a0,lefty:a1,"
"rightx:a2,righty:a3,lefttrigger:b8,right trigger:b9";

SDL_GameControllerAddMapping(fakePS3Mapping);

I don't know about SDL (as I never ever worked with it) but XInput and generic low-level HID input handling is accessing the USB specifications of the HID device. This is usually a binary template of the controller you want to get input from which is used to map the input message send from the device to some sane results like Button, DPad or Axis states.

Those controller templates come from the corresponding device driver and may or may not be available to ge from the driver API in Windows for example. I already had the problem that a PS4 controller doesn't return a template data pack and so grabbing input wasn't possible.

You have to either install a driver which grants support for those templates or generate the template on your own and post that to the driver API

@Shaarigan SDL has a bunch of pre-canned controller mappings for known controllers (http://hg.libsdl.org/SDL/file/e52d96ea04fc/src/joystick/SDL_gamecontrollerdb.h​).​ The issue here is that the controller mapping for this controller seems to be wrong.