3.9.2 Connect Xbox Wireless Controller with Bluetooth.3.9.1 Connect Xbox Wireless Controller with usb cable.3.9 Xbox Wireless Controller / Xbox One Wireless Controller.3.8.1.2 Mimic Xbox 360 controller with other controllers.3.5 iPEGA-9017s and other Bluetooth gamepads.3.4.2 Dolphin (GameCube controller emulation).3.4.1.4 Using hid-nintendo with SDL2 games.3.4.1.3 Using hid-nintendo Pro Controller with Steam games (with joycond).3.4.1.2 Using hid-nintendo Pro Controller with Steam games (without joycond).3.4.1 Using the kernel Nintendo HID driver.3.4 Nintendo Switch Pro Controller and Joy-Cons.2.5 Remapping of Gamepad buttons and more.2.3 Disable joystick from controlling mouse.

2.2.5 Configuring curves and responsiveness.2.2 Setting up deadzones and calibration.1.1 Loading the modules for analogue devices.SDL2 supports only the new evdev interface. While SDL1 defaults to evdev interface you can force it to use the old Joystick API by setting the environment variable SDL_JOYSTICK_DEVICE=/dev/input/js0. Most new games will default to the evdev interface as it gives more detailed information about the buttons and axes available and also adds support for force feedback. Symbolic links to those devices are also available in /dev/input/by-id/ and /dev/input/by-path/ where the legacy Joystick API has names ending with -joystick while the evdev have names ending with -event-joystick. dev/input/jsX maps to the Joystick API interface and /dev/input/event* maps to the evdev ones (this also includes other input devices such as mice and keyboards). Linux has two different input systems for Gamepads – the original Joystick interface and the newer evdev-based interface. (Discuss in Talk:Gamepad#Joystick API vibration support) Reason: Need info about differences between API, how to switch between them.

Joy of creation steam