The Linux Thread!

[sal_vager]

Updated 31st March 2017

Many links are broken and formatting corrupted, it's going to take a while to fix all of this.

This thread is a continuation of the original Linux Compatibility Thread!

 

Important, new issues for 1.1+, please see the Known Issues section below.

Also there is a critical issue with the Unity engine sending a bad window size to the window manager, causing the window manager to crash, there are some workarounds, please see here for more info.

This is FIXED in the 1.2.9 pre-release!

Workarounds:

• Run KSP in fullscreen mode, you can set this via the launcher.
• Delete the ~/.config/unity3d/Squad/Kerbal\ Space\ Program/prefs file before starting KSP.
• Use the xfce desktop (xfwm is immune)
• Force OOM Killer to target KSP instead of the window manager, latest version below.

 

On 3/17/2017 at 0:52 PM, Psycho_zs said:

Tested 1.2.9.

Strangely, with all the localization work, decimal delimiter settings resetting bug is still present. So, LC_ALL=C still needed. Bad window size bug is still in place.

Fresh version of my launcher script:

  Reveal hidden contents

#!/bin/sh

WIN_WIDTH=1366
WIN_HEIGHT=768
BINARY=KSP.x86_64
GEOM_GUARD_TIME="180 seconds"

[ ! -x "$(which xwininfo)" ] && printf "\e[31mWarning: xwininfo not found or is not an executable!\n         Geometry guard will not work!\e[39m\n" >&2

# change dir to script location
cd "$(dirname "$(readlink -f "$0")")"

printf "Still can not learn localized fraction delimiters? setting LC_ALL=C\n"
LANG=C
LC_ALL=C
export LC_ALL
export LANG
unset LANGUAGE

printf "Fixing weird permissions from game archive.\n"
find . -type d -exec chmod 755 "{}" \;
find . -type f -exec chmod 644 "{}" \;
chmod 755 KSP.x86  KSP.x86_64  Launcher.x86  Launcher.x86_64 "${BINARY}" "$(basename "$0")"

# trap for child process cleanup
trap 'kill $KSPPID 2> /dev/null ; exit' EXIT HUP INT TERM

GEOMKILL="2"
COUNT="0"

until [ "$GEOMKILL" = "0" ]
do
	[ "$GEOMKILL" = "1" ] && printf "\nHere we go again...\n"

	printf "Clearing unity3d config dir\n"
	[ -d "${XDG_CONFIG_HOME:-$HOME/.config}/unity3d/" ] && rm -r "${XDG_CONFIG_HOME:-$HOME/.config}/unity3d/"

	GEOMKILL="0"
	COUNT=$(( $COUNT + 1 ))

	printf "\n\e[32mLaunching KSP, attempt ${COUNT}... Hold on to your helmets and pray the Kraken!\e[39m\n\n"

	## multiple variants, some work better than others.
	#./"${BINARY}" -screen-fullscreen 0 -screen-width $WIN_WIDTH -screen-height $WIN_HEIGHT &
	./"${BINARY}" -screen-fullscreen 0 -popupwindow -screen-width $WIN_WIDTH -screen-height $WIN_HEIGHT &
	#./"${BINARY}" -popupwindow -screen-fullscreen &
	KSPPID=$!

	printf "\e[32mLaunched with PID ${KSPPID}.\e[39m\n\n"

	printf "\e[33mBumping KSP OOM killer score in case it goes berserk and chews up all the memory at once.\nCurrent OOM score: $(cat /proc/${KSPPID}/oom_score)\e[39m\n"
	echo 15 > "/proc/${KSPPID}/oom_adj"
	printf "\e[33mNew OOM score: $(cat /proc/${KSPPID}/oom_score)\e[39m\n"

	if [ -x "$(which xwininfo)" ]
	then
		printf "Starting window geometry guard...\n"
		STOPDATE="$(date +%s -d "$GEOM_GUARD_TIME")"
		while [ "$(date +%s)" -lt "$STOPDATE" ] && kill -0 "$KSPPID" 2> /dev/null
		do
			GEOM="$(xwininfo -name "Kerbal Space Program" 2>/dev/null)"
			HEIGHT="${GEOM##*Height:}"
			HEIGHT="${GEOM##*[[:space:]]}"
			HEIGHT="${HEIGHT%%[^0-9]*}"
			WIDTH="${GEOM##*Width:}"
			WIDTH="${GEOM##*[[:space:]]}"
			WIDTH="${WIDTH%%[^0-9]*}"

			if [ "${WIDTH:-0}" -gt "$(( $WIN_WIDTH * 2 ))" -o "${HEIGHT:-0}" -gt "$(( $WIN_HEIGHT * 2 ))" -o "${WIDTH:-10000}" -lt "$(( $WIN_WIDTH / 2 ))" -o "${HEIGHT:-10000}" -lt "$(( $WIN_HEIGHT / 2 ))" ]
			then
				kill -9 "$KSPPID"
				GEOMKILL=1
				printf "\n\e[31mWindow geometry is freaky (${WIDTH:-NA}x${HEIGHT:-NA}), killed KSP!\e[39m\n\n" >&2
				sleep 1
				break
			else
				GEOMKILL=0
			fi
			[ "$WIDTH" != "$PREVWIDTH" -o "$HEIGHT" != "$PREVHEIGHT" ] && printf "\e[33mWindow geometry changed from ${PREVWIDTH:-NA}x${PREVHEIGHT:-NA} to ${WIDTH:-NA}x${HEIGHT:-NA}\e[39m\n"
			PREVWIDTH=$WIDTH
			PREVHEIGHT=$HEIGHT
		done
		[ "$GEOMKILL" = "0" ] && printf "\e[33mWindow geometry guard is (hopefully) no longer needed.\e[39m\n"
	else
		printf "\e[31mxwininfo not found, aborting window geometry guard!\nYou're on your own with OOM.\e[39m\n" >&2
	fi
done

wait

 

Note: Geometry guard might eat up some CPU.

 

 

(1) Getting Started.

Spoiler

 

Supported systems.

Kerbal Space Program is made using the Unity3D game engine, which supports Ubuntu Linux 12.04 and up, and 14.04.3 LTS is recommended, both 32bit and 64bit is supported.

Ubuntu is based on Debian, so nearly any Debian based Linux will work for KSP.

Other versions of Linux will also run KSP as long as they can install any missing dependencies, you can check that KSP has what it needs by using these lines in a terminal.

For 32bit use:

ldd KSP.x86

And for 64bit use:

ldd KSP.x86_64

Click here to learn more about the Linux terminal.

KSP should work "out of the box" on Ubuntu, and the rest of this guide will assume the player is using Ubuntu unless stated otherwise.

[table=width: 500]

[tr]

[td]Minimum System Specs are:

* 2Ghz Single Core CPU or higher

* 3GB RAM

* 512MB Video Card, Shader Model 3.0

* 3GB Free HDD space[/td]

[td]Recommended System Specs are:

* 3.0Ghz Dual Core CPU or higher

* 8GB RAM+

* 1GB Video Card, Shader Model 3.0

* 3GB Free SSD space[/td]

[/tr]

[/table]

KSP is not supported on virtual machines, but see linuxgurugamers post if you want to try (scroll up, to find the post).

Microsoft Windows and Apple Mac users should dual-boot with Linux, instead of trying to play in a virtual machine.

Getting KSP for Linux.

KSP for Linux is currently available DRM free from:

The Squad store (recommended)

GoG.com

Steam

The Humble Store (Steam key)

Green Man Gaming (Steam key)

Amazon.com (Not recommended, Amazon is slow to update, Amazon customers should contact support@kerbalspaceprogram to be migrated to the Squad store)

 

Buying KSP will add the game or the Steam key to your account with that vendor, see each vendors Support pages for help with downloading and redeeming Steam keys.

Installation.

Depending on where you bought KSP, it will either be a GoG installer, an archive file, or it will be in your Steam library.

The GoG installer:

* Make the installer executable by right clicking it, clicking "Properties", then "Permissions", click the box marking the file as a program, then click "Ok".

* If you would like to try changing the permissions with the terminal see here.

* Double click the file to being installing.

* KSP will be installed to "/home/user/GOG Games/Kerbal Space Program" by default and a shortcut added to your applications menu.

The archive:

* Right click the archive and open it with archive manger, click "extract" to extract the contents to the current folder.

Steam:

* Double click KSP in your Steam client to begin installing.

* KSP for Linux on Steam is installed to the normal Steam games folder on your system, see the Steam section for more info.

Starting KSP.

* For the installer version, click the KSP shortcut in your application menu.

* For Steam, double click on KSP in your Steam client.

* If you installed KSP from the archive, open the Kerbal Space Program folder and double click on Launcher.x86 or KSP.x86, if you are using a 64bit version of Linux you can run 64bit KSP by double clicking the Launcher.x86_64 or KSP.x86_64

KSP.x86 will start KSP directly, and Launcher.x86 will open an application that will allow you to edit setting, open KSP sites in your browser, and start KSP.

Issues.

"Launcher.x86_64 and KSP.x86_64 won't start, I have 'Open with' instead."

These two files are not 'executable' by default, so they need to be made executable in the same way as described for the installer, above.

"Launcher.x86 and KSP.x86 won't work on Ubuntu 64bit."

These need some 32bit libraries which are not installed by default on Ubuntu 64bit, so open a terminal (see above) and copy in this line, then press enter:

sudo apt-get install libgl1-mesa-glx:i386

"KSP.x86 in the terminal doesn't work" or "I started KSP from the terminal and things aren't right in the game."

The terminal needs to be set to the folder that KSP is in,

KSP looks in the folder it was started in for configuration files, so if your terminal was in ~/home KSP will not work correctly.

You need to either open a terminal in the Kerbal Space Program folder, or use the cd command to Change Directory.

