Joystick bug in both Windows and Linux version.

[HagbardCeline]

I've just installed a Linux box to be able to play 64bit, and had a faint hope that I also could escape the joystick issues in Windows KSP. The latter did not come true, except KSP does not randomize the the order of the joysticks at each start as it did in Windows.

I have a Thrustmaster T.Flight Hotas X and two Thrustmaster T.16000M connected. The Hotas works as expected, the problem is with the two T.16000M; KSP is not able to tell their axes apart.

Input-setup reacts to both T.16000M's axes when in assign mode. But the game itself reacts only to the axes of one of the two T.16000M. This is true for both Windows-32bit and Linux-64bit.

In Windows version there was one additional issue with the joystick-buttons where the input-setup seemed to be able to diffrentiate the buttons on the two identical joysticks, but in-game a function mapped to button1 of the first T.16000M would also trigger when pressing button1 of the second T.16000M.

And while I'm at it; TrackIR and 6dof can control the camera in the Space Center scene, joysticks can not.

And joysticks axis assignment are limited to camera pitch/jaw; technically not a bug but I had to mention it as relevant.

Edited July 3, 2015 by HagbardCeline

[T-Bouw]

It sounds like the 2 T.16000M's might have the same ID in their USB-protocol.

If I remember correctly, according to the USB-standard, USB-pheripherals should present unique ID's even when they are of the same model, in order for them to be told apart.

Does Windows see 2 separate joysticks?

[Alshain]

This is a known issue. I've seen it posted here before, KSP is looking at the name, not the ID. So any two devices of the same type will not be properly recognized by KSP. There is no solution I know of at the moment.

[HagbardCeline]

It sounds like the 2 T.16000M's might have the same ID in their USB-protocol.

If I remember correctly, according to the USB-standard, USB-pheripherals should present unique ID's even when they are of the same model, in order for them to be told apart.

Does Windows see 2 separate joysticks?

The id is not the problem. Neither Windows or Linux have any problem differentiating the two T.16000M's in joystick-config and other games.

[allmhuran]

It's not a name/ID thing either as far as I can see. I have a thrustmaster warthog HOTAS. JoyID shows that the two devices have different names.

I thought I'd try setting up the controls for KSP 1.04 without autohotkey to see if it would work. Prior to now I have always used autohotkey to fix KSP's joystick recognition.

On this occasion the controls appear to be registered correctly in the input setup. Buttons on the stick, for example, register as "Joystick1ButtonX", whereas on the throttle it lists them as "Joystick2ButtonX".

But it doesn't work in game. Some joystick buttons are doing things I have mapped to the throttle, others just don't work.

It seems unity just sucks for anything other than keyboard and mouse. Although a while back I believe there was a mod that fixed everything for KSP, not sure if it's up to date. In any case, maybe it's not a unity problem after all. But I've never, ever seen a Squad post about it.

Oh, and it is definitely not a hardware or OS issue, so I'd suggest fixing the thread tag.

Edited July 29, 2015 by allmhuran

[sal_vager]

Does the workaround in the sticky thread help with this?

[allmhuran]

I expect so, most device virtualization or device impersonation layers will help alleviate the problem. There are lots to choose from, ppjoy, vjoy, autohotkey, glovePIE/freePIE, etc. I've generally found autohotkey to be the most reliable since everything gets turned into keyboard input, and just about everything works correctly with keyboard input, plus you can write the code yourself so it's very powerful. For this reason I haven't checked whether ppjoy/vjoy etc work with KSP.

What I can add, which might be useful, is that switching the ID's of the devices using JoyID does not change the behaviour when launched in KSP. This is pretty unusual, and I can't explain why the in-game engine would behave differently from the input configuration screen.