Hey, i'm playing KSP on Arch Linux 64bit for a couple of days now. After Jebediah Kermans tragic death while testing the atmospheric beta version of my new moon lander, I decided it would be inevitable to take action and find a more efficient way to control the RCS boosters. When I finally attached my old and dusty Microsoft Sidewinder Precision Joystick, I was somewhat disappointed to realise KSP would not recognise its axes D:
Luckily I accidentally touched the thrust lever, when trying to assign one of the other axes and that one got recognised! When inspecting the settings.cfg after that, I found something like that:
AXIS_THROTTLE { name = Microsoft SideWinder Precision 2 Joystick 3 id = joy0.3 inv = True sensitivity = 1 deadzone = 0 scale = 1 group = 0 switchState = Any }
I guessed "joy0.3" would be some kind of device/axis identifier, so I tried and wrote slightly modified versions of this entry to the other axis definition sections in settings.cfg and it worked just fine:
AXIS_PITCH { name = Microsoft SideWinder Precision 2 Joystick 3 id = joy0.1 inv = False sensitivity = 1 deadzone = 0 scale = 1 group = 0 switchState = Any } AXIS_ROLL { name = Microsoft SideWinder Precision 2 Joystick 3 id = joy0.2 inv = True sensitivity = 1 deadzone = 0 scale = 1 group = 0 switchState = Any } AXIS_YAW { name = Microsoft SideWinder Precision 2 Joystick 3 id = joy0.0 inv = False sensitivity = 1 deadzone = 0 scale = 1 group = 0 switchState = Any }
So just in the case it was unknown until now: There seems to be a bug in the axis detection code in KSP settings, but - at least for some devices/setups/whatever - you can get your joystick working through manual settings.cfg modifications.
The Linux compatibility thread!
in KSP1 Technical Support (PC, unmodded installs)
Posted
Hey, i'm playing KSP on Arch Linux 64bit for a couple of days now. After Jebediah Kermans tragic death while testing the atmospheric beta version of my new moon lander, I decided it would be inevitable to take action and find a more efficient way to control the RCS boosters. When I finally attached my old and dusty Microsoft Sidewinder Precision Joystick, I was somewhat disappointed to realise KSP would not recognise its axes D:
Luckily I accidentally touched the thrust lever, when trying to assign one of the other axes and that one got recognised! When inspecting the settings.cfg after that, I found something like that:
I guessed "joy0.3" would be some kind of device/axis identifier, so I tried and wrote slightly modified versions of this entry to the other axis definition sections in settings.cfg and it worked just fine:
So just in the case it was unknown until now: There seems to be a bug in the axis detection code in KSP settings, but - at least for some devices/setups/whatever - you can get your joystick working through manual settings.cfg modifications.