PS4 controller on linux (1.1.3)

[Snarfster]

Hello all,

I've used my PS4 controller with KSP before, it's great to fly aircraft.

For some reason I can't get it to show up in the settings in 1.1.3. It is detected, however it's not working.

When running the 64 bit linux client from the command line, this is what I see:

Set current directory to /home/snarf/Games/KSP_linux
Found path: /home/snarf/Games/KSP_linux/KSP.x86_64
Mono path[0] = '/home/snarf/Games/KSP_linux/KSP_Data/Managed'
Mono path[1] = '/home/snarf/Games/KSP_linux/KSP_Data/Mono'
Mono config path = '/home/snarf/Games/KSP_linux/KSP_Data/Mono/etc'
displaymanager : xrandr version warning. 1.4
client has 4 screens
displaymanager screen (0)(DVI-I-1): 1920 x 1080
displaymanager screen (1)(HDMI-0): 1920 x 1080
Using libudev for joystick management


Importing game controller configs
Found /dev/input/event19
Mapping raw axis 0 to 0
Mapping raw axis 1 to 1
Mapping raw axis 2 to 2
Mapping raw axis 3 to 3
Mapping raw axis 4 to 4
Mapping raw axis 5 to 5
Sony Computer Entertainment Wireless Controller: Mapping b1.0 to b0
Sony Computer Entertainment Wireless Controller: Mapping b2.0 to b1
Sony Computer Entertainment Wireless Controller: Mapping b8.0 to b6
Sony Computer Entertainment Wireless Controller: Mapping h0.4 to a7
Sony Computer Entertainment Wireless Controller: Mapping h0.8 to a6
Sony Computer Entertainment Wireless Controller: Mapping h0.2 to a6
Sony Computer Entertainment Wireless Controller: Mapping h0.1 to a7
Sony Computer Entertainment Wireless Controller: Mapping b12.0 to b8
Sony Computer Entertainment Wireless Controller: Mapping b4.0 to b4
Sony Computer Entertainment Wireless Controller: Mapping b10.0 to b9
Sony Computer Entertainment Wireless Controller: Mapping a3.0 to a2
Sony Computer Entertainment Wireless Controller: Mapping a0.0 to a0
Sony Computer Entertainment Wireless Controller: Mapping a1.0 to a1
Sony Computer Entertainment Wireless Controller: Mapping b5.0 to b5
Sony Computer Entertainment Wireless Controller: Mapping b11.0 to b10
Sony Computer Entertainment Wireless Controller: Mapping a4.0 to a5
Sony Computer Entertainment Wireless Controller: Mapping a2.0 to a3
Sony Computer Entertainment Wireless Controller: Mapping a5.0 to a4
Sony Computer Entertainment Wireless Controller: Mapping b9.0 to b7
Sony Computer Entertainment Wireless Controller: Mapping b0.0 to b2
Sony Computer Entertainment Wireless Controller: Mapping b3.0 to b3
Assigning joystick 1

However, in the settings dialog, it doesn't show up.

I'm using the controller with a USB cable.

Does anyone know to happen a solution to this?

Thanks!

Just an addition. In the settings.cfg, this is shown:

INPUT_DEVICES
{
	Sony Computer Entertainment Wireless Controller = 0
}

 

[sal_vager]

Hi @Snarfster, have you tried restarting KSP with the controller still attached?

Everything should be working except binding the triggers as buttons, as they are axis they can only be used for axis bindings.

Here's my settings file with the PS4 controller thumbsticks bound to pitch, roll, yaw and throttle.

[Snarfster]

Hi @sal_vager, I tried that several times. Tried two different controllers as well.

There's one thing I haven't tried yet, booting up with the controller connected (via USB). Once I get home from work, I'll give that a shot.

Should that not work, is there a way to get debugging information?

[sal_vager]

25 minutes ago, Snarfster said:

Hi @sal_vager, I tried that several times. Tried two different controllers as well.

There's one thing I haven't tried yet, booting up with the controller connected (via USB). Once I get home from work, I'll give that a shot.

Should that not work, is there a way to get debugging information?

The only information would be in the KSP.log, Player.log and settings.cfg, as your log already shows the controller we know it was detected, but the controller must be present when KSP starts for it to work correctly.

I assume you are using the axis bindings part of the settings screen when you try to bind the controllers thumbsticks? They will not be detected when binding to the pitch, roll or yaw keybindings.

Also make sure you have calibrated the controller, js-test can do this on Debian based distros.

[Snarfster]

It seems I made a classic user error. For some reason I expected to see the PS4 controller under the controllers tab.

When I assigned the axis binding, it worked. Quite a humbling moment.

Thanks and I am sorry for wasting your time.