Jump to content

Karatorian

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by Karatorian

  1. Thanks for the feedback. I generally only buy games with explicit Linux support, since that's the best indicator that the devs might actually care about Linux. Sad that that isn't the case here.
  2. I have a Logitech X3D (aka Extreme 3D Pro) that I bought to use with KSP. Barring a few throttle bugs, it used to work perfectly. Now it doesn't seem to work at all. I think the problem started when Steam added gamepad support, but I can't be positive. All I know is that it worked, I didn't play KSP for some time and then it didn't work. The stick itself works fine. Both jstest-gtk (a standard Linux joystick config program) and Steam's gamepad configurator can see the stick and all it's axes and buttons. When I first tried to get it working again, some of the buttons and most of the axes wouldn't register in the input settings menu. However, once I figured out that Steam's gamepad mapping was part of the problem and configured my stick in Steam (to a reasonable approximation of a Gamepad), all the buttons and axes worked in KSP's settings menu. Mapping buttons worked in the menu and even worked in game. Mapping axes doesn't seem to work at all. When I move the axes in the settings menu, it detects them, but I don't think it saves them. In the button you click on to map them it just says "<". And when you click on it, it says the current mapping is "None", even after you just set it. In any event the axes in game don't do anything. All of this was with Steam Controller Configs disabled. Thinking that might be the problem, I enabled Steam Controller Configs for generic gamepads. However, the official settings aren't really usable with a flight stick. The analogs are mapped like buttons and there's no throttle axis (or any axis really) support. I tried to modify the settings to map the main stick to left joystick and the throttle and twist to right stick (and/or the trigger axes) in hopes that that'd solve my problem. But it didn't. I still couldn't get any analog controls to actually work. I had the same problem with them basically not actually saving in the menu, even though the game detected them. Thinking Steam was the problem, I launched KSP without Steam. The launcher detected my stick no problem: Importing game controller configs /dev/input/js1: driver version: 2.1.0 (20100) /dev/input/js1: fd 4, buttons 12, axes 6, name Logitech Logitech Extreme 3D /dev/input/js1: axis 0: raw 0, mapped 0.000000 /dev/input/js1: axis 1: raw 0, mapped 0.000000 /dev/input/js1: axis 2: raw 0, mapped 0.000000 /dev/input/js1: axis 3: raw 0, mapped 0.000000 /dev/input/js1: axis 4: raw 0, mapped 0.000000 /dev/input/js1: axis 5: raw 0, mapped 0.000000 Assigning joystick 1 Then it complained about not finding Steam, but launched the game just fine. However, at this point, the game didn't see the joystick at all. When I tried to configure it, it didn't respond at all. And that's when I gave up. I tried Googling and searching here, but I didn't find much? Are analog controls just broken now?
×
×
  • Create New...