"Steam starts the 32bit version of KSP and I'm on 64bit"

See the section on Linux KSP on Steam.

"I'm trying to install KSP on Fedora..."

Fedora can be a bit tricky, so linuxgurugamer has made a how-to for getting KSP to run on Fedora 21 and up, complete with installing the Ckan community addon manager and display drivers.

You can also try installing KSP using voidi's installation script, but it's pretty old, just click here! (needs link updating)

(Direct link to script)

Back to top

 

 

 

---

 

(2) Graphics Drivers.

Spoiler

 

Ubuntu and most other Linux distributions come with open source graphics drivers included, and KSP will work fine with these drivers and with most graphics cards.

But updating the open driver, or switching to a proprietary driver, can improve performance so it's worth considering, if you don't know what graphics card you have please see here.

If you have a 32bit PC you should only install a 32bit graphics driver, and only a 64bit driver on Linux 64bit, if installing via official sources only the correct type will be available but if downloading drivers from the internet it is important to get the right ones.

AMD.

There are three "families" of driver for AMD graphics cards, Radeon, Fglrx and Catalyst.

Radeon is the name for the open source AMD/ATI driver which is already installed in Ubuntu and other Linux distributions, and uses the Mesa and Gallium3D libraries to show graphics on AMD cards.

Usually this driver is fairly up-to-date and shouldn't need any maintenance, but newer radeon drivers are available from the Oibaf personal package archive (PPA's).

sudo apt-add-repository ppa:oibaf/graphics-drivers

Update with:

sudo apt-get update

Then:

sudo apt-get upgrade

Whether you stick to the driver from the repository or use a PPA, the driver will automatically update when newer versions become available.

Fglrx is the older proprietary AMD driver and is no longer updated or supported by AMD, but it is still in the Ubuntu repository so many players install this driver via the "Additional Drivers" tool.

On Ubuntu 12.04 and higher, only AMD HD5000 series cards and up are compatible with this driver, the HD4000 and below will only work if the X.org server is replaced with an older version, but this is beyond the scope of this manual.

This can easily be installed by using the "Additional Drivers" appication (jockey, installed by default), which will detect your hardware and display all available drivers that support your graphics card.

Due to the lack of updates this driver is not recommended, please use the Radeon or Catalyst/AMDGPU drivers instead.

Catalyst, and for the latest cards, AMDGUP, is the newer proprietary driver and is frequently updated by AMD, it supports all AMD cards from the HD5000 and up, it is available from the AMD website here.

If you find the open driver to be too slow or lack features, the Catalyst driver is recommended and comes as a .deb package, which can be installed by double clicking it and following the instructions here.

The Catalyst driver won't update itself however, and when a new version is available the current version should be uninstalled before installing the new driver, this can also be done by Software Center, by the Synaptic package manager, or via the Terminal.

Intel.

The Intel driver is called xf86-video-intel and is provided by Intel themselves, so there is no proprietary Intel graphics driver.

This driver is kept up-to-date by Intel and many others who contribute to the drivers upkeep, and the Ubuntu repository usually contains the latest version so if you're using an Intel graphics card you don't need to install anything.

But when a new driver is released it may not appear in the repository straight away, so you still may want to use the Oibaf PPA.

There are some issues with KSP and Intel drivers though, see Issues. for information.

Nvidia.

Two drivers are available for Nvidia hardware, Nouveau, and the Nvidia Display Driver.

Nouveau is the open source Nvidia driver and like the Radeon driver, it is already installed in Ubuntu, and is updated via Ubuntu software updates when new versions are available.

As with Radeon and xf86-video-intel, newer versions of Nouveau may be available in the Oibaf PPA before they are added to the official repository.

Development of Nouveau is slow due to the lack of help from Nvidia, so KSP's performance with this driver can be poor.

The proprietary Nvidia Display Driver, also called the GeForce driver as it is intended for Nvidia's GeForce graphics cards, offers more features, support and speed than Nouveau, so if you have an Nvidia card you should consider installing them.

Several versions of the Nvidia driver are available in the Ubuntu repository so it is important to choose the one that best suits your hardware, so check that your card is listed by clicking "Supported Products" at the following links, from newest to oldest:

Nvidia-355

Nvidia-352

Nvidia-346

Nvidia-340

Nvidia-331

Nvidia-304

Nvidia-173

 

These can easily be installed by using the "Additional Drivers" appication (jockey, installed by default), which will detect your hardware and display all available drivers that support your graphics card.

Ubuntu now also offers an official PPA for the proprietary Nvidia drivers, which can be added via the Terminal with:

sudo apt-add-repository ppa:graphics-drivers/ppa

This makes installing and updating the proprietary Nvidia driver much simpler by using sudo apt-get update then sudo apt-get upgrade.

If you are using Fedora Linux please see here for installing the non-free Nvidia drivers using RPMfusion.

Nvidia Optimus enabled laptops are supported on Linux, and require the Bumblebee package, this can be found in the repository and installed using sudo apt install bumblebee.

You can also get the latest Nvidia driver from the Nvidia website.

Showing the FPS.

There's a few different ways to get FPS in KSP.

The Debug Toolbar

Since 1.0.0, KSP has had a Performance tab added to the Debug tools, Hold Right Shift and tap F12 to open the Debug toolbar then click the Performance tab.

This is rather large however, so you may want to try the options below.

GLXOSD

You can get an on-screen FPS counter in any Linux game using GLXOSD.

It's a command line tool, so to use it you need to start KSP from a terminal or a shell script with "glxosd" in front of the ./KSP.x86 command, like this:

glxosd ./KSP.x86

or

glxosd ./KSP.x86_64

KSP-DEVTOOLS

These platform agnostic tools include FPS.dll, which if plonked in your GameData folder will show the FPS of KSP, it's a little jittery and works on Windows and OSX as well.

VOGLPERF

No I didn't sneeze in German, VOGLPERF is Valves OpenGL benchmarking tool for Linux games and has some very nice features, but it needs compiling.

Thanks to Steve_V for finding these.

Issues.

"KSP doesn't start!" (New for 1.1)

On systems with AMD graphics cards using the proprietary fglrx (outdated) or catalyst drivers the game will need to be started with the -force-gfx-direct command line argument.

This can be done via the terminal with ./KSP.x86_64 -force-gfx-direct

Or via a shell script.

 

"Text is missing!" (New for 1.1)

This has been reported by players using the open source graphics drivers, this can also be fixed by command line argument, in this case by using -force-glcore

This can also be worked around by manually setting a resolution in the settings.cfg file that is 1 pixel smaller, for example:

SCREENWIDTH = 1023

SCREENHEIGHT = 767

The prefs file in .config/unity3d/Squad/Kerbal Space Program/ may also need to be deleted.

 

"KSP cannot set the screen resolution!" (New for 1.1)

The prefs file in .config/unity3d/Squad/Kerbal Space Program/ will need to be deleted.

 

"The GUI buttons overflow their menus!" (New for 1.1)

This looks like a variation on the 1.0.5 map bug, where the map would not render correctly if KSP was at a lower resolution than the desktop in fullscreen mode.

Use windowed mode or set KSP to the desktop resolution.

 

"There are graphic artefacts, there is a green rectangle over my navball!" (New for 1.1)

This appears to be an incompatibility between Unity5 stencilling methods and current graphics driver, either Unity need to fix their bugs or the gfx driver vendors will need to support Unity's broken shaders.

There is no workaround at this time.

 

"Gnome/UnityDE/IceWM/lxde/Xserver crashes when I start/change resolution in KSP!" (New for 1.1)

This appears to be OOM killer killing Xorg, see @Psycho_zs's fix here

On 4/27/2016 at 2:45 AM, Psycho_zs said:

My two cents:

Sometimes KSP managed to freeze and crash my X server upon start. This happens because of some rare instant memory leak, so Xorg gets killed by OOM killer. To give it some other target (KSP), I've added a line to my launcher script before KSP exec, like so:

sh -c 'sleep 1 ; echo 15 > "/proc/$(pgrep KSP.x86_64)/oom_adj"' &
exec ./KSP.x86_64 ...

This should make KSP a priority target for OOM killer. Funny thing, no such freak leak happened ever since, so I do not yet know if this can really help X to walk away from it in working order.

 

"I have no hardware support?"

Some graphics features such as PPFX edge highlighting need anti-aliasing (AA) enabled in KSP to work, so turn on AA in the Graphics settings screen.

"The game crashes after everything loads"

S3TC textures can be broken on Intel cards, Kelmv has a fix here.

"I am missing shadows and have an Intel graphics card" and "Aerodynamic FX says 'No hardware support' but anti-aliasing is on"

You'll want diego_gz's fix for Intel cards here, make a copy of your KSP.x86_64 first!

This has been reported to also solve some crashing issues with these cards.

(Big thanks to Eleven for reminding me)

"All the edges are jagged" (Updared for 1.1)

Unity3D's built-in anti-aliasing seems to be broken with the proprietary open source drivers, there is no known fix.

For older versions of KSP  anti-aliasing can be forced in the Nvidia settings panel by making a new application profile for KSP.x86 or KSP.x86_64 and adding GLFSAAMode = true

 

More info here.

"The ground is missing"

If your game looks like this you need to disable KSP's anti-aliasing, as it breaks terrain rendering with some drivers, notably AMD.

"My editor gizmos are pink!"

The editor gizmos do not display correctly when using the proprietary Nvidia driver, and show magenta circles where the markings should be, the only workaround is to use Nouveau.

"The game is slow with my Nvidia card"

UndeadBanana has a fix here for Nvidia hardware that can greatly improve the speed of your game.

"The ground is weird"

If your then you need to update your graphics driver, as Philipp2499 found here.

Back to top

 

---

 

(3) KSP on Steam.

Spoiler

 

Installing the Steam client.

Important:

The Steam client comes with old lib files, see here on deleting these so Steam works properly.

