Linux
This section contains information about Kerbal Space Program on operation systems based on GNU/Linux.
Contents
Running on non-English localized systems
Source of the problem
KSP doesn't work on some localization, because English uses decimal fractions with a decimal point (3.1415
), and other languages use a comma (3,1415
). As a result of this, the Unity engine is attempting to use one method for writing and another method to read.
For starting KSP in English localization use this command line:
LC_ALL=C ./KSP.x86
- for the 64-bit version:
LC_ALL=C ./KSP.x86_64
The command lines can be used in console, placed in shell file, in the command or in the command line of menus. For the Steam version the file name has to be replaced with the %command%:
<code>LC_ALL=C %command%
- for the 64-bit version:
LC_ALL=C %command%_64
(See the picture on the right)
Source of the problem
The game needs Arial and Arial Black fonts to be installed.
Solution
In case of Debian based systems (Ubuntu, Mint) install the "Microsoft TrueType core fonts" (ttf-mscorefonts-installer) package (or something similar), in case of AchLinux "ttf-ms-fonts" package, and so in case of other distros too.
Since KSP 1.1
Under Linux (all distributions) the Unity game engine encounter an occasional compatibility issue that cause few menus (including settings panel) to not show text at all under certain screen resolution.
Solution
You can try to launch the game with different screen resolution by manually editing the settings.cfg file of KSP (seems to work with few config) this file can be found at the root directory of KSP.
A solution that work with any screen resolution is to add the -force-glcore
as launch option. Under Steam go to: Library -) right click on KSP -) Proprieties -) Set up launch options and add -force-glcore
The game engine will try to run the game with the best OpenGL version possible and all available OpenGL extensions as explained in the Unity 3D documentation
With this option enabled you may encounter shadow glitches, try few different settings in-game in the setting panel to resolve the problem.
This issue has been reported but it seems that it will not be fixed until the next game engine release.
Text is unreadable, letters are replaced by squares
Source of the problem
If you have an ATI graphic card, you need to enable AMD compatibility mode. This is not a Linux-specific issue.
Solution
You have two ways to handle this problem :
- From the settings in KSP launcher, select "advanced" then check "Run in AMD compatibility mode".
- From Steam: go to Library, right click on KSP, select "Properties", click on "Set launch options..." and add
-force-gfx-st
Mods
Source of the problem
There are no problems. Mods are usually compatible with each other, and you do not have to pay special attention of compatibility of mod.dll files.
64-bit version
Source of the problem
KSP can sometimes run out of memory, especially if you use many mods; the 32-bit application cannot handle memory over 4GB, and the 64-bit Linux version has a small bug, which can be fixed before use.
Solution
This works only on a 64-bit system. The command uname --hardware-platform
replies x86_64
on 64 bit systems.
In the root directory is the executable named KSP.x86_64
which needs to be patched. First you need to change to the directory using cd depending on your installed directory. Two bytes need to be set to 0, depending on the installed version:
Version | Positions |
---|---|
0.24 — 0.24.2 | 0099f587 and 0099f58c
|
0.23.5 | 090f377 and 090f37c
|
0.23 | 838077 and 83807c
|
For example for version 0.24.2 it looks like:
echo "0099f587: 00" | xxd -r - KSP.x86_64 echo "0099f58c: 00" | xxd -r - KSP.x86_64
Automatic script
Alternatively based on ksp_installer by Voidi, the following script will automatically search for the erroneous position and fix it. It'll also backup the original file as KSP.x86_64.unpatched
if anything has gone wrong.
#!/bin/sh position1=$(echo "obase=16; $(perl -n0777e 'print pos()-1,"\n" while /\x01\x00\x00\x00\xB8\x01\x00\x00\x00\xC3\x41\x56\x41\x55\x49/g' "./KSP.x86_64") - E" | bc) if [ $position1 != "-E" ] then echo "Patching Segfault out of the Rockets ..." cp -n "./KSP.x86_64" "./KSP.x86_64.unpatched" position2=$(echo "obase=16;ibase=16; $position1 + 5" | bc) echo "$position1: 00" | xxd -r - "./KSP.x86_64" echo "$position2: 00" | xxd -r - "./KSP.x86_64" else echo "This seems to be not a vanilla KSP executable" fi
From now, only your hardware limits the usable memory. Install as many mods as you wish.
64-bit on Steam
Source of the problem
Steam installs both 32- and 64-bit versions of KSP, but even on 64-bit systems launches the 32-bit by default.
Solution
Tell Steam to launch the 64-bit version instead by editing the launch parameters. Right-click on the game in your Steam library listing and go to "properties". In the "General" tab (which should be the one that opens by default), click the "Set launch options..." button. In most cases, this box will be empty - insert the text %command%_64
and click OK. If there is text in the box (because you've added flags, you're using Bumblebee, or you followed the instructions above for non-English localised systems), you'll need to insert the same text at the start (if %command%
doesn't already appear) or change %command%
to %command%_64
(if it does).
Joystick
The joystick has to work by default. If your joystick is not available for the game, check the availability for Linux: ls -l /dev/input/js* /dev/js*
. If the command is not replied with any file, that means there is no driver installed. If you have the driver install it, for example in case of Fedora install kernel-modules-extra
package. If the driver is installed, plug in the joystick, and try again!
External Links
https://wiki.archlinux.org/index.php/Kerbal_Space_Program - KSP on Archwiki