overkill87

hi sal_vager, as per your suggestion I looked in settings.cfg, and although during the axis mapping the label changes accordingly (Joystick 0, Axis 5) and in settings.cfg it correctly saves the binding: AXIS_THROTTLE { PRIMARY { name = Joystick 0 axis = 5 inv = False sensitivity = 1 deadzone = 0.05 scale = 1 group = 0 modeMask = 7 } [...] under this section I don't see "joystick 0" INPUT_DEVICES { Joystick - HOTAS Warthog = 1 } but just my other joystick. I tried to add the line manually myself, but after I tried to run the game the file was back as it was before.

So... should I edit the name of the joystick? Funny thing is that if I open up settings.cfg and search for joystick 0 I find it correctly assigned to the throttle axis... I don't know what to do at this point, i'm just going to try random stuff related to the name of the joystick... If anyone has some suggestions, I'll try them all!

I second shotwn, unfortunately it doesn't work for me either. After pressing "accept", the settings still says "not found" anything I can do to debug this? I'm trying to look at the output_log.txt now... - - - Updated - - - Here's the last portion of the output_log... i tried to map 2 axis (0.2 and 0.5) but it still doesn't work... could it be a name issue? Names: 0: Joystick 0 1: Joystick - HOTAS Warthog (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.0 - Joystick 0; Axis 0, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.5 - Joystick 0; Axis 5, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.5 - Joystick 0; Axis 5, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.5 - Joystick 0; Axis 5, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) listen target set to: Joystick 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.0 - Joystick 0; Axis 0, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.2 - Joystick 0; Axis 2, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.2 - Joystick 0; Axis 2, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.2 - Joystick 0; Axis 2, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.2 - Joystick 0; Axis 2, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) listen target set to: Joystick 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.5 - Joystick 0; Axis 5, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [inputSettings]: listen target set to joy0.5 - Joystick 0; Axis 5, Device 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) listen target set to: Joystick 0 (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) Launcher here(in write): False (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Hello everyone! The 1.0.5 is out! Has anyone been able to test it out ye? Squad's mentioning in the changelog: Fix an issue with plugging/unplugging controllers breaking/losing settings. I really hope this is going to be fixed, although the bugabove is not the one that we're experiencing. Fingers crossed! I'll post something once I'm back home!

Yesterday's Devnote Tuesday read: Kerbal Space Program 1.0.5 I was so excited! They'll push a small patch before the update that solves some bugs, but unfortunately looking at the list of fixed bugs, this one is not present. Let's hope it's in the "more stuff" section.... I'll post an update as soon as it is out!

every week I also check the devs blog... apparently they're busy with upgrading to Unity 5.2, probably that's why they're not doing anything for this issue? I just hope that's going to fix it...

I'm having the grey accept button issue too. Win 8 x64. Before the 1.0 update everything was working just fine. I hope they're going to release a patch as soon as they can... playing the game is nice with the keyboard, but I've bought a joystick just for this game... and now it's there to gather dust...