There are two ways to install the Steam client on Linux, the latest version of Steam is available from the Steam website as a .deb package which can be installed by double clicking it and opening it in Software Center or with gDebi sudo apt install gdebi.

An older version of the Steam is available in most Linux distribution repositories which will automatically update when first run, and can be installed from the Terminal with sudo apt install steam.

Previous versions of KSP.

Steam will download the latest release and keep it up-to-date, and if you would like to try the previous stable release you can by right clicking KSP in the Steam client, selecting "Properties", then the "Betas" tab, and selecting "Previous" from the betas drop-down menu.

KSP 64bit.

The Steam launcher will start the KSP.x86 by default, even on a 64bit version of Linux, to make Steam start the 64bit version of KSP right click KSP in your Steam library, click "Properties" and copy the following into the "Set launch Options" box:

%command%_64

 

Can't find the box? see here and here.

Finding your files.

Depending on which Steam package you installed you can find KSP in either "/home/yourusernamehere/.local/share/Steam/SteamApps/common/Kerbal Space Program" or in "/home/yourusernamehere/.steam/SteamApps/common/Kerbal Space Program"

The . folders (.local and .steam) are hidden folders in Linux, you can toggle viewing of hidden files and folders with control+h or via the file managers options.

The easiest way to find your files is simply to right click on KSP in your Steam client, click "Properties", click the "Local Files" tab, then click on "Browse Local Files", see here for details.

Issues.

"KSP doesn't work/takes ages to load through the Steam client!" (New for 1.1)

Something in the Steam overlay and Unity5 is conflicting, try starting KSP directly or disabling the Steam overlay.

 

"I installed Steam but it won't start"

The older Steam client won't start on Ubuntu 15.04 and later due to including an out-of-date library file, but this is easily fixed by following the instructions here.

"KSP won't start on my 64bit Linux install"

Steam starts KSP 32bit by default, so it needs some 32bit libraries which are not installed by default on Ubuntu 64bit, so open a terminal (see above) and copy in this line, then press enter:

sudo apt-get install libgl1-mesa-glx:i386

"KSP 64bit won't start on my 64bit Linux install"

The KSP.x86_64 is not set as executable by default, so needs to be made executable, see Installation. for info on making a file executable.

"I see 'game overlay renderer' won't load due to a bad ELF class, what does this mean?"

When KSP is started with Steam, Steam loads both a 32bit and a 64bit version of gameoverlayrenderer.so, one will work while the other will fail, but as this doesn't cause any harm you can ignore it.

"KSP won't start for some other reason"

If KSP has any other issues most of the time it's caused by a bad file, so you should first try fixing KSP by verifying the games cache, see here for details.

"The Steam controller doesn't work properly."

Please see here for why and a possible fix.

Back to top

 

 

 

 

---

 

(4) Modifying KSP and importing saves.

Spoiler

 

KSP "mods".

Nearly all KSP addons (mods) will work on KSP for Linux (as well as Apple OS X and Windows), a few will have platform specific downloads so check the addons information before downloading.

Addons usually come in zip files and can be opened with Archive Manager or a similar program, and should be extracted to the "Kerbal Space Program/GameData folder".

Some addons may need more work to install if they don't follow the GameData convention, so do check the addons documentation to be sure.

Removing an addon can be as easy as deleting the addons folder in GameData, though some like Module Manager will have files in GameData that are not in a folder, these also need to be deleted.

Many KSP addons come with plugins written in C#, and the Unity3D engine includes the files it needs to run these, so no extra software needs to be installed to use addons with plugins.

External applications.

Unlike KSP addons, applications designed to run outside of KSP are almost always platform specific so you need to download the Linux version if there is one.

Some applications are only available in one version and require extra work to get them running on Linux, so check the applications documentation for instructions on how to use it.

An example of the above would be addon managers, which may require the Mono or Java software to be installed, and be started via a terminal command.

Most Linux distributions will have Mono and an open source version of Java available in their repositories.

Moving savegames.

KSP keeps your savegames in "Kerbal Space Program/saves" and these can be shared between Linux, OS X and Windows.

The thumbnail images of your craft are in "Kerbal Space Program/thumbs", and your sub assemblies are in "Kerbal Space Program/GameData/Squad/Partlist", these can be copied over the same as with savegames.

Issues.

There aren't really many issues with addons on Linux that aren't due to special install requirements for certain mods.

If you do have an issue, check the addons documentation first, then seek help in the addons thread or the modded support forums.

Back to top

 

 

 

 

---

 

(5) Troubleshooting.

Spoiler

 

When things go wrong.

Don't panic

Most issues with KSP are single events, such as the occasional crash or bug, and restarting the game will resolve it.

Or an issue may be caused by graphics drivers, please see the section on Graphics Drivers for graphics issues.

Reoccurring or constant issues usually have a cause that can be tracked down though, and KSP provides some tools to help us do so.

The debug tools.

The first place to look for the cause of an issue is the debug log in KSP, the log can be opened holding down RightShift and tapping F2.

This opens a window showing the lines being written to the log as they occur, and can often indicate what is causing the problem as it happens, lines marked with "Error" mean something has gone wrong, and lines marked with "NullReferenceException" usually mean a file was not found.

For example, "NullReferenceException: Object reference not set to an instance of an object at ModuleParachute" would indicate that there was a problem with the parachute file.

More information, tools, a button to reload KSP's files and cheats, can be found in the debug tool menu which is opened by holding down RightShift and tapping F12.

From here you can see the values used for flight and heat, view your frames per second and memory use, view the log in more detail and give yourself unlimited fuel, turn off gravity, blow up stuff with whack-a-kerbal (middle mouse button to fire), and if you hold down RightShift with this screen open, you can top up your funds and give your labs a boost

The KSP logs.

The debug log will show what is happening at that particular time but scrolling through it to find issues is difficult, so KSP writes events to a pair of files, called KSP.log and Player.log

KSP.log on Linux is the same as the KSP.log on Windows and OSX, and can be found in the Kerbal Space Program folder.

Where the Kerbal Space Program folder is will depend on how it was installed, please refer to the Installation section.

Player.log contains more information and is more useful when finding the cause of an issue, and can be found in a hidden folder in your home folder called .config

On most Linux distributions, viewing hidden files and folders is toggled by holding the Control and pressing H in the file manager, or via the file managers menu.

The full path to the Player.log is "/home/yourusername/.config/unity3d/Squad/Kerbal Space Program/"

Both logs are plain text files and can be opened in any text editor.

Hardware report.

The logs provide some basic system information but it's sometimes helpful to know more and to do that on Linux we need the hardinfo program.

This may not already be installed, but can easily be installed via Software Center, Synaptic, or the Terminal with:

 

sudo apt install hardinfo

 

It can be started via the programs menu, and is usually called "System profiler and benchmark".

Hardinfo will provide a thorough report on your computers hardware and drivers, and the information can be saved as a plain text document.

Getting help.

Now you know where to find information on KSP, the errors and your hardware, you can put it all together here in the forums.

First, search for a similar issue in case your problem has already been solved, if the issue exists but is unsolved your information may help with resolving it, if you cannot find a similar issue you will need to open a new thread.

Text files need to be uploaded to a file sharing site such as Dropbox or their contents copied to a text sharing site such as Hastebin.

Any screenshots of the issue taken with F1 can be uploaded to Imgur.

Then start the new thread in Support or Modded Support, include a description of the issue, reproduction steps, and the links to the text files and images.

KSP support is provided by the players themselves and not everything is easy to fix or even diagnose, so please give the people volunteering to help you your respect.

Back to top

 

 

 

 

---

 

(6) Known issues.

Spoiler

 

There are a number of issues beyond those mentioned above for installation, graphics, Steam and modding.

If you don't see your specific issue here please check the other sections.

 

"The right shift key has stopped working for zoom in the VAB!"

The default zoom key was changed to fix an issue with Mac OSX failing to pass the shift key to KSP, but you can set this back in the settings screen on Linux (and Windows).

 

"KSP crashes!" (New for 1.1 and updated)

KSP will crash, seemingly at random.

The cause for this is not yet known, but my best guess can be found here.

There is no fix or workaround at this time.

 

"KSP doesn't start!" (New for 1.1)

Current proprietary AMD drivers are breaking with the Unity multi-threaded rendering, force single threaded rendering with the following in a terminal:

KSP.x86_64 -force-gfx-direct

Another cause of KSP failing to start is having PulseAudio installed but disabled, if you have this issue you will see this in your log.

Quote

FMOD failed to get number of drivers ... An error occured that wasn't supposed to. Contact support.

Support in this case is Unity Technologies, but there is a workaround that can be found here.

 

"Text is missing!" (New for 1.1)

This has been reported by players using the open source graphics drivers, this can also be fixed by command line argument, in this case by using -force-glcore

This can also be worked around by manually setting a resolution in the settings.cfg file that is 1 pixel smaller, for example:

SCREENWIDTH = 1023

SCREENHEIGHT = 767

The prefs file in .config/unity3d/Squad/Kerbal Space Program/ may also need to be deleted.

 

"KSP cannot set the screen resolution!" (New for 1.1)

The prefs file in .config/unity3d/Squad/Kerbal Space Program/ will need to be deleted.

 

"The GUI buttons overflow their menus!" (New for 1.1)

This looks like a variation on the 1.0.5 map bug, where the map would not render correctly if KSP was at a lower resolution than the desktop in fullscreen mode.

Use windowed mode or set KSP to the desktop resolution.

 

"There are graphic artefacts, there is a green rectangle over my navball!" (New for 1.1)

This appears to be an incompatibility between Unity5 stencilling methods and current graphics driver, either Unity need to fix their bugs or the gfx driver vendors will need to support Unity's broken shaders.

There is no workaround at this time.

 

