Support any controller: PC controllers, Wheels, Dualshock 3, Dualshock 4, Dualsense (PS5), XBOX, XBOX360, XBOXONE, ...
Sys-con is a Nintendo Switch module that adds support for all HID and XID joysticks and gamepads to the Nintendo Switch. Only USB connection is supported (For Bluetooth connection prefer to use ndeadly's MissionControl)
Download the latest zip from the releases page. Extract it to your SD card root folder and boot/reboot your switch.
sys-con comes with a configuration folder located in /config/sys-con/
. It contains configuration for controllers (Button mappings, sticks configuration, triggers configuration, deadzones...).
The configuration is loaded in the following way:
[global]
section is only loaded once, when the switch boots, so if you want to apply a setting, you have to reboot the switch.When a new controller is plugged, the configuration is loaded in below order
[default]
section[VID-PID]
section[VID-PID]
contains a [profile]
, it will load the [profile]
then load [VID-PID]
.In other words, the loading order is: [Default]
[Profile]
[VID-PID]
.
If you want to override a setting for only 1 controller, it's adviced to change the configuration in [VID-PID]
in order to not impact others controllers
In case of issue, you can look at the logs in /config/sys-con/log.log
(On your SDCard).
The logs are automatically created with a log level equal to Info.
For more verbose logs, edit /config/sys-con/config.ini
and set:
[global]
log_level=0
Reboot the Nintendo Switch.
Important note: If you enable the trace(log_level=0
) or debug(log_level=1
) log level, sys-con will automatically increase the polling frequency to 100ms (for debug) and 500ms (for trace). This will add a lot of latency to your controller (this isn't a problem and is expected). So, if you want to press a button, you have to hold it down for 1 second. These log levels (trace and debug) cannot be used to play a game, they are for debugging purposes only.
A complete list of tested controller is available here
When a new controller is connected, sys-con tries to determine the best profile for this new controller. In most cases the dpad and joystick will work fine, the buttons may not be mapped correctly by default (and in rare cases the right stick may be reversed or not working). If this is the case, you will need to map the buttons yourself using the procedure below:
/config/sys-con/config.ini
and find your controller's [vid-pid]
section (most likely at the end of the file).
Note: A new section is automatically created if the controller is not known to sys-con. This means that your controller will most likely be the last one (at the end).Typical configuration will look like
[0810-0001]
B=1
A=2
Y=3
X=4
L=5
R=6
ZL=7
ZR=8
minus=9
plus=10
home=11
capture=12
rstick_left=-Rz
rstick_right=+Rz
rstick_up=+Z
rstick_down=-Z
Where ButtonName (A, B, Y, X ...) need to be assign to a ButtonID (1,2,3,4,5 ...) Now, according to what you found in step 2, you need to match ButtonName with ButtonID. For example, if you found that 'B' is reversed with 'A', just swap the ButtonID:
B=2
A=1
[0810-0001]
./config/sys-con/config.ini
on your switch sdcard and edit your controller's vid-pid section:[0810-0001]
B=3
A=2
Y=4
X=1
L=7
R=8
ZL=5
ZR=6
minus=9
plus=10
home=11
capture=12
rstick_left=-Z
rstick_right=+Z
rstick_up=+Rz
rstick_down=-Rz
Where ButtonID (1,2,3,4, ...) is the key ID noted in step 7. Note: Depending to the controller, this windows procedure might not works. If the mapping is incorrect, switch to Method 1
List of possible mappable switch buttons:
lstick_left=
lstick_right=
lstick_up=
lstick_down=
rstick_left=
rstick_right=
rstick_up=
rstick_down=
B=
A=
Y=
X=
L=
R=
ZL=
ZR=
minus=
plus=
lstick_click=
rstick_click=
dpad_up=
dpad_down=
dpad_left=
dpad_right=
capture=
home=
simulate_home=
simulate_capture=
List of possible values:
Additionnaly, you can configure deadzone and/or factor for every analog.
deadzone_x=20
deadzone_y=20
deadzone_z=20
deadzone_rz=20
deadzone_rx=5
deadzone_ry=5
deadzone_slider=20
deadzone_dial=20
factor_x=100
factor_y=100
factor_z=100
factor_rz=100
factor_rx=100
factor_ry=100
factor_slider=100
factor_dial=100
All these values are in percentages Typical deadzone range: 0% to 30% Typical Factor range: 100% to 150%
For common issues a troubleshooting guide is available: Troubleshooting
All contributions are welcome, you can be a simple user or developer, if you did some mapping work in the config.ini or if you have any feedback, feel free to share it in Discussions or submit a Pull request
Don't download the project as ZIP as it will not copy submodules properly, prefer a git clone:
git clone --recurse-submodules -j8 https://github.com/o0Zz/sys-con.git
Like all other switch projects, you will need devkitA64 set up on your system. (Direct link for windows https://github.com/devkitPro/installer/releases/tag/v3.0.3)
Open MSYS2 console from devkitA64 and type below commands:
pacman -S switch-libjpeg-turbo
make -C lib/libnx install
If you have Visual Studio Code, you can open the project as a folder and run the build tasks from inside the program. It also has Intellisense configured for switch development, if you have DEVKITPRO correctly defined in your environment variables.
Otherwise, you can open the console inside the project directory and use one of the following commands:
make -j8
: Build the projectmake clean
: Cleans the project files (but not the dependencies).make mrproper
: Cleans the project files and the dependencies.Output folder will be there: out/
For an in-depth explanation of how sys-con works, see here.
In order to debug the applicaiton, you can directly refer to the logs available there: /config/sys-con/log.log
.
Texita For his contribution in controllers testings and mappings
If you want to support this work