Logitech Extreme 3D Pro Axis Bindings Freeze

[dx33]

KSP Version 1.0.0.830

Upon upgrading to 1.0 all of my axis bindings reset, and when I go to assign them in Settings>>Control Mapping>>Flight>>Axis Bindings, it will not allow me to accept a new binding

It recognizes the joystick and the axis I am using (Logitech Extreme 3D Pro), but the accept button does not work, and after I click cancel the settings screen becomes non-responsive.

This is the screen where I can progress no further:

[Frankenchokey]

I had this problem trying to set up my gamepad axis, and was able to solve it be deleting the settings.cfg file in the main KSP directory, then relaunching the game.

[dx33]

Thanks for the solution! Definitely works now.

[Grande Rojo]

Didn't work for me. I deleted the file and restarted. Axes still don't work. I have a CH products HOTAS setup and what is weird is that in the config file, not all of my devices enumerate. Even though I have a couple devices (stick, rudder, throttle), the only input device line in the cfg is:

INPUT_DEVICES

{

Control Manager ID #00 = 0

}

and all axes map to that. As of right now i can't get any axes to work at all. Worked great in 0.90 and on all other games.

[paralipsis]

Posting to add that I'm having this problem. While deleting settings.cfg partially works, it's not a complete solution.

I'm using a Thrustmaster HOTAS Warthog and Saitek Pro Flight Combat Rudder Pedals. My main problem arises when I use the Thrustmaster TARGET GUI, which creates a single virtual controller out of the throttle and stick of the HOTAS setup. If I have this virtual controller set up, then none of my axis mappings from that device will be accepted by KSP.

While I can map axes from the stick and throttle if they aren't mapped to the virtual controller by the TARGET software, that leaves me with significant difficulties mapping any button commands. KSP won't accept any button/hat/switch inputs from either device. I can manage a partial work around of this using Xpadder, but that doesn't handle the throttle switches very well at all.

If the controller name issue was resolved, then I could use the TARGET software, which would allow me to configure all of my controls as I would like.

To be clear, I can assign axis mapping in KSP to the Saitek rudder pedals, and to the Thrustmaster stick and throttle when they are separate devices, but I can't assign any button mappings to the stick or rudder if they are separate USB devices. The pedals have no buttons to map. When the two Thrustmaster controllers are assigned to a single virtual controller through Thrustmaster's TARGET software, then I get the problem repeatedly reported here; axes will be recognised by KSP, but they can't be saved.

Also, any time I want to try a different controller config (e.g. TARGET on/off or additional devices plugged in or unplugged), then I have to delete the settings.cfg file and start again with my config from scratch. Otherwise I get the other oft reported problem in this thread and the axis assignment window doesn't come up at all.

[bn880]

On 10/30/2015 at 1:56 AM, paralipsis said:

Posting to add that I'm having this problem. While deleting settings.cfg partially works, it's not a complete solution.

I'm using a Thrustmaster HOTAS Warthog and Saitek Pro Flight Combat Rudder Pedals. My main problem arises when I use the Thrustmaster TARGET GUI, which creates a single virtual controller out of the throttle and stick of the HOTAS setup. If I have this virtual controller set up, then none of my axis mappings from that device will be accepted by KSP.

While I can map axes from the stick and throttle if they aren't mapped to the virtual controller by the TARGET software, that leaves me with significant difficulties mapping any button commands. KSP won't accept any button/hat/switch inputs from either device. I can manage a partial work around of this using Xpadder, but that doesn't handle the throttle switches very well at all.

If the controller name issue was resolved, then I could use the TARGET software, which would allow me to configure all of my controls as I would like.

To be clear, I can assign axis mapping in KSP to the Saitek rudder pedals, and to the Thrustmaster stick and throttle when they are separate devices, but I can't assign any button mappings to the stick or rudder if they are separate USB devices. The pedals have no buttons to map. When the two Thrustmaster controllers are assigned to a single virtual controller through Thrustmaster's TARGET software, then I get the problem repeatedly reported here; axes will be recognised by KSP, but they can't be saved.

Also, any time I want to try a different controller config (e.g. TARGET on/off or additional devices plugged in or unplugged), then I have to delete the settings.cfg file and start again with my config from scratch. Otherwise I get the other oft reported problem in this thread and the axis assignment window doesn't come up at all.

Same problem here, TARGET is totally unsupported by KSP now, while it used to work with earlier versions of KSP.