"Gnome/UnityDE/IceWM/lxde/Xserver crashes when I start/change resolution in KSP!" (New for 1.1)

This seems to be OOM killer killing Xorg, try this fix by @Psycho_zs

On 4/27/2016 at 2:45 AM, Psycho_zs said:

My two cents:

Sometimes KSP managed to freeze and crash my X server upon start. This happens because of some rare instant memory leak, so Xorg gets killed by OOM killer. To give it some other target (KSP), I've added a line to my launcher script before KSP exec, like so:

sh -c 'sleep 1 ; echo 15 > "/proc/$(pgrep KSP.x86_64)/oom_adj"' &
exec ./KSP.x86_64 ...

This should make KSP a priority target for OOM killer. Funny thing, no such freak leak happened ever since, so I do not yet know if this can really help X to walk away from it in working order.

 

The localization problem (old).

Should no longer be necessary.

KSP doesn't have any support for localizations and expects the language of the PC to be set to US-English or equivalent, if it is not then the period (.) used for floating point numbers is swapped for a comma (,) in the settings and save files, and can cause problems such as:

* Missing attachment nodes.

* Hugely mis-scaled parts.

* Misaligned editor UI.

* Failure to save/load progress.

* Settings not persisting.

* Loading stops at indicator panel, Mk1 cockpit internal or some other file.

* Hyperactive mouse.

This was fixed in KSP 1.0.x but only for the KSP.x86, so if you have any odd behavior you should try this workaround for KSP.x86_64, when using the launchers and for KSP 0.90.0

Note: KSP ignores the users location in 1.0.5, but there are reports that these are required for 1.1

KSP can be forced to use the Posix standard language © which will be available on every Linux system by starting it from a terminal with the LC_ALL or LC_LANG commands (part of setlocale), like these.

LC_ALL=C ./KSP.x86_64

LC_ALL=C ./KSP.x86

LC_ALL=C ./Launcher.x86_64

LC_ALL=C ./Launcher.x86

This gets a bit repetitive, so to save typing you can add this to a text file, called a shell script, that will apply the line and start KSP for you.

The simplest way to do this is to make a new file in your KSP folder, paste in these lines:

#!/bin/bash

LC_ALL=C ./KSP.x86_64

Save the file then make it executable in the same way as for the installer

StoliFlyer made a better shell script that can start the right version of KSP for your system, which was later improved by Ghost99:

Here is universal and simple script for running one of binary, according to user's architecture and with correct locale.

X64_IS_UNSTABLE variable will protect users from running still unstable 64bit version. When 64bit version would be stable (or just for testing), variable can be changed to "no", or just removed.

LANG variable will be used for any binary, launched from current script and will set correct locale for game.

Code: #!/bin/sh LANG=C X64_IS_UNSTABLE="yes" if [[ `arch` == "x86" || $X64_IS_UNSTABLE == "yes" ]] ; then ./KSP.x86 elif [ `arch` == "x86_64" ] ; then ./KSP.x86_64 fi

These scripts will only work inside the KSP folder, if you want a script that you can place anywhere it will need to know where KSP is installed, here is an example for the Steam folder.

#!/bin/sh cd ~/.local/share/Steam/SteamApps/common/Kerbal\ Space\ Program LC_ALL=C ./KSP.x86_64

 

If the script just opens in your text editor you will need to change it to open with 'sh', right click it, click the 'Open with' option then 'custom', type in 'sh' and click 'ok'.

Adding LC_ALL=C to Steam is covered in the Steam section.

Missing fonts.

KSP uses the Arial and ArialBold fonts to display most text in the game, and while Ubuntu already has these installed other distributions may be missing these fonts, and are using libre fonts instead which KSP wasn't set up for.

If you are missing text in KSP you can usually install them from your distro's repositories by installing the ttf-mscorefonts-installer, though the ones I used were from the winetricks eufonts pack (version 2.55 from Windows95, 1998) by running winetricks, selecting the current prefix, selecting "Install a font", choosing the eufonts pack then moving the fonts from Wine to my ~/.fonts folder.

Debian distro jockeys should pop their fonts into their /home/user/.fonts directory.

Arch Linux geniuses should check here for where to install their fonts.

OpenSUSE sufferers should look here.

Gentoo compilers here.

Fedora wearers here.

Followers of Slacktivism here.

Nixos nuts have it harder than most, but see here for help.

Don't forget that files and folders which start with a period are hidden in Linux.

For all distro's, putting the fonts in /usr/share/fonts should do the trick, also after adding any fonts to a linux system you should run "fc-cache -fv" as this will look in the common font directory(s) and build from there (thanks meeki)

Windows users may need these fonts as well, as Windows can suffer from font corruption, necessitating re-installation of the broken fonts.

You can find out more about these fonts on the Wikipedia page which also links to other sources for the fonts.

Missing heat and re-entry effects, 1.0.4 only.

The 1.0.4 version of KSP shipped with a Physics.cfg with correct 1.0.4 values, but if this is deleted KSP will use internal defaults that are incorrect, resulting in no heating or re-entry effects, improper cooling and similar thermal issues, this can be a problem for Steam users if Steam fails to update the file.

 

You can get a copy of the correct Physics.cfg here, just put this in your KSP folder, if you have an existing Physics.cfg you'd like to keep, rename it "Physics.old".

Also, if KSP is started via a shortcut link it will look in the shortcuts directory for the .cfg files, fail to find them, and will run with internal values for heat, controls and part colliders, causing problems.

So use a script that cd's to the KSP folder instead of a link, this also affects Windows users who put shortcuts on their desktop.

Crashing and segmentation faults.

Segfaults in KSP 64bit?, soulsource has found new memory addresses for fixing this issue (Not 100% sure but looking good so far, back up your KSP.x86_64 before attempting)

Meeki has worked out a fix here for 0.22, helps a lot for heavily modded installs, also 0.23 has new offsets, so check out the new instructions here, thanks to MikeAeronautLZ for finding them.

Also, FuzzyLlama has found how to make the above work in Gentoo!

Updated by meeki.

And updated again for 0.23.5 by ASCII892.

Updated yet again, this time by MikeAeronautLZ for 0.24.

Updated for 0.90.0 by Addle.

Updated for 1.0.x by soulsource here.

Just open a terminal, use the cd command followed by the path to your KSP folder in quotes to change to the KSP directory, for example for a Steam install use:

cd "/home/user/.steam/steamapps/common/Kerbal Space Program/"

Alternatively, open a terminal in the KSP folder with your file manager, this can be done via right click or the menus, but Ubuntu users will have to install "nautilus-open-terminal" first.

Backup your KSP.x86_64 using cp KSP.x86_64 KSP.x86_64.bakthen use these two lines, these are for 1.0.x:

echo "008ab803: 00" | xxd -r - KSP.x86_64

echo "008ab808: 00" | xxd -r - KSP.x86_64

 

And these are for 0.90.0:

echo "0099e747: 00" | xxd -r - KSP.x86_64

echo "0099e74c: 00" | xxd -r - KSP.x86_64

 

If for any reason it doesn't work just use:

cp KSP.x86_64.bak KSP.x86_64

to restore your binary from the backup.

If KSP crashes when you revert or pause and resume, you can try the fix here, big thanks to Misanthe for working on this one.

KSP can crash on startup on non-Ubuntu systems with a stacktrace in the log, member a.g. has worked out a fix here.

Mouse issues.

Mouse lag has been reported by several players especially when rotating the camera, and member D_U has worked out it's the mouse polling rate, he explains how to fix it here, and member legolegs has another solution here.

Fedora users should see here.

How to change polling rate on: Ubuntu : Mint : Arch.

If you use a localization that suffers from the above your mouse sensitivity can be corrupted, just delete the settings.cfg to fix it.

Missing a middle mouse button? Then you're missing out on some control in KSP, so see Peachoftree's post here for help.

Joysticks & Gamepads.

Unity3D doesn't handle multiple controllers very well, and has a hard limit of 20 trigger buttons after which they overlap, so complex controllers or several controllers attached simultaneously can overload Unity's controller detection and cause problems.

And with 1.0.x there's serious issues with binding many types of controller, with axis and buttons just not being detected until the second run of KSP with the controller attached.

Also settings are not persisting as KSP resets the settings.cfg if a previously bound controller has been removed or given a new device ID by the operating system, such as when unplugged and reattached.

Strangely, controller bindings can survive and be seen on restart, but other settings are lost.

The only workaround seems to be to restart KSP until it works and never unplug your joystick, if you manage to set up your controller and other settings, make a backup of your settings.cfg, making the settings.cfg read-only will prevent the game from working.

Since Fedora 18 the joystick driver was moved to a module outside of the kernal, so please see here on how to get joysticks to work.

Xbox controllers actually work very well in Linux, but they do require xboxdrv to be installed, luckily many Distros include it in their repositories.

Some keyboards have joystick/gamepad like functions and will be detected as a game controller by jstest and by Unity3D, and if they detect all the keyboard keys as triggers this quickly overloads Unity's controller code.

This can result in strange problems such as the inability to correctly map a trigger button, and triggers acting as if they had autofire enabled, when what is really happening is the keyboard repeat rate is being applied to the trigger (because the trigger and key are overlapped).

One possible fix is to disable part of the keyboard in udev, cantab has instructions on doing this here, another possible fix might be to change the order of the HID devices.

Miscellaneous.

"When I start KSP I am logged out of Ubuntu."

Gnome desktop users that are booted to the login screen when running KSP need to install libwnck-3-0 to fix the panel crash, Prof_Strangelove solved this one.

"I reverted to the previous stable version and now KSP does not start."

Players reverting to .90 from 1.0 will need to delete their settings.cfg or their sound will not work, thanks to kiwiak for this one.

"My keyboard does not work properly."

The azerty keyboard layout don't work very well with KSP (or Unity), the only workaround is to set it to qwerty.

