1.0 Bug - Config->Control input: (Un)Ticking boxes doesn't work

[Kowgan]

Just passing by to report this bug, as it can bring to several other problems.

Whenever you try rebinding a key, the game gives you three additional options, asking you on which flight modes do you want that keybind to work: Staging, Docking (Translation) and Docking (Rotation).

Problem is, (un)ticking those boxes have no effect at all. They will always go back to their default configuration, as soon as you hit "Accept".

Take care.

[sal_vager]

I think that's just the graphic, can you verify that it still assigns them to the deselected options please

[Kowgan]

Unchecked the boxes, accepted and went testing. Confirmed: That's not just graphics.

I have both "Launch/Stages" and "Switch Translation/Rotation" commands bound to Spacebar.

- Loaded a craft;

- Switched to Docking mode, Translation activated;

- Pressed space;

- Stage occurs, and Translation mode switches to Rotation.

[sal_vager]

Hmm, can you please try clearing the assignment and then pressing space and changing the lit options, this may be a Windows issue as I was able to redefine on Linux.

[Kowgan]

I've followed your instructions, and tried a few other ways as well. Unfortunately, got no luck here.

Would someone else using Windows be able to replicate that bug as well?

[sal_vager]

Most likely, we need another Windows user in here.

[Cerber]

i'm using windows too, and it doesn't work for me neither

on a wider note, i can't change any keybind at all

it says "press the key" but when i do nothing changes

[Kowgan]

Weird, I can change keybinds normally.

Have you tried clearing the key and then changing it?

[AlexinTokyo]

Another Windows user here (Win7 x64).

I also am unable to rebind keys from the settings menu (primary, secondary, new binding, change binding, all fail).

I can clear a binding using the "Clear Assignment" button, but cannot then re-assign a key.

Editing the settings.cfg file does work as expected.

Please let me know if any further information is required.

EDIT: Reinstalling the game appears to have resolved this issue for me.

Edited April 29, 2015 by AlexinTokyo
Additional info

[ChronosWS]

Also Windows user here, and seconding that reinstalling the game seems to have fixed the issues attempting to bind joystick axes (Thrustmaster HOTAS + Saitek Pedals in my case)