Joystick mapping error

[m1sz]

I've been waiting for the 1.1 release, hoping it will fix the bugs with the joystick mapping for Saitek users (or as far as I know, any joystick which uses 2 different USB [throttle and stick, for example]).

I was very happy to see the game recogniced joystick0 and joystick1, but when I try to map one of the axis, It always binds it to the joystick0, despite recognising both of them. I made a quick video to show what I'm talking about. Windows 7 64bits that recognise both devices as separated ones. In the config.ini it only recognises one of them: 

INPUT_DEVICES
{
    Saitek Pro Flight X-55 R. = 0
}

But as you can see, when I try to map the axis to my stick, it recognises the joy1.1, but then it binds it to joy0.1 (axis 1 of my throttle). This doesn't look right at all.

 

 

More information: Button mapping works. It recognises 2 joysticks as joysticks 1 and 2, and they appear like this "joystick1button0" and "joystick2button0" in the config.ini, and works as intended.

Thanks for the help

Edited April 20, 2016 by m1sz
better explanation of what you see in video + more information

[[email protected]]

I am having this problem as well.  In previous versions I used the Advanced Fly By Wire mod as.  However this mod hasn't been ported to 1.1 yet.  I would prefer to be able to play KSP unmodified.

[Frankenchokey]

Are both your throttle and stick listed separately in the settings.cfg file?

I did a quick test using both my F710 gamepad and T16000m, and they assigned the axes correctly. 

However, those two controllers have different names in the config file, and I seem to recall there being some issue with longer, similar, names being truncated and causing confusion. 

For example both  "Saitek Pro Flight X-55 Rhino Joystick" and  "Saitek Pro Flight X-55 Rhino Throttle" ( I don't know the exact names) both showing up as  "Saitek Pro Flight X-55 R" in truncated form.

Though, your buttons work as mentioned so maybe that isn't it. 

 

[m1sz]

Yes, as far as I could read over the internet (including KSP bug tracker) it's an issue with Unity..., KSP only lists one of my two devices, and therefore thinks they are the same (same name in the first 10 characters). I've been messing arround trying to change their names in the registry with no luck (Seems like they have internal names that I cannot rewrite, and managed to chance their windows name but KSP still recognised them with the original one). Biggest thing is that when setting the input, KSP knows it's "joy1axis1" or "joy0axis1" if it's throttle or stick, so it KNOWS there are two, but then, it cannot translate that info to the mapping.

Even if it's UNITY's flaw, it's notorious how a mod called Advanced Fly By Wire fixes all the problems (apart from other good things it provides), and even after 1.1 I cannot use my Saitek in KSP (advanced joystick with a space simulator). 

Anyway, and as I said, the fact that the game knows when I'm moving "joy1" or "joy0" makes me think that there's something pretty wrong with the mapping. Before it would only recognise one joystick. (I think this changed since 1.0, last version I played before coming back)

[Frankenchokey]

Just out of curiosity, would going into the config file and manually changing the axis to joy1.1 do anything?

 

It's probably more of a windows thing, but the other problem I have continually run into is the various input devices changing device Id's.

It would be nice if something like Advanced Fly by Wire's solution could be implemented in the base game though.  

[m1sz]

Nope, doesnt work either. Was the first thing I tried. First, add under input devices another one. Then, tried setting it but it can't work, because in the config.ini it appears with the full name of the device. In this case,   Saitek Pro Flight X-55 R , so it doesn't make any difference :(. Really, it's a stupid bug that doesn't make sense to me.

 

Buttons appear like this:

BRAKES
{
    primary = B
    secondary = Joystick1Button5
    group = 0
    modeMask = -1
    modeMaskSec = -1
}

 

Axis appear like this:

AXIS_PITCH
{
    PRIMARY
    {
        name = Saitek Pro Flight X-55 R.
        axis = 1
        inv = False
        sensitivity = 1
        deadzone = 0.05
        scale = 1
        group = 0
        modeMask = -1
    }

 

That may be the reason of why buttons works but axis don't. 

[HagbardCeline]

I got the same problem with my dual Thrustmaster T.1600M setup, really hope they can fix this.

[Parhelionlens]

I got my Saitek Rhino X-55 a few months after getting KSP, It's always had this problem and frankly I stopped playing waiting for them to fix this. I'd love to come back to the game, especially seeing the new release but its frustrating to have this unrealized potential because of a seemingly simple bug. I wish I had a solution, hopefully someone out there can help us!

[sal_vager]

8 hours ago, Parhelionlens said:

I got my Saitek Rhino X-55 a few months after getting KSP, It's always had this problem and frankly I stopped playing waiting for them to fix this. I'd love to come back to the game, especially seeing the new release but its frustrating to have this unrealized potential because of a seemingly simple bug. I wish I had a solution, hopefully someone out there can help us!

Have you actually tried your stick in 1.1.2 ?  Because this was addressed and tests with a Saitek X52 showed it was working.

[Parhelionlens]

1 hour ago, sal_vager said:

Have you actually tried your stick in 1.1.2 ?  Because this was addressed and tests with a Saitek X52 showed it was working.

I just uninstalled and started a fresh, non-modded 1.1.2 and its working brilliantly! Still have to back all the way out of a game to change controls, but it works!

[sal_vager]

2 hours ago, Parhelionlens said:

I just uninstalled and started a fresh, non-modded 1.1.2 and its working brilliantly! Still have to back all the way out of a game to change controls, but it works!

Whoop!  You had me worried it was still broke