"I used LC_ALL=C and my save is broken."

There is an issue where if a player needs LC_ALL=C and starts a new save, the persistent.sfs can be corrupted in exactly the same way that the settings.cfg can be, please see here for a fix.

"I am tying to run KSP on Arch."

There's a number of issues with KSP on Arch, you can find more info and fixes here.

"My launcher/KSP is the wrong size and I cannot change it."

You can fix this in the Unity3D prefs file at "/home/user/.config/unity3d/Squad/Kerbal Space Program" and "/home/user/.config/unity3d/SQUAD/KSPLauncher" respectively.

"The patcher does not work"

See here for details.

"Parachutes cause KSP to crash."

See the communities stock bugfix modules here.

Back to top

 

 

 

 

---

 

(7) KSP for Windows in Wine.

Spoiler

 

It is still possible to run the Windows version of KSP 1.0.4 in the Wine compatibility layer, KSP works best with the rawinput support of Wine 1.5.13 and higher, so make sure you are using the latest version of Wine.

You will need the updated proprietary drivers for your graphics adapter and the Eufonts pack which is part of Winetricks, then KSP for Windows should work fine in Wine.

There won't be joystick support, and shadows can be messed up, but actual game performance can be slightly higher then in the native Linux build, see the old Wine thread for more.

 

 

Index in case I ever find a way to fix it.

Spoiler

 

--------------------- Scroll down to a heading to be taken to that section --------------------

 

(1) Getting Started.

Supported systems.

Getting KSP for Linux.

Installation.

Starting KSP.

Issues.

(2) Graphics Drivers.

AMD.

Intel.

Nvidia.

Showing the FPS.

Issues.

(3) KSP on Steam.

Installing the Steam client.

Previous versions of KSP.

KSP 64bit.

Finding your files.

Issues.

(4) Modifying KSP and importing saves.

KSP "mods".

External applications.

Moving savegames.

Issues.

(5) Troubleshooting.

When things go wrong.

The debug tools.

The KSP logs.

Hardware report.

Getting help.

(6) Known issues.

The localization problem.

Missing fonts.

Missing heat and re-entry effects.

Crashing and segmentation faults.

Mouse issues.

Joysticks & Gamepads.

Miscellaneous.

(7) KSP for Windows in Wine.

 

 

 

---

 

[KasperVld]

The old thread is available here.

[Endersmens]

Hey Sal, post #3, line one. "Can you hep(I'm guessing it was supposed to say help) add to the list?"

[Kaa253]

As I say in another post. It would be great if this thread could be made sticky again.

[politas]

Given the age of the posts, is the information still relevant?

[vexx32]

Most of it is, actually. The Linux version of KSP has tended to have pretty standard issues ever since it came out, which is pretty interesting. Keeps us from having to figure out new fixes and workarounds with every new release, heh.

[politas]

What are the "Launcher" executables in the KSP_linux folder for exactly?

[sal_vager]

Original post.

 

politas said:

What are the "Launcher" executables in the KSP_linux folder for exactly?

Launcher.x86 and Launcher.x86_64 naturally

And yeah, a lot of the old info is still relevant.

 

 

(1) Getting Started.

 

Supported systems.

Kerbal Space Program is made using the Unity3D game engine, which supports Ubuntu Linux 12.04 and up, and 14.04.3 LTS is recommended, both 32bit and 64bit is supported.

Ubuntu is based on Debian, so nearly any Debian based Linux will work for KSP.

Other versions of Linux will also run KSP as long as they can install any missing dependencies, you can check that KSP has what it needs by using these lines in a terminal.

For 32bit use:

Quote

ldd KSP.x86

And for 64bit use:

Quote

ldd KSP.x86_64

Click here to learn more about the Linux terminal.

KSP should work "out of the box" on Ubuntu, and the rest of this guide will assume the player is using Ubuntu unless stated otherwise.

[table=width: 500]

[tr]

[td]Minimum System Specs are:

* 2Ghz Single Core CPU or higher

* 2GB RAM

* 512MB Video Card, Shader Model 2.0

* 2GB Free HDD space[/td]

[td]Recommended System Specs are:

* 3.0Ghz Dual Core CPU or higher

* 4GB RAM

* 1GB Video Card, Shader Model 3.0

* 2GB Free SSD space[/td]

[/tr]

[/table]

KSP is not supported on virtual machines, but see linuxgurugamers post if you want to try.

Microsoft Windows and Apple Mac users should dual-boot with Linux, instead of trying to play in a virtual machine.

Getting KSP for Linux.

KSP for Linux is currently available DRM free from:

[table=width: 500]

[tr]

[td]The Squad store (recommended)[/td]

[/tr]

[tr]

[td]GoG.com[/td]

[/tr]

[tr]

[td]Steam[/td]

[/tr]

[tr]

[td]The Humble Store (Steam key)[/td]

[/tr]

[tr]

[td]Green Man Gaming (Steam key)[/td]

[/tr]

[tr]

[td]Amazon.com (Not recommended)[/td]

[/tr]

[/table]

Buying KSP will add the game or the Steam key to your account with that vendor, see each vendors Support pages for help with downloading and redeeming Steam keys.

Installation.

Depending on where you bought KSP, it will either be a GoG installer, an archive file

, or it will be in your Steam library.

The GoG installer:

* Make the installer executable by right clicking it, clicking "Properties", then "Permissions", click the box marking the file as a program, then click "Ok".

* If you would like to try changing the permissions with the terminal see here.

* Double click the file to being installing.

* KSP will be installed to "/home/user/GOG Games/Kerbal Space Program" by default and a shortcut added to your applications menu.

The archive:

* Right click the archive and open it with archive manger, click "extract" to extract the contents to the current folder.

Steam:

* Double click KSP in your Steam client to begin installing.

* KSP for Linux on Steam is installed to the normal Steam games folder on your system, see the Steam section for more info.

Starting KSP.

* For the installer version, click the KSP shortcut in your application menu.

* For Steam, double click on KSP in your Steam client.

* If you installed KSP from the archive, open the Kerbal Space Program folder and double click on Launcher.x86 or KSP.x86, if you are using a 64bit version of Linux you can run 64bit KSP by double clicking the Launcher.x86_64 or KSP.x86_64

KSP.x86 will start KSP directly, and Launcher.x86 will open an application that will allow you to edit setting, open KSP sites in your browser, and start KSP.

Issues.

"Launcher.x86_64 and KSP.x86_64 won't start, I have 'Open with' instead."

These two files are not 'executable' by default, so they need to be made executable in the same way as described for the installer, above.

"Launcher.x86 and KSP.x86 won't work on Ubuntu 64bit."

These need some 32bit libraries which are not installed by default on Ubuntu 64bit, so open a terminal (see above) and copy in this line, then press enter:

Quote

sudo apt-get install libgl1-mesa-glx:i386

"KSP.x86 in the terminal doesn't work" or "I started KSP from the terminal and things aren't right in the game."

The terminal needs to be set to the folder that KSP is in,

KSP looks in the folder it was started in for configuration files, so if your terminal was in ~/home KSP will not work correctly.

You need to either open a terminal in the Kerbal Space Program folder, or use the cd command to Change Directory.

"Steam starts the 32bit version of KSP and I'm on 64bit"

See the section on Linux KSP on Steam.

"I'm trying to install KSP on Fedora..."

Fedora can be a bit tricky, so linuxgurugamer has made a how-to for getting KSP to run on Fedora 21 and up, complete with installing the Ckan community addon manager and display drivers.

You can also try installing KSP using voidi's installation script, but it's pretty old, just click here!

(Direct link to script)

Back to top

 

---

 

[Ruedii]

Has anyone found a workaround for the keyboard input issues that are causing the numeric keypad not to work?

[peachoftree]

I found a way to enable middle mouse button functionality on computers that don't have a middle mouse button by mapping the middle mouse function to a key on the keyboard. link.

Edited September 30, 2014 by peachoftree

[sal_vager]

Spoiler

 

Ruedii, no sorry, there's no fix yet.

 

 

(2) Graphics Drivers.

Ubuntu and most other Linux distributions come with open source graphics drivers included, and KSP will work fine with these drivers and with most graphics cards.

But updating the open driver, or switching to a proprietary driver, can improve performance so it's worth considering, if you don't know what graphics card you have please see here.

If you have a 32bit PC you should only install a 32bit graphics driver, and only a 64bit driver on Linux 64bit, if installing via official sources only the correct type will be available but if downloading drivers from the internet it is important to get the right ones.

AMD.

There are three "families" of driver for AMD graphics cards, Radeon, Fglrx and Catalyst.

Radeon is the name for the open source AMD/ATI driver which is already installed in Ubuntu and other Linux distributions, and uses the Mesa and Gallium3D libraries to show graphics on AMD cards.

Usually this driver is fairly up-to-date and shouldn't need any maintenance, but newer radeon drivers are available from the Oibaf and Edgers personal package archives (PPA's).

If you use these PPA's only use one or the other, not both, to install Oibaf, open a terminal and use:

Quote

sudo apt-add-repository ppa:oibaf/graphics-drivers

For Edgers use:

Quote

sudo apt-add-repository ppa:xorg-edgers/ppa

Update with:

Quote

sudo apt-get update

Then:

Quote

sudo apt-get upgrade

Whether you stick to the driver from the repository or use a PPA, the driver will automatically update when newer versions become available.

Fglrx is the older proprietary AMD driver and is no longer updated, but it is still in the Ubuntu repository so many players install this driver via the "Additional Drivers" tool.

On Ubuntu 12.04 and higher, only AMD HD5000 series cards and up are compatible with this driver, the HD4000 and below will only work if the X.org server is replaced with an older version, but this is beyond the scope of this manual.

This can easily be installed by using the "Additional Drivers" appication (jockey, installed by default), which will detect your hardware and display all available drivers that support your graphics card.

