• 8
sal_vager

The Linux Thread!

Question

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:

 

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

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.

cXxaHor.png

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 :wink:

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.

 

 

 


 

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0
an odd stutter every few seconds if I panned the camera a lot.

Ahh, that... it's may be this known issue, no real solution for this one. Or it may be related to mouse polling rate, for which an answer may be found here.

When Steam started up; I got the message "OpenGL GLX context is not using direct rendering, which may cause performance problems"

--8<--

Not sure what to make of it, but I can gather that the direct rendering is related to 32-64 bit inconsistencies.

Yup, for some reason the 64 and 32 bit Nvidia libraries cannot be installed simultaneously on Ubuntu (not sure what gives, again no Ubuntu here) so the 32bit parts of steam fall back to mesa indirect rendering. It shouldn't affect the game itself though (assuming you have steam set to launch the 64bit KSP binary).

The link mentioned in the error message offers some explanation.

Methinks somebody needs to light a fire under Valve about a true 64bit steam client. ;)

- - - Updated - - -

There are updated drivers here which *might* fix this.

This may also be an issue with the steam runtime, though I thought that was fixed... does starting steam with 'STEAM_RUNTIME=0 steam' make that message go away?

Otherwise, more help may be forthcoming on the Ubuntu forums / google...

Edited by steve_v

Share this post


Link to post
Share on other sites
  • 0

It doesn't seem to affect KSP at all, as its ginning right along in 64 bit as fast as I set the FPS. Looks like I'm back in business with KSP

RUNTIME=0 doesn't help, but the error doesn't seem to affect Steam or KSP noticeably so I can live with it until Valve or Ubuntu makes a fix.

Share this post


Link to post
Share on other sites
  • 0

Quick question before I spend a lot of time running through the script on page 1, is it still valid for Ubuntu 14.04?

Share this post


Link to post
Share on other sites
  • 0

Yes, the scripts should all be fine for all versions of Ubuntu, and indeed all Linux distro's, as a terminal of some sort and the shell that runs inside it are standard to all Unix-like operating systems.

Edited by sal_vager

Share this post


Link to post
Share on other sites
  • 0
Quick question before I spend a lot of time running through the script on page 1, is it still valid for Ubuntu 14.04?

If you refer to my script: Should work partial.

As I don't play KSP actively at the moment i only check this thread now and then for News.

My Script has Problem downloading the latest version from the Kerbalspaceprogram website, as a workaround download the zipfile manual and place it in the same directory as the script.

At all:

The problem:

There is maybe something broken with the SSL Certificate of the KSP Website.

If you download something via wget, it aborts and you get the following error message:


