Joystick bound, but unplugged results in very slow keyboard traverse

[oo6oo7]

This is something I'd noticed before the new "No Joystick"/"With Joystick" options, but now that those options exist this bug comes up readily. What happens is that if you set turret traverse (or anything that has a traverse) to your keyboard (WASD, e.g.) and then go to traverse that turret, the traverse rate is extremely slow. I first noticed it when I would unplug the joystick on my main machine and forget to plug it back in and play the game. Once I had the joystick back in, things were fine. The same thing happens even if you never had a joystick plugged in to begin with. It's only until you clear the bindings under the "With Joystick" setting and replace them with the Mouse axis that the problem goes away. Ironically, if you try to just clear the bindings on the "With Joystick" setting, save, and go to the "No Joystick" setting to use, the traverse axis on that page is cleared out, as well. You have to do all your bindings on the "With Joystick" page in order to have your keyboard traverse work properly.

To summarize, if you try to traverse something with the keyboard when that something has a joystick mapped to its axis, and no joystick is plugged in, then the traverse rate from the keyboard is very slow.

A related bug is that if you clear an axis or keybinding on one of the pages (No Joystick or With Joystick), it clears it on the other page, as well. I'm not sure if that was intentional, but I wanted to mention it anyhow. You can reset the bindings to default and they will stay dichotic, but any custom keybindings will be mirrored on both pages.

Not a huge bug, because it can be worked around, but it might be frustrating to those who don't have a joystick and wouldn't think to try putting all of their bindings on the "With Joystick" page. The purpose of having an axis and keyboard binding is to use coarse corrections with the keyboard (such as rotating your AA guns on a DD 180 degrees) and then use the axis (In this case, with mouse input) to do the actual aiming. Hopefully that all makes sense, let me know if it needs further explanation, cheers!