Due to the lack of updates this driver is not recommended, please use the Radeon or Catalyst driver instead.

Catalyst is the newer proprietary driver and is frequently updated by AMD, it supports all AMD cards from the HD5000 and up, it is available from the AMD website here.

If you find the open driver to be too slow or lack features, the Catalyst driver is recommended and comes as a .deb package, which can be installed by double clicking it and following the instructions here.

The Catalyst driver won't update itself however, and when a new version is available the current version should be uninstalled before installing the new driver, this can also be done by Software Center, by the Synaptic package manager, or via the Terminal.

Intel.

The Intel driver is called xf86-video-intel and is provided by Intel themselves, so there is no proprietary Intel graphics driver.

This driver is kept up-to-date by Intel and many others who contribute to the drivers upkeep, and the Ubuntu repository usually contains the latest version so if you're using an Intel graphics card you don't need to install anything.

But when a new driver is released it may not appear in the repository straight away, so you still may want to use the Oibaf or Edgers PPA's.

There are some issues with KSP and Intel drivers though, see Issues. for information.

Nvidia.

Two drivers are available for Nvidia hardware, Nouveau, and the Nvidia Display Driver.

Nouveau is the open source Nvidia driver and like the Radeon driver, it is already installed in Ubuntu, and is updated via Ubuntu software updates when new versions are available.

As with Radeon and xf86-video-intel, newer versions of Nouveau may be available in the Oibaf or Edgers PPA's before they are added to the official repository.

Development of Nouveau is slow due to the lack of help from Nvidia, so KSP's performance with this driver can be poor.

The proprietary Nvidia Display Driver, also called the GeForce driver as it is intended for Nvidia's GeForce graphics cards, offers more features, support and speed than Nouveau, so if you have an Nvidia card you should consider installing them.

Several versions of the Nvidia driver are available in the Ubuntu repository so it is important to choose the one that best suits your hardware, so check that your card is listed by clicking "Supported Products" at the following links, from newest to oldest:

[table=width: 500]

[tr]

[td]Nvidia-355[/td]

[td]Nvidia-352[/td]

[td]Nvidia-346[/td]

[td]Nvidia-340[/td]

[td]Nvidia-331[/td]

[td]Nvidia-304[/td]

[td]Nvidia-173[/td]

[/tr]

[/table]

These can easily be installed by using the "Additional Drivers" appication (jockey, installed by default), which will detect your hardware and display all available drivers that support your graphics card.

Ubuntu now also offers an official PPA for the proprietary Nvidia drivers, which can be added via the Terminal with:

Quote

sudo apt-add-repository ppa:graphics-drivers/ppa

This makes installing and updating the proprietary Nvidia driver much simpler by using sudo apt-get update then sudo apt-get upgrade.

If you are using Fedora Linux please see here for installing the non-free Nvidia drivers using RPMfusion.

Nvidia Optimus enabled laptops are supported on Linux, and require the Bumblebee package, this can be found in the repository and installed using sudo apt install bumblebee.

You can also get the latest Nvidia driver from the Nvidia website.

Showing the FPS.

There's a few different ways to get FPS in KSP.

The Debug Toolbar

Since 1.0.0, KSP has had a Performance tab added to the Debug tools, Hold Right Shift and tap F12 to open the Debug toolbar then click the Performance tab.

This is rather large however, so you may want to try the options below.

GLXOSD

You can get an on-screen FPS counter in any Linux game using GLXOSD.

It's a command line tool, so to use it you need to start KSP from a terminal or a shell script with "glxosd" in front of the ./KSP.x86 command, like this:

Quote

glxosd ./KSP.x86

or

Quote

glxosd ./KSP.x86_64

KSP-DEVTOOLS

These platform agnostic tools include FPS.dll, which if plonked in your GameData folder will show the FPS of KSP, it's a little jittery and works on Windows and OSX as well.

VOGLPERF

No I didn't sneeze in German, VOGLPERF is Valves OpenGL benchmarking tool for Linux games and has some very nice features, but it needs compiling.

Thanks to Steve_V for finding these.

Issues.

"I have no hardware support?"

Some graphics features such as PPFX edge highlighting need anti-aliasing (AA) enabled in KSP to work, so turn on AA in the Graphics settings screen.

"The game crashes after everything loads"

S3TC textures can be broken on Intel cards, Kelmv has a fix here.

"I am missing shadows and have an Intel graphics card" and "Aerodynamic FX says 'No hardware support' but anti-aliasing is on"

You'll want diego_gz's fix for Intel cards here, make a copy of your KSP.x86_64 first!

This has been reported to also solve some crashing issues with these cards.

(Big thanks to Eleven for reminding me)

"All the edges are jagged"

Unity3D's built-in anti-aliasing seems to be broken with the proprietary drivers, but it can be forced in the Nvidia settings panel by making a new application profile for KSP.x86 or KSP.x86_64 and adding GLFSAAMode = true, here's what it looks like in my Nvidia control panel:

Javascript is disabled. View full album

 

More info here.

"The ground is missing"

If your game looks like this you need to disable KSP's anti-aliasing, as it breaks terrain rendering with some drivers, notably AMD.

"My editor gizmos are pink!"

The editor gizmos do not display correctly when using the proprietary Nvidia driver, and show magenta circles where the markings should be, the only workaround is to use Nouveau.

"The game is slow with my Nvidia card"

UndeadBanana has a fix here for Nvidia hardware that can greatly improve the speed of your game.

"The ground is weird"

If your then you need to update your graphics driver, as Philipp2499 found here.

Back to top

 

---

 

 

 

[foole]

Can someone repost the info from this thread:

http://forum.kerbalspaceprogram.com/threads/49817-How-to-enable-shadows-on-Linux-for-Intel-Ivy-Bridge-graphics?p=929000&viewfull=1#post929000

Is this a locked thread? I am having crashing issues with Linux Mint 17 and Steam and I was directed to the above thread, but I can't access it for some reason.

Thanks

[sal_vager]

Here you go, the thread is archived,t hat's why it's inaccessible.

FYI, I just gave this a try and it seems to work!

More specifically, my steps were:

0) make a backup!

$ cp KSP.x86_64 KSP.x86_64.bak

1) figure out the byte offset where the particular Intel string shows up:

$ cat KSP.x86_64 | xxd | grep "Intel"

0f01f00: 454c 0049 6e66 6f6f 0025 692e 2569 2e25 EL.Intel.%i.%i.%

0f024f0: 2049 6e74 656c 2039 7878 2028 6275 6767 Intel 9xx (bugg

That first line is the one you want (as GeneCash points out), figure out what that is:

$ printf "%d" 0x0f01f00

15736576

then add a few bytes to get exactly into that "Intel" string, in this case about 5 bytes should do it

2) replace those bytes (thanks to StackOverflow: http://stackoverflow.com/questions/4783657/cli-write-byte-at-address-hexedit-modify-binary-from-the-command-line)

printf 'foo' | dd of=KSP.x86_64 bs=1 seek=15736581 count=3 conv=notrunc

3) profit! as GeneCash points out, you should see a shadow behind the kerbal on the Mun at startup.

[NanoExplorer]

Hello! I'm having a problem that Google can't tell me much about. I had been running the Windows x86 build of KSP while I set up my graphics driver on Linux, and my Logitech Extreme 3D Pro joystick worked like a charm. Now that I'm on Linux however, I'm having difficulty with the buttons.

If I press the button I've mapped as "RCS Toggle" or any other "toggle", the indicator for that function turns on or off every frame. If I try to stage, I hear the staging click 20+ times per second. Spying on the raw joystick with jstest, I see only what I would expect. When I press a button, jstest labels that button as "on" and when I let go it labels it as "off."

My machine is Linux Mint 17 (kernel 3.13, based off of Ubuntu Trusty), with NVIDIA optimus and bumblebee. To launch KSP, I use "optirun ./KSP.x86_64".

Has anyone else experienced this issue or know of a workaround? I don't know whether this is a Unity/Linux problem or whether it is restricted to KSP. The analog axes work just fine.

Thanks for your help!

[jordanjay29]

Has anyone found a workaround for the keyboard input issues that are causing the numeric keypad not to work?

Is this perhaps the same bug that's causing action groups to trigger when I attempt to input numbers into a dialog window, like MechJeb?

[sal_vager]

Spoiler

 

 

Hmm, not had that with my Logitech Wingman NanoExplorer, does it do this only in KSP? Try renaming the settings.cfg so KSP makes a new one, the old one may have a problem.

jordanjay29, Ruedii, just be patient okay

 

 

 

(3) KSP on Steam.

 

Installing the Steam client.

There are two ways to install the Steam client on Linux, the latest version of Steam is available from the Steam website as a .deb package which can be installed by double clicking it and opening it in Software Center or with gDebi sudo apt install gdebi.

An older version of the Steam is available in most Linux distribution repositories which will automatically update when first run, and can be installed from the Terminal with sudo apt install steam.

Previous versions of KSP.

Steam will download the latest release and keep it up-to-date, and if you would like to try the previous stable release you can by right clicking KSP in the Steam client, selecting "Properties", then the "Betas" tab, and selecting "Previous" from the betas drop-down menu.

KSP 64bit.

The Steam launcher will start the KSP.x86 by default, even on a 64bit version of Linux, to make Steam start the 64bit version of KSP right click KSP in your Steam library, click "Properties" and copy the following into the "Set launch Options" box:

%command%_64

 

Can't find the box? see here and here.

Finding your files.

Depending on which Steam package you installed you can find KSP in either "/home/yourusernamehere/.local/share/Steam/SteamApps/common/Kerbal Space Program" or in "/home/yourusernamehere/.steam/SteamApps/common/Kerbal Space Program"

The . folders (.local and .steam) are hidden folders in Linux, you can toggle viewing of hidden files and folders with control+h or via the file managers options.

