Each game controller button, dpad or axis (thumbsticks or triggers) have an internal numeric representation that very often does not match the controller's labels and is different for each controller, no matter its current physical location. Joystick Mapper (and any other app that reads gamepad input) uses this information to map the input (button/axis/etc) to the desired output(keyboard/mouse).
Joystick Mapper was designed to be generic enough to be able to use any mac compatible joysticks/gamepads, so it can not assume a common popular layout for all controllers.
That is why, currently, there is no way to create generic presets that can be used for all controllers, even if they have similar button count/disposition. Each preset only works correctly with the kind controller was used to create it.
When creating a preset, you generally simply scan for input and press the buttons for each mapping(bind). So it shouldn't be a problem. But when you need to edit it, it may get a bit boring to locate which number corresponds to which button.
Currently, to help figuring the buttons/axis numbers when editing a preset, you can:
- Download the Joystick Show App, which is a gamepad visualizer / tester.
- When creating/editing a preset, you can scan for input, then when you press the button/move the sticks it will show the info you need. Then I suggest you to write it somewhere else if you need to edit a lot of mappings. It is a bit cumbersome, but works.
I plan to include some kind of built-in way to visualize the buttons values or even hide the need of this information in the future, so it would be easier to edit the presets. Not sure how yet.
For now, here you can find some diagrams for some popular gamepads to help you modify your presets:
1 With the latest version of this driver.
2 The XBox One controller have the same layout as the XBox 360 controller, using the driver above.