Rocket Taco

That workaround is to a different issue. The bug most users in this thread are encountering is related to joysticks without a name string being given a default name, which is not entered into the dictionary used to look up joystick handles making any attempt at accessing that stick fail. No workaround posted yet has solved this, and almost certainly won't be able to without a fix.

That report was closed because the reporter was not having issues. I have another issue open (didn't find the first one when I looked before) but no one's touched it. I'm pretty sure I know what the bug is, but not so sure if it's in KSP or Unity3D (and thus out of squad's hands).

Confirmed, behavior on 1.0.3 is identical.

This seriously needs to be hotfixed. I've tested this extensively and here's what I know: -I have three controllers, a HOTAS Cougar, a Logitech PS3/USB Pad, and a Logitech G13. The G13 comes up with no name, ie "Joystick 1" and is the only one affected. I suspect this is related. -Attempting to bind an axis which is unbound or bound to a working pad brings up the binding pop-up -The pop-up detects the axis correctly -Canceling the pop-up at any point prior to clicking accept leaves everything working as it was -Clicking accept does not close the popup -Canceling the pop-up after clicking accept causes any further attempt to bind that axis to grey out the screen as though the pop-up had appeared, but it does not appear -Attempting to bind the axis by editing the config file causes the stats tracking request to show up on game start as though the settings had been nuked, but the axis binding menu still grays out without showing the popup Edit: Yeah, I think it's related to stick names. This shows up when the screen goes grey: [EXC 12:32:26.483] KeyNotFoundException: The given key was not present in the dictionary. System.Collections.Generic.Dictionary`2[system.String,System.Int32].get_Item (System.String key) InputDevices.GetDeviceIndex (System.String deviceName) AxisBinding_Single.Load (.ConfigNode node) AxisBinding.Load (.ConfigNode node) InputSettings.ListenToAxis (.AxisBinding target, Boolean primary, System.String actionName) InputSettings.DrawAxisBinding (System.String name, .AxisBinding axisRef) InputSettings.drawInputPage ( page) InputSettings.DrawSettings () SettingsScreen.draw (Int32 d) UnityEngine.GUI.CallWindowDelegate (UnityEngine.WindowFunction func, Int32 id, UnityEngine.GUISkin _skin, Int32 forceRect, Single width, Single height, UnityEngine.GUIStyle style) That should be more than enough for your bug hunters to track this down. Please don't make this wait for a major release!