ERROR: cannot verify kerbalspaceprogram.com's certificate, issued by '/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2':
Unable to locally verify the issuer's authority.
To connect to kerbalspaceprogram.com insecurely, use `--no-check-certificate'.

Has anybody a idea what this error really means or has a proper workaround (No diasableling '--no-check-certificate' is not a proper workaround).

Also thiy problem may be know: http://forum.kerbalspaceprogram.com/threads/117966-trouble-accessing-kerbalspaceprogram-com-on-Firefox

Edited by Voidi

Share this post


Link to post
Share on other sites
  • 0

It's the site certificate, if you try opening the KSP website in a new browser it will complain about the certificate as well and there is nothing we can do about it.

It is Squads responsibility to keep their certificates up to date and to use reputable issuers instead of GoDaddy.

So while it is true that disabling '--no-check-certificate' is not desirable, it is the only workaround.

Share this post


Link to post
Share on other sites
  • 0

Hey guys,

Upgraded to Ubuntu 15.04 recently. Made sure I had the latest nVidia drivers. Installed KSP, and it runs fine absolutely stock. Yay!

Then I got crazy. Installed CKAN and downloaded some mods. But now KSP crashes after finishing loading all assets and switching between the loading and main menu screens.

Player.log is indicating a SIGSEGV, and at the end of the log is indicating that more than 16GB of memory is being used. However, the System Monitor doesn't indicate any usage above 6GB while KSP is running.

Logs on DropBox: https://www.dropbox.com/sh/q9c0mu16ieta8ix/AAAiecOmqDLOF9IoEcA0hfspa?dl=0

I'm at a loss as to how to fix it from here... Thanks in advance for any help you guys can offer!

-Visi

Share this post


Link to post
Share on other sites
  • 0

Looks like it's trying to use a memory address outside of 16gigs, not that it's using 16gigs, so it'd be an invalid call rather than running out.

The stack trace actually specifically mentions a 2D texture call and clouds.

Stacktrace:

at (wrapper managed-to-native) UnityEngine.Texture2D.INTERNAL_CALL_Compress (UnityEngine.Texture2D,bool) <0x00068>

at (wrapper managed-to-native) UnityEngine.Texture2D.INTERNAL_CALL_Compress (UnityEngine.Texture2D,bool) <0x00068>

at UnityEngine.Texture2D.Compress (bool) <0x0001e>

at OverlaySystem.TextureSet.initTexture () <0x002a1>

at OverlaySystem.TextureSet..ctor (ConfigNode,bool) <0x00099>

at Clouds.Clouds.LoadConfigNode (ConfigNode,string,bool,bool) <0x004a2>

at Clouds.Clouds.loadCloudLayers (bool) <0x002b7>

at Clouds.Clouds.Awake () <0x0005f>

And the KSP.log also ends with clouds.

[LOG 13:35:33.217] Clouds: Cloud Material initialized

[LOG 13:35:33.217] Clouds: Generating Overlay...

So I'm guessing it's the clouds...

Share this post


Link to post
Share on other sites
  • 0

Hello there,

I'm comin back again with my Ubuntu 14.04LTS issues... :P

This time it's about the LC_ALL=C fix that seems to not work anymore.

I use to launch KSP with a little bash file in order to change the cwd to KSP's folder (for the atmospheric and reentry effects) and to set the LC_ALL env variable. Here is my script :

#!/bin/bash

cd "/media/Documents/Jeux/Steam-Linux/Kerbal Space Program"

LC_ALL=C ./KSP.x86_64

Since last sunday, the graphics settings are systematically reset after each KSP reboot (and the sent data confidentiality dialog too, off course) , as if the LC_ALL=C fix was not working anymore (I should remind that I'm using a french desktop).

This happened after an ubuntu update if I can remember (but I'm not 100% sure).

So if somedy has encountered the same problem and would share some advices, it will be greatly appreciated :cool:

And while i'm on that, are the __GL_THREADED_OPTIMIZATIONS=1 and LD_PRELOAD="libpthread.so.0 libGL.so.1" variable definition still necessary for KSP 1.0.4??

Thanks for all (welcome) help.

[Edited]

My OS is Ubuntu 14.04, GTX 760 with Nvidia drivers v355.11, libc is v2.19 (if that could help).

Edited by hargn

Share this post


Link to post
Share on other sites
  • 0

I'm getting consistent hangs/freezes at around T+32 on the basic flight training mission.

I've tried lowering all of my graphics settings as low as possible, but to no avail. Also tried updating drivers and ensured that I'm using the proprietary nvidia-304 driver. KSP.log has no hints and dmesg doesn't show anything interesting.

Any ideas?

Share this post


Link to post
Share on other sites
  • 0
Player.log is indicating a SIGSEGV, and at the end of the log is indicating that more than 16GB of memory is being used. However, the System Monitor doesn't indicate any usage above 6GB while KSP is running.

As far as I can tell, this is a Unity bug; other Unity games (like Cities: Skylines) have the same problem when running under 64-bit Linux. I've tried asking about this in Unity-land, but I haven't gotten anywhere. Best one can do is limit how many mods are installed while hoping that the problem doesn't exist in Unity 5.

Share this post


Link to post
Share on other sites
  • 0

So I was perusing my Player.log for giggles, and I see the following at the top.

My question is mainly, why is my 2GB VRAM dedicated at the top, but anear the bottom, it shows 0 MB VRAM detected?...Also, it looks like KSP is defaulting to using OpenGL? is that correct?

Thanx for any insight... (Oh, this is Lubuntu 15.04, KSP 1.0.4 64bit)


Desktop is 1600 x 900 @ 60 Hz
GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX: 2097152
OpenGL:
Version: OpenGL 4.5 [4.5.0 NVIDIA 346.96]
Renderer: GeForce GT 630M/PCIe/SSE2
Vendor: NVIDIA Corporation
VRAM: 2048 MB
Extensions: GL_AMD_multi_draw_indirect GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_NV_internalformat_sample_query GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_query_buffer_object GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_x11_sync_object GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vdpau_interop GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NV_shader_thread_group GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum
GLX Extensions: GLX_EXT_visual_info GLX_EXT_visual_rating GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGI_video_sync GLX_SGI_swap_control GLX_EXT_swap_control GLX_EXT_swap_control_tear GLX_EXT_texture_from_pixmap GLX_EXT_buffer_age GLX_ARB_create_context GLX_ARB_create_context_profile GLX_EXT_create_context_es_profile GLX_EXT_create_context_es2_profile GLX_ARB_create_context_robustness GLX_NV_delay_before_swap GLX_EXT_stereo_tree GLX_ARB_context_flush_control GLX_ARB_multisample GLX_NV_float_buffer GLX_ARB_fbconfig_float GLX_EXT_framebuffer_sRGB GLX_NV_multisample_coverage GLX_NV_copy_image GLX_ARB_get_proc_address
Setting maxVSyncInterval to 4
GL: Detected 0 MB VRAM
Total system RAM: 5805 MiB
Initialize engine version: 4.6.4f1 (99f88340878d)

Edited by Stone Blue

Share this post


Link to post
Share on other sites
  • 0

I have a desktop system (Centos 7, x86_64, Core2Duo, 8Gb RAM, Nvidia, Nvidia proprietary driver), here KSP works fine.

But on my laptop ThinkPad x220t (Ubuntu 14.04 LTS, Core i5, 16GB RAM, intel graphics) it doesn't works :( The game running, display starting game menu, but when I try to load anything, for example, asteroid mission, I seen vessel, navbol, panel, and... black screen. No space around. I try googling, and read FAQ in start post of this thread, but it doesn't help me.

I use clean, 32 bit installation from Steam(in future I want to change it to x86_64, it works on my desktop fine).

How I can fix my problem?

Share this post


Link to post
Share on other sites
  • 0
Hello there,

I'm comin back again with my Ubuntu 14.04LTS issues... :P

This time it's about the LC_ALL=C fix that seems to not work anymore.

...

And while i'm on that, are the __GL_THREADED_OPTIMIZATIONS=1 and LD_PRELOAD="libpthread.so.0 libGL.so.1" variable definition still necessary for KSP 1.0.4??

Hi hargin, this sounds like the joystick bug, your gfx settings will reset if you start KSP with a controller bound but no controller present.

And __GL_THREADED_OPTIMIZATIONS was never necessary, it's just reported to help for some players (though I never saw a difference).

I'm getting consistent hangs/freezes at around T+32 on the basic flight training mission.

I've tried lowering all of my graphics settings as low as possible, but to no avail. Also tried updating drivers and ensured that I'm using the proprietary nvidia-304 driver. KSP.log has no hints and dmesg doesn't show anything interesting.

Any ideas?

We will need your Player.log from after this occurs wingman :)

So I was perusing my Player.log for giggles, and I see the following at the top.

My question is mainly, why is my 2GB VRAM dedicated at the top, but anear the bottom, it shows 0 MB VRAM detected?...Also, it looks like KSP is defaulting to using OpenGL? is that correct?

Thanx for any insight... (Oh, this is Lubuntu 15.04, KSP 1.0.4 64bit)

KSP on Linux and OSX uses OpenGL, this is normal, the VRAM thing is a Unity bug however and there's nothing we can do about it, thankfully it's completely harmless.

I have a desktop system (Centos 7, x86_64, Core2Duo, 8Gb RAM, Nvidia, Nvidia proprietary driver), here KSP works fine.

But on my laptop ThinkPad x220t (Ubuntu 14.04 LTS, Core i5, 16GB RAM, intel graphics) it doesn't works :( The game running, display starting game menu, but when I try to load anything, for example, asteroid mission, I seen vessel, navbol, panel, and... black screen. No space around. I try googling, and read FAQ in start post of this thread, but it doesn't help me.

I use clean, 32 bit installation from Steam(in future I want to change it to x86_64, it works on my desktop fine).

How I can fix my problem?

We will need your Player.log from after this occurs and your hardinfo report (plain text, not html) please PolNoch, see the first post for details :)

Share this post


Link to post
Share on other sites
  • 0
Hi hargin, this sounds like the joystick bug, your gfx settings will reset if you start KSP with a controller bound but no controller present.

And __GL_THREADED_OPTIMIZATIONS was never necessary, it's just reported to help for some players (though I never saw a difference).

Thanks sal_vager, I've my answer. I saw that there was issues with joysticks.

I tried to test my joystick, but as the thrust axis has an assigned range of −32768 to 32767, only half of my axis is taken into account (KSP set the thrust only from 0% to 50% or from 50% to 100%).

So piloting aircrafts becomes a real challenges.

I didn't wait for your answer : I did a full KSP reinstall ;.;

Edited by hargn

Share this post


Link to post
Share on other sites
  • 0
I'm running KSP on a Thinkpad X220 with Arch Linux. I have a few odd problems, here's a few:

When resuming after a suspend (systemctl suspend, or shutting the laptop lid) while having KSP started, the sound doesn't come back on. I have to fully restart KSP to fix it. This is pretty annoying, and I'd like to fix at least this.

Quicksaving doesn't show the "quicksaving..." in the corner.

I can't use aero-effects. Settings says it's hardware related, but I wouldn't be suprised if it wasn't.

CPU hovers in the upper 50%s, even when doing nothing and on the main menu screen.

I also had a few problems I fixed or I can't replicate, like black VAB fixed by turning a setting off, the Mun disappearing, buttons being blacn, etc.

I'm starting to think my thinkpad is faulty. I had none of these problems on my desktop and other (now dead) laptop. Edited by Zekario

Share this post


Link to post
Share on other sites
  • 0
Hi Zekario.

I don't know about the sound, maybe a pulseaudio issue?

Does quicksave work, have you tried rebinding it to another key?

KSP checks for anti-aliasing before enabling some effects, so try turning on anti-aliasing in the KSP settings screen.

¯\_(ツ)_/¯

The black VAB is caused by the PPFX edge highlighter with Intel drivers, this may also have made the Mun and buttons disappear.

Share this post


Link to post
Share on other sites
  • 0
I use ALSA for sound, and the same thing happens when I suspend on my desktop. Possible KSP bug? I don't remember this happening on PulseAudio, maybe I'll try that.

Quicksave works. I can use F5 and Mod+F5, but the messages don't pop up.

No aero-effects is okay, I guess.

I can live with CPU usage, I don't do much else when playing KSP. And hey, unused CPU is wasted CPU (Right?). Only thing that may be a problem is heating.

Makes sense. I don't have those issues after disabling it.

ALSO: I can't see the fonts on menus like the debug menu. Do I need certain fonts for it to display properly?

Also: Thanks for helping everyone with their KSP troubles on Linux!

Share this post


Link to post
Share on other sites
  • 0
Hello. Hopefully I'm posting this in the right place.

I'm running Ubuntu 14.04 and earlier today my game crashed. I'm not sure why, but it has happened before and everything has turned out fine. The first time, Kerbal told me I had invalid/broken saves and I needed to either delete them or cancel. I canceled and replaced my persistent.sfs with my quicksave.sfs file and was able to play again. However, this time it asked me again and I clumsily clicked delete. Now my save is gone. Is is possible to recover it before I spend most of my time hyperediting everything back? If you need more information I can give you more. Any help is appreciated.

Share this post


Link to post
Share on other sites
  • 0
Zekario, KSP uses [U][URL="https://en.wikipedia.org/wiki/FMOD"]FMOD[/URL][/U] for sound via the [U][URL="http://unity3d.com/"]Unity3D[/URL][/U] game engine, and it looks like [U][URL="http://answers.unity3d.com/questions/524602/audiosource-glitching-when-resuming-from-suspend-o.html"]others have also had issues[/URL][/U] with sound after using suspend.

No idea on the quicksave message, maybe there's an error in the log to say why, you can open it in-game with rightshift+F2 or check your Player.log in ~/.config/unity3d/Squad/Kerbal\ Space\ Program/ , also you can enable anti-aliasing, "no hardware support" doesn't mean AA won't work.

KSP also uses a lot of cpu on my desktop, no idea why or if it can be reduced.

For fonts you will need Arial.ttf and ArialBd.ttf files in your usr/share/fonts folder, you can get these from the ttf-mscorefonts-installer package on Debian systems, there should be an equivalent on Arch, [U][URL="http://forum.kerbalspaceprogram.com/threads/92231-The-Linux-Thread!#linuxthread06b"]more info here.[/URL][/U]


ETPOF, not easily, KSP doesn't make a backup or send the folder to the recycle bin so your only choice is to try an undelete program and hope it recovers the files.

The Ubuntu repository contains a few programs to do this, they are extundelete, magicrescue and testdisk.

Share this post


Link to post
Share on other sites
  • 0
I installed XFCE4 then uninstalled it, and that fixed lots of KSP related problems. I don't know either. Quicksave and debug fonts show up, and I think my only KSP problem now is the suspend-sound thing. My CPU makes more sense now, going up when actually doing things and going down when on menus. It even made CKAN work, before it have errors. I'm confused, but happy.

I have AA on, but aero effects still don't want to work. It's fine though.

Thanks for your help!

Share this post


Link to post
Share on other sites
  • 0
I've been trying to fix my performance issues with Linux KSP on and off for months now. This thread finally provided the answer.

I had massive FPS hits every time I panned the camera around or even moved the mouse too quickly. Turns out my mouse defaults and locks to a polling rate of 1000hz on Linux and changing the rate via usbhid does nothing. I grabbed a cheap mouse locked to 125hz and the FPS drops are finally gone. [URL="https://www.youtube.com/watch?v=P3ALwKeSEYs"]They're GOOONNNEEEE.[/URL]

Share this post


Link to post
Share on other sites
  • 0
LC_ALL=C is not working for me.
the game is in a different HD, but the terminal gives: Permission Denied

what do I do?

Share this post


Link to post
Share on other sites
  • 0
Well, LC_ALL=C should not be needed anymore, with 1.0.5 the game was made to ignore the users locale.

But if you're getting permission denied you'll need to check the permissions of the files, if you're dualbooting with Windows make sure Linux and KSP are on a Linux compatible file system (not NTFS or FAT).

Share this post


Link to post
Share on other sites
  • 0
On 27/11/2015 11:35:46, Ricardo.b said:

the game is in a different HD, but the terminal gives: Permission Denied

What filesystem and mount options does that drive have? (see output of 'mount' command)

If it's NTFS, it's possible to make permissions play nice, but not straightforward, best put KSP on a Linux-native filesystem.

Check that your "different HD" isn't mounted with "noexec" - Ubuntu does this by default for some reason.

 

On another note, why the bleep do we have an "answer this question" button on this thread now? which question? What if it's an informational post - i.e. the top of this thread?

Edited by steve_v

Share this post


Link to post
Share on other sites
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.