The easiest way to find your files is simply to right click on KSP in your Steam client, click "Properties", click the "Local Files" tab, then click on "Browse Local Files", see here for details.

Issues.

"I installed Steam but it won't start"

The older Steam client won't start on Ubuntu 15.04 and later due to including an out-of-date library file, but this is easily fixed by following the instructions here.

"KSP won't start on my 64bit Linux install"

Steam starts KSP 32bit by default, so it needs some 32bit libraries which are not installed by default on Ubuntu 64bit, so open a terminal (see above) and copy in this line, then press enter:

Quote

sudo apt-get install libgl1-mesa-glx:i386

"KSP 64bit won't start on my 64bit Linux install"

The KSP.x86_64 is not set as executable by default, so needs to be made executable, see Installation. for info on making a file executable.

"I see 'game overlay renderer' won't load due to a bad ELF class, what does this mean?"

When KSP is started with Steam, Steam loads both a 32bit and a 64bit version of gameoverlayrenderer.so, one will work while the other will fail, but as this doesn't cause any harm you can ignore it.

"KSP won't start for some other reason"

If KSP has any other issues most of the time it's caused by a bad file, so you should first try fixing KSP by verifying the games cache, see here for details.

"The Steam controller doesn't work properly."

Please see here for why and a possible fix.

Back to top

 

---

 

[jordanjay29]

Hmm, not had that with my Logitech Wingman NanoExplorer, does it do this only in KSP? Try renaming the settings.cfg so KSP makes a new one, the old one may have a problem.

jordanjay29, Ruedii, just be patient okay

I didn't think I wasn't. Just trying to get information so I can track when bugs are fixed and such. I was pretty close to hitting backspace once to clear a digit when I remembered that it would trigger my abort action.

[sal_vager]

Spoiler

 

Just.....wait......

There's no fix or workaround we can apply.

 

 

(4) Modifying KSP and importing saves.

KSP "mods".

Nearly all KSP addons (mods) will work on KSP for Linux (as well as Apple OS X and Windows), a few will have platform specific downloads so check the addons information before downloading.

Addons usually come in zip files and can be opened with Archive Manager or a similar program, and should be extracted to the "Kerbal Space Program/GameData folder".

Some addons may need more work to install if they don't follow the GameData convention, so do check the addons documentation to be sure.

Removing an addon can be as easy as deleting the addons folder in GameData, though some like Module Manager will have files in GameData that are not in a folder, these also need to be deleted.

Many KSP addons come with plugins written in C#, and the Unity3D engine includes the files it needs to run these, so no extra software needs to be installed to use addons with plugins.

External applications.

Unlike KSP addons, applications designed to run outside of KSP are almost always platform specific so you need to download the Linux version if there is one.

Some applications are only available in one version and require extra work to get them running on Linux, so check the applications documentation for instructions on how to use it.

An example of the above would be addon managers, which may require the Mono or Java software to be installed, and be started via a terminal command.

Most Linux distributions will have Mono and an open source version of Java available in their repositories.

Moving savegames.

KSP keeps your savegames in "Kerbal Space Program/saves" and these can be shared between Linux, OS X and Windows.

The thumbnail images of your craft are in "Kerbal Space Program/thumbs", and your sub assemblies are in "Kerbal Space Program/GameData/Squad/Partlist", these can be copied over the same as with savegames.

Issues.

There aren't really many issues with addons on Linux that aren't due to special install requirements for certain mods.

If you do have an issue, check the addons documentation first, then seek help in the addons thread or the modded support forums.

Back to top

 

---

 

[NanoExplorer]

Thanks for getting back so quickly!

does it do this only in KSP?

Do you have a recommendation of where else I should try it?

Try renaming the settings.cfg so KSP makes a new one, the old one may have a problem.

I deleted settings.cfg, went to the controls setup, set "lights" to button 2, and launched a new craft with a solar panel and a lightbulb. It still did the same thing, sadly.

Launching it without optirun yields the same result, but at a much lower framerate.

I should mention that I am using the 64 bit version. I'd try it in the 32 bit one, but it crashes right after loading. If you think it would be worth it, I can fix that and try it in 32 bit.

[sal_vager]

Spoiler

 

To be honest, joysticks in KSP have always caused me hassle, they should work but Unity is bad with sticks, you can't have more than 20 buttons for instance (they just loop back round)

It definitely shouldn't be operating the controls with that frequency, it sounds like some kind of autofire is enabled.

 

 

(5) Troubleshooting.

When things go wrong.

Don't panic

Most issues with KSP are single events, such as the occasional crash or bug, and restarting the game will resolve it.

Or an issue may be caused by graphics drivers, please see the section on Graphics Drivers for graphics issues.

Reoccurring or constant issues usually have a cause that can be tracked down though, and KSP provides some tools to help us do so.

The debug tools.

The first place to look for the cause of an issue is the debug log in KSP, the log can be opened holding down RightShift and tapping F2.

This opens a window showing the lines being written to the log as they occur, and can often indicate what is causing the problem as it happens, lines marked with "Error" mean something has gone wrong, and lines marked with "NullReferenceException" usually mean a file was not found.

For example, "NullReferenceException: Object reference not set to an instance of an object at ModuleParachute" would indicate that there was a problem with the parachute file.

More information, tools, a button to reload KSP's files and cheats, can be found in the debug tool menu which is opened by holding down RightShift and tapping F12.

From here you can see the values used for flight and heat, view your frames per second and memory use, view the log in more detail and give yourself unlimited fuel, turn off gravity, blow up stuff with whack-a-kerbal (middle mouse button to fire), and if you hold down RightShift with this screen open, you can top up your funds and give your labs a boost

The KSP logs.

The debug log will show what is happening at that particular time but scrolling through it to find issues is difficult, so KSP writes events to a pair of files, called KSP.log and Player.log

KSP.log on Linux is the same as the KSP.log on Windows and OSX, and can be found in the Kerbal Space Program folder.

Where the Kerbal Space Program folder is will depend on how it was installed, please refer to the Installation section.

Player.log contains more information and is more useful when finding the cause of an issue, and can be found in a hidden folder in your home folder called .config

On most Linux distributions, viewing hidden files and folders is toggled by holding the Control and pressing H in the file manager, or via the file managers menu.

The full path to the Player.log is "/home/yourusername/.config/unity3d/Squad/Kerbal Space Program/"

Both logs are plain text files and can be opened in any text editor.

Hardware report.

The logs provide some basic system information but it's sometimes helpful to know more and to do that on Linux we need the hardinfo program.

This may not already be installed, but can easily be installed via Software Center, Synaptic, or the Terminal with:

 

sudo apt install hardinfo

 

It can be started via the programs menu, and is usually called "System profiler and benchmark".

Hardinfo will provide a thorough report on your computers hardware and drivers, and the information can be saved as a plain text document.

Getting help.

Now you know where to find information on KSP, the errors and your hardware, you can put it all together here in the forums.

First, search for a similar issue in case your problem has already been solved, if the issue exists but is unsolved your information may help with resolving it, if you cannot find a similar issue you will need to open a new thread.

Text files need to be uploaded to a file sharing site such as Dropbox or their contents copied to a text sharing site such as Hastebin.

Any screenshots of the issue taken with F1 can be uploaded to Imgur.

Then start the new thread in Support or Modded Support, include a description of the issue, reproduction steps, and the links to the text files and images.

KSP support is provided by the players themselves and not everything is easy to fix or even diagnose, so please give the people volunteering to help you your respect.

Back to top

 

---

 

[robopilot99]

I had an issue with the axises on my logitech 3d pro joystick on Ubuntu. I was able to get it working with jstest thankfully. Never had any problems with the buttons though.

[foole]

Thanks for that, although my specific problem isn't lack of shadows, it's lack of the game completely.

I'm trying to run KSP through Steam because I bought the game on the recent Humble Store promo. Humble Store only gave a Steam key to run the game, (no direct download link) and Steam+KSP=crash and unplayable game every time. The game tries to load and wham, vanishes when it crashes.

I emailed KSP support and they referred me to the locked thread above regarding shadows, but I don't think that's my issue. Is there any way to play the game without Steam on Linux?

[sal_vager]

Spoiler

 

Hi foole, maybe we can help, it'd help us to see your player.log though, you can find that in "/home/user/.config/unity3d/Squad/Kerbal Space Program"

It is worth seeing if the game with start using the KSP.x86 or KSP.x86_64 files in the game folder directly, in case it's a Steam issue, and if you use a non English system language you may need to try starting KSP from the terminal with "LC_ALL=C ./KSP.x86"

 

 

(6) Known issues.

There are a number of issues beyond those mentioned above for installation, graphics, Steam and modding.

The localization problem.

KSP doesn't yet have any support for localizations and expects the language of the PC to be set to US-English or equivalent, if it is not then the period (.) used for floating point numbers is swapped for a comma (,) in the settings and save files, and can cause problems such as:

* Missing attachment nodes.

* Hugely mis-scaled parts.

* Misaligned editor UI.

* Failure to save/load progress.

* Settings not persisting.

* Loading stops at indicator panel, Mk1 cockpit internal or some other file.

* Hyperactive mouse.

This was fixed in KSP 1.0.x but only for the KSP.x86, so if you have any odd behavior you should try this workaround for KSP.x86_64, when using the launchers and for KSP 0.90.0

Note: KSP ignores the users locate in 1.0.5, so these aren't needed if you're up to date.

KSP can be forced to use the Posix standard language © which will be available on every Linux system by starting it from a terminal with the LC_ALL or LC_LANG commands (part of setlocale), like these.

Quote

LC_ALL=C ./KSP.x86_64

Quote

LC_ALL=C ./KSP.x86

Quote

LC_ALL=C ./Launcher.x86_64

Quote

LC_ALL=C ./Launcher.x86

