Page MenuHomeFeedback Tracker

Linux 1.42: Saitek X52 Pro Joystick cannot be mapped correctly using Steam Big Picture Mode
New, WishlistPublic


Using the Linux 1.42 build, my Saitek X52 Pro joystick cannot be mapped correctly using Steam Big Picture mode.

  1. First, Steam Big Picture mode controller configuration and settings does not auto detect the controller.
  1. Entering the Saitek joystick configuration manually into Steam's configuration file results with some axis improperly working, as well as buttons.

"SDL_GamepadBind" "03000000a30600006207000011010000,Saitek Saitek X52 Pro Flight Control System,platform:Linux,rightx:a0,righty:a1,righttrigger:b15,leftx:a2,lefty:a5,"


Legacy ID
Additional Information

I have documented my efforts to the following page.

Bohemia Interactive ARMA 3

Event Timeline

rogerx edited Additional Information. (Show Details)Oct 22 2015, 3:24 PM
rogerx set Category to Controls.
rogerx set Reproducibility to Always.
rogerx set Severity to None.
rogerx set Resolution to Open.
rogerx set Legacy ID to 4199271776.May 8 2016, 12:59 PM
rogerx added a subscriber: rogerx.EditedDec 22 2016, 1:57 AM

This bug still persists within Linux ports 1.64 version.

No workaround exists.

Almost all users are vacant of microphone and joystick usage making the Linux port undesirable to play or work in. (Shrugs.)

Similar to being alive, but joyless and living without a penis.

Within the last few versions release, I lost all detection of the Saitek joystick within Steam Big Picture mode, but maybe due to not plugging the joystick into the main computer hub. I doubt this though, as the joystick is detected and works just fine within Linux.

$ ls -alh /dev/input/js0
crw-rw-r-- 1 root input 13, 0 2016-12-21 08:08 /dev/input/js0

Although I noticed my $USER was not within the input line of /etc/group file (eg. input:x:987:roger), however I still have read permissions... so ... I'll update this if for some reason adding my $USER to the input line helps, but doubtful as of this post. Seems the Saitek joystick device ID within the previously mentioned config file is not being used anymore.

This comment was removed by rogerx.