Search the Community

Showing results for tags 'linux'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • The Daily Kerbal
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • Making History Expansion
    • Making History Missions
    • Making History Discussion
    • Making History Support
  • Breaking Ground Expansion
    • Breaking Ground Discussion
    • Breaking Ground Support
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL





Found 75 results

  1. Hi I'm running Ubuntu 18.04 with the GOG version of KSP, and when I launch the game I immediately get a black screen and the cursor followed by a crash to desktop. This is a fresh install with all the dlc and no mods. Here is a link to my log file, Player.log
  2. I'm currently running Pop! OS Linux distro, and I was wondering as to how I would be able to install KSP. My main problem, is that I have the GOG Galaxy version of the game, I have tried using Lutris to install the game, but each time I get an error saying "Error("Destination path '/home/name/.cache/lutris/installer/kerbal-space-program/unzip' already exists",)" I have obviously checked this each time before installing and its not there. In case its of any help: I have ensured that Lutris has read and write permissions
  3. Since Linux gamers do not get update scripts but have to DL whole client when updating to newer version i suggest that updated version would come with a script, that optionally can be run, that asks are there older version from which to import settings, saves and mods. On the other hand since some updates may break mods, these selections should all be selectable separetly... not forgetting those awesome screenshots!
  4. so i'm only really making a return because i have an ion-powered craft with burn times ~1 hour, but i can't enable physics warp for some reason. everyone says to do alt + . but it doesn't work for me for some reason. maybe because i'm on linux? i really don't know. (sorry if this is in the wrong place, only ~85% sure it should go here but i'm kinda desperate so :/)
  5. I was wondering what distro other forum users have installed if you dual boot with windows that does not count as a dual boot in this quiz also if you use another distro please explain which one
  6. As the title says.... Is v1.6 for Linux actually released? I play on two different computers, one Windows, one Linux. The Window system got the update to 1.6 first, there were some complaints about mk2 Lander but it all worked out in the end. Later that same day I went to play on my Linux system and I *thought* I had update dialog telling me about 1.6, doing upgrade, etc. I played, got the same warning about the lander and some other parts but it worked. Then trying to play again the next day I get incompatible save errors and it won't load. I started investigating this thinking the save had been corrupted only to realize I'm still playing 1.5.1 Now I'm wondering, did I imagine my Linux system updating? Did it revert? Is it even out?
  7. I"m in need of some help installing making history add-on. I"m running Linux mint on a Quad core Asus motherboard I built. the basic program runs great, so i decided to buy the Making history Add-on. I"ve unzipped the files to a folder on my desktop. But the instructions tell me to run a script called dlc-mhe-[lang]. command. I"ve got no clue how to run this in the Command terminal. after i open the terminal I get this:( ray@ray-quadcore:~$ ) can anyone with some linux experience help me out? Thanks for any help Ray Gott
  8. I've installed the game and the Making History expansion through Steam running on Ubuntu 18.04 (Bionic). With the expansion installed, the game no longer runs. Sometimes it crashes before it can load the main menu. Sometimes it crashes or freezes at the main menu. The farthest I've ever made it was to click through to the Making History select-a-mission screen, at which point the game froze. If I uninstall the expansion, the base game still works fine. Is anyone else seeing this behavior? Anyone come up with a workaround?
  9. I am running Darkmultiplayer on KSP 1.4.3 (direct download) on linux. The first time I start a fresh ksp with fresh DMP I get an incompatible mods detected message and A message with terms of service of darkmultiplayer. Darkmultiplayer works just fine the first time I start KSP. the second time I start KSP the incompatible mods message is still there but there is no DarkMultiPlayer window. It is pretty annoying to have to install KSP and DMP again everytime I want to play on my DMP server so I was wondering if anybody knew a solution I am running arch on Linux 4.14.36-1-lts.
  10. ANSWER: Ensure Keyboard Layout matches your physical keyboard from KSP1.4 onwards (ie, 101-key, 105-key, etc) UPDATED ANSWER: Ensure you only have a single keyboard layout available! Having multiple layouts (eg, to switch between different languages) breaks KSP1.4 onwards. ---- So I re-downloaded a brand-new fresh install of KSP 1.4.3 for Linux using Steam. No changes to settings, no mods. Double checked and the keyboard layout matches my OS layout; changing this has no effect. No errors in the log file. Debian GNU/Linux 9 with KDE desktop. Launch the game, start a new stock game, create the first basic rocket, launch it, and in flight-mode, none of the standard keyboard keys (ie, letters) work. Ditto in the Editor; none of the "letter" shortcut keys work. The number keys and the control keys DO work (Shift/Ctrl to adjust throttle, R-Shift F12 to open Debug menu, ESC to pause, etc). In other parts of the game, the keyboard works normally: Settings - keyboard configuration; I can change the bindings (eg, Full-throttle from Z to F) VAB - naming a ship; I can type in a new name. Debug menu (in flight mode); I can type into the log input box. So it looks like something is blocking the controls in flight mode/VAB/etc. And no, there's no input locks active. KSP1.3.1 works fine. Any ideas?
  11. I am dependent on an external DLL to perform some functionality for my plugin. To do this I use P/Invoke's DllImport and it works all fine on Windows. When on Linux/OSX, however, a DllNotFoundException is thrown. (I am using dedicated mac/linux libs when appropriate) [EXC 13:45:27.864] DllNotFoundException: osx/discord-rpc.bin DiscordRP.Discord.OSXInvoker.Initialize (System.String applicationId, .EventHandlers& handlers, Boolean autoRegister, System.String optionalSteamId) DiscordRpc.Initialize (System.String applicationId, .EventHandlers& handlers, Boolean autoRegister, System.String optionalSteamId) DiscordRP.Discord.PresenceController.Initialize () DiscordRP.DiscordRPMod.Start () The file definitely exists, so this error can only mean some other issue occurred while loading was attempted. Windows imports: OSX imports: Used library files: I'm quite lost as to what's going on here -- so any help would be appreciated!
  12. I have installed 1.4.1 and the DLC as instructed in the ReadMe file. I can access Missions and Mission Builder in game but I cannot see any of the new parts and when I try to start a mission that uses the new KV-series pods I get an error message saying the files cannot be found. I looked for the files and found them but Squad has changed the folder organization in the DLC and it no longer resembles the vanilla install folders. Unfortunately I cannot make any changes to the DLC folders as they are write protected. This is frustrating because I have the files on my computer but cannot figure out how to get the game to see them...
  13. Hi All, First for the required info: KSP Version: I'm running in Linux Mint 18.3 (64 bit), and the game is running via steam; From BuildID.txt: 02077; From readme.txt: 1.4.0; Detailed explanation of what happens: I run the game and i get a VERY brief window which closes immediately, this is with both the 32 and 64 bit versions, reverting to v1.3.1Ican play no problem. No need for screenshots or save files as the game doesn't run Player.log: System specs: I run a Lenovo L512 laptop; Chipset: core i5 430M; Graphics: Integrated Intel HD (inex reports it as "Mesa DRI Intel(R) Ironlake Mobile"); RAM: 4GB; HDD: 512GB SSD (Samsung Evo); Clean Install, no mods Generally I assume my machine is too old now and cannot support the minimum level of OpenGL required for 1.4?? It works no problem on 1.3.1 which I can revert to in steam (for now atleast). Is there any way around this at all? I think it might work if I run Win7 but I prefer Linux really. Is there anything I can do here or am I destined to run no later than 1.3.1 on this machine, it s shame as I was just getting into a decent career with it! Cheers All.
  14. I just installed 64 bit arch linux and ksp 1.3.1 64 bit works but for some reason I always get wierd physics lag spikes in 64 bit ksp on windows and every linux distro that I have tried. 32 bit ksp worked fine on ubuntu but I recently switched to arch and when I try running KSP.x86 now I get Searching for joysticks with GUID 05000000362800000100000003010000 Parsing config 030000008916000001fd000024010000,Razer Onza Classic Edition,platform:Linux,x:b2,a:b0,b:b1,y:b3,back:b6,guide:b8,start:b7,dpleft:b11,dpdown:b14,dpright:b12,dpup:b13,leftshoulder:b4,lefttrigger:a2,rightshoulder:b5,righttrigger:a5,leftstick:b9,rightstick:b10,leftx:a0,lefty:a1,rightx:a3,righty:a4, Searching for joysticks with GUID 030000008916000001fd000024010000 Parsing config 030000005e040000d102000001010000,Microsoft X-Box One pad,platform:Linux,x:b2,a:b0,b:b1,y:b3,back:b6,guide:b8,start:b7,dpleft:h0.8,dpdown:h0.0,dpdown:h0.4,dpright:h0.0,dpright:h0.2,dpup:h0.0,dpup:h0.1,leftshoulder:h0.0,leftshoulder:b4,lefttrigger:a2,rightshoulder:b5,righttrigger:a5,leftstick:b9,rightstick:b10,leftx:a0,lefty:a1,rightx:a3,righty:a4, Searching for joysticks with GUID 030000005e040000d102000001010000 Parsing config 03000000790000001100000010010000,RetroLink Saturn Classic Controller,platform:Linux,x:b3,a:b0,b:b1,y:b4,back:b5,guide:b2,start:b8,leftshoulder:b6,rightshoulder:b7,leftx:a0,lefty:a1, Searching for joysticks with GUID 03000000790000001100000010010000 Parsing config 050000007e0500003003000001000000,Nintendo Wii U Pro Controller,platform:Linux,a:b0,b:b1,x:b3,y:b2,back:b8,start:b9,guide:b10,leftshoulder:b4,rightshoulder:b5,leftstick:b11,rightstick:b12,leftx:a0,lefty:a1,rightx:a2,righty:a3,lefttrigger:b6,righttrigger:b7,dpup:b13,dpleft:b15,dpdown:b14,dpright:b16, Searching for joysticks with GUID 050000007e0500003003000001000000 Parsing config 030000005e0400008e02000004010000,Microsoft X-Box 360 pad,platform:Linux,a:b0,b:b1,x:b2,y:b3,back:b6,start:b7,guide:b8,leftshoulder:b4,rightshoulder:b5,leftstick:b9,rightstick:b10,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,dpup:h0.1,dpleft:h0.8,dpdown:h0.4,dpright:h0.2, Searching for joysticks with GUID 030000005e0400008e02000004010000 Aborted (core dumped) the hardware I am using is a ryzen 7 1700 and an r9 380x
  15. crashes whether i run it from steam or not, 32 bit or 64. tried reinstall of game. crashes before ksp.log generates. there is the player.log: Stacktrace: Native stacktrace: /SSDgames/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/ [0x7f209afeca46] /SSDgames/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/ [0x7f209af8f8e4] /lib/x86_64-linux-gnu/ [0x7f20a0760390] /SSDgames/steam/steamapps/common/Kerbal Space Program/KSP.x86_64() [0xf2dd3d] /lib/x86_64-linux-gnu/ [0x7f209ef38ff8] /lib/x86_64-linux-gnu/ [0x7f209ef39045] /lib/x86_64-linux-gnu/ [0x7f209ef1f837] /SSDgames/steam/steamapps/common/Kerbal Space Program/KSP.x86_64() [0x46f695] Debug info from gdb: ERROR: object '/home/thetoric/.steam/ubuntu12_32/' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. No threads. ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= all i can think of is that a package updated that ksp relied on and broke it? using KDE neon, no third party ppas for libraries.
  16. I'm currently setting up a new computer and want to get back to KSP modding. I'd like to use Unity on Debian 9 and I've got some experience with Unity 5.4.1f1 on Debian 8 but it did not end very well last time. Before I install anything I'd like to know if other modders are running Unity on Linux (successfully)? If so, what version of Unity? Does anyone know where to get Unity 5.4.0p4 for Linux? Couldn't find it here.
  17. I'm currently using LimuxPlayer en-us, and I recall getting a consistent segmentation fault quitting the game since 1.3 (Not on earlier versions though). I was hoping this would have been a usually error and someone reporting it and having it fixed. But after picking up playing again, I can't find any mention of this error or fixes for it on the forums. Anyone have some ideas on were to start with solving this? Some clues (short enough to add directly to the thread I'm guessing): ********************** ./KSP.x86_64 Set current directory to /home/oskar/ksp/KSP_linux_1.3.1 Found path: /home/oskar/ksp/KSP_linux_1.3.1/KSP.x86_64 Mono path[0] = '/home/oskar/ksp/KSP_linux_1.3.1/KSP_Data/Managed' Mono path[1] = '/home/oskar/ksp/KSP_linux_1.3.1/KSP_Data/Mono' Mono config path = '/home/oskar/ksp/KSP_linux_1.3.1/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 client has 4 screens displaymanager screen (0)(DVI-I-1): 1920 x 1080 displaymanager screen (1)(DVI-D-0): 1920 x 1080 Using libudev for joystick management Importing game controller configs Segmentation fault (core dumped) ********************* dmesg gives a "KSP.x86_64[4894]: segfault at 7f01641b9be8 ip 00007f00d30c2874 sp 00007ffda783ecf0 error 4 in[7f00d2fe5000+1ca000]" ********************* First and last lines from KSP.log (doesn't seem like there is anything interesting in the log file): ******* Log Initiated for Kerbal Space Program - (LinuxPlayer) en-us ******* Kerbal Space Program - (LinuxPlayer) en-us OS: Linux 4.4 openSUSE project 42.2 64bit CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (4) RAM: 7982 GPU: GeForce GTX 670/PCIe/SSE2 (2048MB) SM: 30 (OpenGL 4.5 [4.5.0 NVIDIA 384.98]) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8 ... ... [LOG 01:55:32.147] [MessageSystem] OnAppInitialized [LOG 01:55:32.147] [MessageSystem] Reposition 0.08033587 10446 [LOG 01:57:58.175] [UIApp] OnDestroy: MessageSystem
  18. Hi All, I just switched to linux mint 18.3 and am having trouble getting KSP to run as well as it did on windows (prior to windows 10 completely dying on me, hence the switch). I'm using the launcher described here: and had a question. I need to activate my discrete radeon graphics card before playing so I run $ xrandr --setprovideroffloadsink 1 0 as a startup script and am trying to then run env DRI_PRIME=0 foo In that same starter script but don't know what application name to substitute. Any ideas? Thanks, torchbat11
  19. Hello everyone I'm have just discovered this amazing game (and for the first time since the days of minecraft I actually play on my computer). For the moment I run it in kubuntu but have decided to switch manjaro instead. What is your experience running KSP in manjaro? Will it just run like expected or do I have to do some console magic? Best regards/ Leif
  20. I'll just put this here as a record of troubleshooting a problem with KSP 1.3 on Linux Mint 17.3 Cinnamon 64-bit. I hope it helps someone else, someday... Hardware: Sandy Bridge i7-2600, 12GB, 1TB, GXT1050 (2GB VRAM). Shell: Bash. Process to produce the problem: $ cd ~/games/ksp_1_3/ # folder to which KSP 1.3 was unzipped. $ ./KSP.x86_64 Result: A completely blank/dark grey screen flashes up a couple of times, and then I am returned to the command line. A core dump is produced. $ echo $? 127 $ find . -type f -name "*.log" $ #no results. "127" is the universal "user-defined error" return code. Not much help. Nor is the core dump of much help, without the source code or a binary compiled for debugging. As shown, no log files are produced by KSP. Solution Steps: Required packages: strace and mlocate. $ sudo updatedb $ strace -s 256 -o strace.log ./KSP.x86_64 As before KSP runs and crashes, but this time a file strace.log is produced. The "-s 256" means record up to 256 bytes of strings in the program, so you can get full file names. $ less strace.log Press 'End' to go to the end of the file. Working backwards from the end of the trace log, the last significant thing was an error within the file "". $ ls -lh `locate` -rwxr-xr-x 1 manaiaK users 13K May 26 04:54 /srv/home/manaiaK/games/ksp_1_3/KSP_Data/Plugins/x86_64/* -rwxr-xr-x 1 manaiaK users 7.7K May 26 04:54 /srv/home/manaiaK/games/ksp_1_3/KSP_Data/Plugins/x86/* -rw-r--r-- 1 root root 56K Jun 25 2014 /usr/lib/gnome-settings-daemon-3.0/ -rw-r--r-- 1 root root 31K Mar 8 2016 /usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/ So, there are different versions of this file. $ cd KSP_Data/Plugins/x86_64 $ cp $ cp /usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/ . $ cd - # returns to ~games/ksp_1_3 $ strace -s 256 -o strace.log ./KSP.x86_64 KSP runs and crashes as before, but inspecting the strace.log file as before reveals a different problem! Progress!. This time the problem is with a file, which is unique to KSP I downloaded the KSP 1.3.1 pre-release, and sure enough the file was different. Copying the 1.3.1 liblingoona in place of the one in my 1.3 install using the process described above fixed that problem. After that, KSP ran normally but produced a SIGSEGV and core dump when I quit the game. To not get core dumps when I run KSP, but still get them when required for debugging my own stuff:- $ ulimit -c 0 ; ./KSP_x86_64 ; ulimit -c unlimited
  21. Hi folks, I hope you don't mind if I share a working script that sets a certain resolution in settings.cfg via bash (should work on mostly all Linux OS'es). This is just a small snipped but I'm not sure where else to put that Feedback is welcome! Regards EDIT: I have updated my shell script to start KSP make sure you read this info before something bad happens. You can grab the here
  22. Hi, just wanted to get a feel for whether users of Manjaro are successfully using Kerbal? I've seen a lot of threads where folks are trying (and mostly succeeding) to install on Arch via Steam. Just want some general feedback on how smoothly this goes, since it's not an officially supported setup. Thanks! Russ
  23. Hi there. I've noticed that none of my batteries in game have any mass. They are all listed as 0.0, even the 1K rechargable I am running KSP 1.3 in Ubuntu Linux My game was started in KSP 1.22 The mods I am running are: Kerbal Engineer Redux Maneuver Node Evolved X Science Kerbal Alarm Clock Lab Upgrade Mod - six Kerbals instead of two I noticed the issue before I installed KAC and the Lab upgrade I can find no setting in the cheat menu that would be causing massless batteries nor in the game difficulty settings. Does anyone have any idea what might be causing this? Actually - I have just worked out part of the issue - The batteries DO have mass as the KER registers an increase in mass each time I add a battery. However the interface is telling me they are all 0 mass ( at least I don't feel ultra cheaty now and it's just an interface bug )
  24. I have been playing through a career game started in KSP 1.2.x After the 1.3 update, Kerbal names no longer appear in the text. Instead odd symbols are present which I guess are in the source file and are supposed to be replaced at run-time. All the Kerbals are now named: "<<1^n>>" That's not a weird code, that's the name as it appears on screen. In addition there multiple choice substitutions that appear such as: "Ferry <<n:1[/%d]>> <<n:1[a VIP]/tourists]>> safely to <<n:3[destination/destinations/destinations]>><<n:4[./and back./ and back.]>>" for contract text. Looking in KSP.log I see the related error message (long paths have been shortened to $KSP_ROOT): [ERR 01:28:04.883] Couldn't open $KSP_ROOT/KSP_Data/Plugins/x86/, error: /usr/lib/i386-linux-gnu/ version `CXXABI_1.3.8' not found (required by $KSP_ROOT/KSP_Data/Plugins/x86/ I gotta say, it's pretty impressive that the game is still playable even when a shared object flat out fails to load. Nice work Squad! Two questions: * Does anyone know which version of libstdc++ implements the ABI listed above? * Is there any reason that the 32-bit version of the game should be launching instead of the 64-bit version when both are present? I have screen shots if needed, thanks for the help.
  25. Current version: 2.3. License - GPLv3+ Description Based upon known launch options of the Kerbal Space Program, I have created a small bash script. Well, it was small initially... It is not a GUI application on purpose - to keep it simple as possible and to allow integration in existing launchers (Steam, GOG Galaxy etc). How to install: Scroll down to the link, save and paste contents into new file, rename it to "" and make it executable; Then 1. Place the script in the same directory as KSP binary and run. Or, 2. Change the shortcuts/desktop file, usually pointing to KSP - to this script instead. Or, 3. If you use GOG offline installer, in "" replace strings "KSP.x86_64" and "KSP.x86", with "" For help: run the script with any parameter ("--help" or similar) How to modify settings: run help, edit the script, change the variable values, save. What script currently allows: - debug/dry run mode - force LC_C to fix disappearing saves/forgetting settings - turn vsync on/off (nvidia and mesa/opensource radeon or intel) - force fullscreen or any video resolution at any time - specify opengl / gles settings - change R600_DEBUG variable - change Mesa options - start gallium benchmark mode - protect against memory issues - support for disabling the (massive KSP) log* and/or automatically rotating it - properly waits for KSP to end, even if it segfaults basically all known options that Linux users had to specify manually have been put in one convenient place. * you NEED a log for any kind of support question! Planned (not yet here): - checking how "-force-gfx-st" differs from existing "-force-gfx-direct" - "-adapter X" launch option Current version: previous version (2.2): previous version (2.0): Warning if you use the "download" button on, instead of copy-pasting raw contents into new text file, then you may encounter the error: "/bin/bash^M: bad interpreter: No such file or directory" To fix it, open this script in text editor and change the line end encodings from Windows to Unix. This done by "", I have no control over this. Heads up of the Linux problems I am aware of, being Linux player myself: - KSP runs hot on GPU Use either nvidia settings panel (for proprietary Nvidia) or radeon profile tool (for AMD, ubuntu PPA) to limit the performance mode of the GPU. In case of Radeon, switch it to manual and low. From my observations, only simulations in atmosphere require a lot of GPU. In VAB/SPH the GPU is perfectly fine in manual low-power mode, consuming 10-20% energy and running cool. Since KSP supports window switching (alt-tab), you can easily adjust performance as you need it. - KSP does not remember settings and always starts in window mode This is because LC_ALL=C is required, if the system locale is NOT us_US, because Unity uses comma delimiter set by locale and some locales have "," instead of "." Solution: KSP_unity_forceLC="on", which is default in my script - KSP starts with window of weird size This is because Unity fails to get screen size from window manager. This seem to be resolved with 1.2+. Solution: KSP_ksp_cleanprefs="on" which is default and will remove Unity's "prefs", and you can force the settings for one launch with KSP_unity_forceX, KSP_unity_forceY, KSP_unity_fullscreen variables. - KSP sometimes at loading crashes Xorg session, booting to login Solution: KSP_ksp_protect="on" , which is default in my script - KSP starts with black screen, noticed in Mesa 11 Solution: KSP_unity_glcore to "on" or "33" (or higher value, if your GL library supports it) - Bop and Minmus have terrain glitches, noticed in Mesa 12 Solution: KSP_unity_glcore to "on" or "41" - RasterPropMonitor shows has pink lines instead of IVA panels This is result of having "glcore" enabled, as it breaks the shaders. Here is the bug report. This has not been fixed. - KSP sometimes crashes I read about this bug being present on Intel opensource drivers. To solve, disable antialiasing in KSP settings. - VAB/SPH floor markers are weird (gradient - AMD, covered in flickering noise - Nvidia). This is connected with shader rendering and OpenGL library in the system. On AMD / Mesa 17, the system also freezes at random time and its connected with issue below. On AMD / Catalyst(depricated driver), its reported to be fixed by disabling PPFX edge shaders in settings. On Nvidia (proprietary driver), is reported to happen with driver 378.13 and later. Its possible to workaround this issue by installing Hangar Extender mod. - KSP freezes the system completely Freeze happens at random point. The freeze happens earlier, if there are Mods that require a lot of GPU work. After many attempts I have traced this issue to Mesa 17+. Solution: If you have OIBAF or PADOKA Mesa installed, try removing them and downgrading to "hwe" Mesa. This is likely DRI3 issue, but no option I know helped, its somewhere in the Mesa userspace stack. Upgrading kernel does not help. If this interests anyone, I am using x64 Kernel 4.12 and KDE Neon (Ubuntu 16.04 LTS-based) with "hwe" packages for Xorg and Mesa. For driver, I use opensource radeon driver, running with R9 280. Enjoy!!