This gets a bit repetitive, so to save typing you can add this to a text file, called a shell script, that will apply the line and start KSP for you.

The simplest way to do this is to make a new file in your KSP folder, paste in these lines:

Quote

#!/bin/bash

LC_ALL=C ./KSP.x86_64

Save the file then make it executable in the same way as for the installer

StoliFlyer made a better shell script that can start the right version of KSP for your system, which was later improved by Ghost99:

Here is universal and simple script for running one of binary, according to user's architecture and with correct locale.

X64_IS_UNSTABLE variable will protect users from running still unstable 64bit version. When 64bit version would be stable (or just for testing), variable can be changed to "no", or just removed.

LANG variable will be used for any binary, launched from current script and will set correct locale for game.

Code:

#!/bin/sh

LANG=C

X64_IS_UNSTABLE="yes"

if [[ `arch` == "x86" || $X64_IS_UNSTABLE == "yes" ]] ; then

./KSP.x86

elif [ `arch` == "x86_64" ] ; then

./KSP.x86_64

fi

These scripts will only work inside the KSP folder, if you want a script that you can place anywhere it will need to know where KSP is installed, here is an example for the Steam folder.

#!/bin/sh
cd ~/.local/share/Steam/SteamApps/common/Kerbal\ Space\ Program
LC_ALL=C ./KSP.x86_64

 

If the script just opens in your text editor you will need to change it to open with 'sh', right click it, click the 'Open with' option then 'custom', type in 'sh' and click 'ok'.

Adding LC_ALL=C to Steam is covered in the Steam section.

Missing fonts.

KSP uses the Arial and ArialBold fonts to display most text in the game, and while Ubuntu already has these installed other distributions may be missing these fonts, and are using libre fonts instead which KSP wasn't set up for.

If you are missing text in KSP you can usually install them from your distro's repositories by installing the ttf-mscorefonts-installer, though the ones I used were from the winetricks eufonts pack (version 2.55 from Windows95, 1998) by running winetricks, selecting the current prefix, selecting "Install a font", choosing the eufonts pack then moving the fonts from Wine to my ~/.fonts folder.

Debian distro jockeys should pop their fonts into their /home/user/.fonts directory.

Arch Linux geniuses should check here for where to install their fonts.

OpenSUSE sufferers should look here.

Gentoo compilers here.

Fedora wearers here.

Followers of Slacktivism here.

Nixos nuts have it harder than most, but see here for help.

Don't forget that files and folders which start with a period are hidden in Linux.

For all distro's, putting the fonts in /usr/share/fonts should do the trick, also after adding any fonts to a linux system you should run "fc-cache -fv" as this will look in the common font directory(s) and build from there (thanks meeki)

Windows users may need these fonts as well, as Windows can suffer from font corruption, necessitating re-installation of the broken fonts.

You can find out more about these fonts on the Wikipedia page which also links to other sources for the fonts.

Missing heat and re-entry effects, 1.0.4 only.

The 1.0.4 version of KSP shipped with a Physics.cfg with correct 1.0.4 values, but if this is deleted KSP will use internal defaults that are incorrect, resulting in no heating or re-entry effects, improper cooling and similar thermal issues, this can be a problem for Steam users if Steam fails to update the file.

 

You can get a copy of the correct Physics.cfg here, just put this in your KSP folder, if you have an existing Physics.cfg you'd like to keep, rename it "Physics.old".

Also, if KSP is started via a shortcut link it will look in the shortcuts directory for the .cfg files, fail to find them, and will run with internal values for heat, controls and part colliders, causing problems.

So use a script that cd's to the KSP folder instead of a link, this also affects Windows users who put shortcuts on their desktop.

Crashing and segmentation faults.

Segfaults in KSP 64bit?, soulsource has found new memory addresses for fixing this issue (Not 100% sure but looking good so far, back up your KSP.x86_64 before attempting)

Meeki has worked out a fix here for 0.22, helps a lot for heavily modded installs, also 0.23 has new offsets, so check out the new instructions here, thanks to MikeAeronautLZ for finding them.

Also, FuzzyLlama has found how to make the above work in Gentoo!

Updated by meeki.

And updated again for 0.23.5 by ASCII892.

Updated yet again, this time by MikeAeronautLZ for 0.24.

Updated for 0.90.0 by Addle.

Updated for 1.0.x by soulsource here.

Just open a terminal, use the cd command followed by the path to your KSP folder in quotes to change to the KSP directory, for example for a Steam install use:

Quote

cd "/home/user/.steam/steamapps/common/Kerbal Space Program/"

Alternatively, open a terminal in the KSP folder with your file manager, this can be done via right click or the menus, but Ubuntu users will have to install "nautilus-open-terminal" first.

Backup your KSP.x86_64 using cp KSP.x86_64 KSP.x86_64.bakthen use these two lines, these are for 1.0.x:

Quote

echo "008ab803: 00" | xxd -r - KSP.x86_64

echo "008ab808: 00" | xxd -r - KSP.x86_64

 

And these are for 0.90.0:

Quote

echo "0099e747: 00" | xxd -r - KSP.x86_64

echo "0099e74c: 00" | xxd -r - KSP.x86_64

 

If for any reason it doesn't work just use:

Quote

cp KSP.x86_64.bak KSP.x86_64

to restore your binary from the backup.

If KSP crashes when you revert or pause and resume, you can try the fix here, big thanks to Misanthe for working on this one.

KSP can crash on startup on non-Ubuntu systems with a stacktrace in the log, member a.g. has worked out a fix here.

Mouse issues.

Mouse lag has been reported by several players especially when rotating the camera, and member D_U has worked out it's the mouse polling rate, he explains how to fix it here, and member legolegs has another solution here.

Fedora users should see here.

How to change polling rate on: Ubuntu : Mint : Arch.

If you use a localization that suffers from the above your mouse sensitivity can be corrupted, just delete the settings.cfg to fix it.

Missing a middle mouse button? Then you're missing out on some control in KSP, so see Peachoftree's post here for help.

Joysticks & Gamepads.

Unity3D doesn't handle multiple controllers very well, and has a hard limit of 20 trigger buttons after which they overlap, so complex controllers or several controllers attached simultaneously can overload Unity's controller detection and cause problems.

And with 1.0.x there's serious issues with binding many types of controller, with axis and buttons just not being detected until the second run of KSP with the controller attached.

Also settings are not persisting as KSP resets the settings.cfg if a previously bound controller has been removed or given a new device ID by the operating system, such as when unplugged and reattached.

Strangely, controller bindings can survive and be seen on restart, but other settings are lost.

The only workaround seems to be to restart KSP until it works and never unplug your joystick, if you manage to set up your controller and other settings, make a backup of your settings.cfg, making the settings.cfg read-only will prevent the game from working.

Since Fedora 18 the joystick driver was moved to a module outside of the kernal, so please see here on how to get joysticks to work.

Xbox controllers actually work very well in Linux, but they do require xboxdrv to be installed, luckily many Distros include it in their repositories.

Some keyboards have joystick/gamepad like functions and will be detected as a game controller by jstest and by Unity3D, and if they detect all the keyboard keys as triggers this quickly overloads Unity's controller code.

This can result in strange problems such as the inability to correctly map a trigger button, and triggers acting as if they had autofire enabled, when what is really happening is the keyboard repeat rate is being applied to the trigger (because the trigger and key are overlapped).

One possible fix is to disable part of the keyboard in udev, cantab has instructions on doing this here, another possible fix might be to change the order of the HID devices.

Miscellaneous.

"When I start KSP I am logged out of Ubuntu."

Gnome desktop users that are booted to the login screen when running KSP need to install libwnck-3-0 to fix the panel crash, Prof_Strangelove solved this one.

"I reverted to the previous stable version and now KSP does not start."

Players reverting to .90 from 1.0 will need to delete their settings.cfg or their sound will not work, thanks to kiwiak for this one.

"My keyboard does not work properly."

The azerty keyboard layout don't work very well with KSP (or Unity), the only workaround is to set it to qwerty.

"I used LC_ALL=C and my save is broken."

There is an issue where if a player needs LC_ALL=C and starts a new save, the persistent.sfs can be corrupted in exactly the same way that the settings.cfg can be, please see here for a fix.

"I am tying to run KSP on Arch."

There's a number of issues with KSP on Arch, you can find more info and fixes here.

"My launcher/KSP is the wrong size and I cannot change it."

You can fix this in the Unity3D prefs file at "/home/user/.config/unity3d/Squad/Kerbal Space Program" and "/home/user/.config/unity3d/SQUAD/KSPLauncher" respectively.

"The patcher does not work"

See here for details.

"Parachutes cause KSP to crash."

See the communities stock bugfix modules here.

Back to top

 

---

 

 

 

[robopilot99]

The actual game files are under a directory called Steam Apps. You can simply copy the game files out of there and it will run perfectly fine independently from steam. You can find it under /home/(your user name)/.steam/steam/steam apps/common/kerbal space program/

[Badsector]

I want add just 2 hints, if someone don't know.

Store joystick settings.

Every time i start KSP first i have to move all axes for have calibrated joystick, for skip this is more simple store the calibration and launch it with launch_script

jscal -p /dev/input/js0 > joystick.sh
chmod +x ./joystick.sh

copy joystick.sh in your KSP folder and add

./joystick.sh

to your launch script

CPU Affinity

With multicore processor you can improve a bit performance.

In debian based distribution you first need linux-utils package than modify your launch line on this way

LC_ALL=C taskset 0x00000003 ./KSP.x86_64

"taskset 0x00000003" is referred to CPU 1&2 aca #0

If you use nvidia

LC_ALL=C LD_PRELOAD="libpthread.so.0 libGL.so.1" __GL_THREADED_OPTIMIZATIONS=1 taskset 0x00000003 ./KSP.x86_64

Sorry for my bad english and with the hope to be usefull