SDL2 game controller API support

[wn2000]

It seems the code uses SDL2's joystick API and not the game controller API.
As such the control config file uses button codes instead of more meaningful names like "A", "B", "Left Shoulder", "Right Trigger" etc.
And users have to reconfigure the controls each time a new controller with different button codes is connected.
So here's my request to support SDL2 game controller API. Thanks!

[DirtBagXon]

I take the point, Daphne control system is not the most intuative. However, shifting this over is gonna break all the current deployments so maybe a new fork could be tackled by anyone interested ?

In the meantime I have created a simple tools that hopefully helps with the current configuration system, and removes the need to figure all the +1's that befuddle so many users.

https://github.com/DirtBagXon/hypjsch

It's packaged with most recent release zips for Windows and Mac and a quick compile on any linux.

[wn2000]

However, shifting this over is gonna break all the current deployments...

It can be made backward compatible. In the code, it can do some regex matching to see if it's the old joystick style, or the gamecontroller names.
What do you think?

[DirtBagXon]

Hey, can I ask which OS you are using?

I have a potential solution I would like some testing on. You can ping me on the Discord Channel (details on main page).

# Available AXIS MACROS
#
# AXIS_LEFT_UP
# AXIS_LEFT_DOWN
# AXIS_LEFT_LEFT
# AXIS_LEFT_RIGHT
# AXIS_RIGHT_UP
# AXIS_RIGHT_DOWN
# AXIS_RIGHT_LEFT
# AXIS_RIGHT_RIGHT
#
# Available BUTTON MACROS
#
# BUTTON_A
# BUTTON_B
# BUTTON_X
# BUTTON_Y
# BUTTON_BACK
# BUTTON_GUIDE
# BUTTON_START
# BUTTON_LEFTSTICK
# BUTTON_RIGHTSTICK
# BUTTON_LEFTSHOULDER
# BUTTON_RIGHTSHOULDER
# BUTTON_DPAD_UP
# BUTTON_DPAD_DOWN
# BUTTON_DPAD_LEFT
# BUTTON_DPAD_RIGHT
# AXIS_TRIGGER_LEFT
# AXIS_TRIGGER_RIGHT

[KEYBOARD]
KEY_UP = SDLK_UP 0 0 AXIS_LEFT_UP
KEY_DOWN = SDLK_DOWN 0 0 AXIS_LEFT_DOWN
KEY_LEFT = SDLK_LEFT 0 0 AXIS_LEFT_LEFT
KEY_RIGHT = SDLK_RIGHT 0 0 AXIS_LEFT_RIGHT
KEY_COIN1 = SDLK_5 0 BUTTON_BACK
KEY_COIN2 = SDLK_6 0 0
KEY_START1 = SDLK_1 0 BUTTON_START
KEY_START2 = SDLK_2 0 0
KEY_BUTTON1 = SDLK_LCTRL 0 BUTTON_A
KEY_BUTTON2 = SDLK_LALT 0 BUTTON_B
KEY_BUTTON3 = SDLK_SPACE 0 AXIS_TRIGGER_RIGHT
KEY_SKILL1 = SDLK_LSHIFT 0 0
KEY_SKILL2 = SDLK_z 0 0
KEY_SKILL3 = SDLK_x 0 0
KEY_SERVICE = SDLK_9 0 0
KEY_TEST = SDLK_F2 0 0
KEY_RESET = SDLK_0 0 0
KEY_SCREENSHOT = SDLK_F12 0 0
KEY_QUIT = SDLK_ESCAPE 0 0
KEY_PAUSE = SDLK_p 0 0
KEY_CONSOLE = SDLK_BACKSLASH 0 0
KEY_TILT = SDLK_t 0 0
END

[wn2000]

Sounds good. I'm running Linux on a rockchip based SoC.

[DirtBagXon]

SDL_GameController support has been added in: cbbd13e

Please report any issues.

[DirtBagXon]

Activate with the -gamepad argument.

[bigroy00]

Just a couple of points about setting up an xbox one joypad, which might help someone as confused as me :-)
The hypjsch tool needs restarting after registering either of the analog sticks (just keeps flickering between values around +-180)
The comments in the hypinput.ini suggest that you need to add one to the button number, but that didnt seem to be the case for me (?)
Here's my ini file:
hypinput.txt
Couple of questions:
Is it possible to assign more than one button/key to a single SDL2 code?
Also is it possible to have different ini files for different games?

Thanks for all you hard work!

[DirtBagXon]

"The hypjsch tool needs restarting after registering either of the analog sticks (just keeps flickering between values around +-180)" -

In the controllers I tested I did see some "flickering", it appeared to be wear in the analog sticks as far as I could tell. Others would be static once you released them. The values are coming from the underlying SDL events, so it would infer that these controllers are "noisy", but SDL has tolerances that should mean it's ok in the games.

"The comments in the hypinput.ini suggest that you need to add one to the button number, but that didnt seem to be the case for me (?)" -

The hypjsch tool, does this calculation for you (the +1). If you were using something like jstest then you would need to do the addition manually, but not when using hypjsch. Not certain how I can make it clearer in documentation without adding even more confusion, sorry.

Your hypinput.txt looks fine, if it works, then all is good.

"Is it possible to assign more than one button/key to a single SDL2 code?" -

There are three fields in against each key in the config file:

KEY_BUTTON1 = SDLK_LCTRL SDLK_RCTRL 2

The first two are for keyboard keycodes, so you can assign SDLK_LCTRL and SDLK_RCTRL for instance.
The third field is for the joystick button, you can have only one of these per key.

The exception to this rule is the first FOUR entries in the config file, in which you can assign the axis in the fourth field. In your config you can see these as +002 or -001 etc. These allow you to invert UP/DOWN or LEFT/RIGHT as can be preferential in the flight based games for instance.

"Also is it possible to have different ini files for different games?" -

Yes, use the -keymapfile argument and give it the name of a different config file in the $HOMEDIR of Hypseus. You should see an example called flightkey.ini in the repo for the reasons mentioned above.

[DirtBagXon]

 
There should be a more tolerant hypjsch v1.1 in the repo which now discards 'jitter':

https://github.com/DirtBagXon/hypjsch/releases/latest

Note:

This utility will provide adjusted config values automatically.
You do not need to perform the +1 addition to button/axis values, as described in the example config.