roothorick

Partial workaround: In jstest-gtk, deliberately miscalibrate the throttle to be off by one, so center reads one step negative (which is "up" because the axis is inverted in hardware). KSP then "calibrates" this as the center, so it picks up the bottom position as past the throttle's range. That will actually stop the engines. But now you don't get 100% throttle.

Ubuntu 16.04 I checked my calibration, throttle moves 32767 to -32767 (bottom to top) just like it should be. But the very bottom end of the throttle's range still registers as the engines being slightly on. I have to manually kill the throttle by button/key and be very very careful not to bump the throttle lever. Sensitivity and deadzone affect the movement curve but 32767 is still not-quite-0. I wonder if -32767 doesn't quite hit 100% either.

The launcher opens at the top of the secondary (left) monitor, and due to its narrow size (1680x1050 LCD rotated 90 degrees) is cut off on the left. The window itself is truncated and remains so when moved to the primary monitor, and cannot be resized, so it's just stuck like this. Primary display is at +1050+600 and has the primary flag in the XRandR layout. Linux x64 site direct Ubuntu-GNOME 16.04.3 LTS GeForce GTX 1080Ti binary driver 390.12 Primary: AOC G2460PF Secondary: Samsung 2243BWX

I think I found a better yet fix: Delete all .cfg files in the main directory, and all .cfg.bak files in Launcher_data/. Then launch KSP.exe directly, i.e. NOT through the launcher. For me, the first boot after this, the loading screen was slightly messed up, like it sort of remembered the settings but not really. It was back to normal the second boot. -E- But NOT physics.cfg as that breaks things.

The same problem as here but x64 and completely unmodded install. (I am jonesing SO hard for editor extensions but it's not available for beta yet ) The workaround given in that thread does not work; all values in the save were already at 0 and the game seems to be ignoring them.