Search the Community

I've been a longtime fan of KSP, and I recently installed version 1.2. However, when I try to launch, the cursor turns into a loading circle for a bit and then reverts. Checking System Monitor shows KSP.exe running for a bit, and then stopping. I get no error messages or pop-ups of any kind. This happens when I run both the 32-bit and 64-bit launchers. I have looked into this problem elsewhere on the forum, but the standard bugfix, deleting ~/.config/unity3d/Squad/Kerbal Space Program, doesn't work because said folder doesn't seem to exist on my hard drive. Running KSP.exe via the terminal returns the following: [...]/Kerbal.Space.Program.v1.2.0.1586/KSP.exe fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:system:SetProcessDPIAware stub! wine: Unhandled stack overflow at address 0x7bc475b8 (thread 0009), starting debugger... err:seh:setup_exception_record stack overflow 832 bytes in thread 0009 eip 7bc475b8 esp 00230ff0 stack 0x230000-0x231000-0x330000 Running KSP_x64.exe via the terminal returns the following: [...]/Kerbal.Space.Program.v1.2.0.1586/KSP_x64.exe fixme:heap:HeapSetInformation 0x3c4000 0 0x22fda0 4 fixme:system:SetProcessDPIAware stub! err:seh:setup_exception stack overflow 2032 bytes in thread 0024 eip 00007f5d97b0718b esp 0000000000130e10 stack 0x130000-0x131000-0x230000 I am running KSP on the latest version of Zorin OS, a variant of Debian. It has an Intel® Pentium(R) 2117U CPU and Intel Ivybridge Mobile graphics.

Completly fresh install, no mods. When I run the command "./KSP.x86_64" the following prints; ====== Set current directory to /home/dirk/KSP/KSP_linux Found path: /home/dirk/KSP/KSP_linux/KSP.x86_64 Mono path[0] = '/home/dirk/KSP/KSP_linux/KSP_Data/Managed' Mono path[1] = '/home/dirk/KSP/KSP_linux/KSP_Data/Mono' Mono config path = '/home/dirk/KSP/KSP_linux/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.4 displaymanager : trying .X11-unix client :0 has 1 screens displaymanager screen (0): 1920 x 1200 Using libudev for joystick management Importing game controller configs ====== And stop. No gamewindow no nothign. Unity Player.log shows the following ===== Selecting FBConfig GLX_FBCONFIG_ID=320 GLX_BUFFER_SIZE=32 GLX_DOUBLEBUFFER=1 GLX_RED_SIZE=8 GLX_GREEN_SIZE=8 GLX_BLUE_SIZE=8 GLX_ALPHA_SIZE=8 GLX_DEPTH_SIZE=24 GLX_STENCIL_SIZE=8 GLX_SAMPLES_ARB=0 GLX_SAMPLE_BUFFERS_ARB=0 GLX_CONFIG_CAVEAT=NONE Desktop is 1920 x 1200 @ 60 Hz Invalid resolution: 1 x 0 Failed to initialize ScreenManager ==== There is no config file to edit to fix this. How did you release this?

On HP EliteBook 8570w, under Linux Mint, the KSP demo works perfectly, but the full version either freezes at some point during launch, or if it does successfully launch, much of the graphical resources are missing from the screen. However, on the same HP Elitebook 8570w, under Windows 7, Windows 8.1, or Windows 10, both the KSP demo and full version work perfectly. Is there a solution for this or am I simply out of luck with the Linux Mint / KSP combination? Thanks in advance.

I recently installed KSP on my arch linux laptop (System 76 Galago, i7-4750HQ, 16 GB RAM, intel iris pro 5200) via steam. I installed a few addons and launched it. The game started for a little bit, showed something about installing add-ons and then crashed. After that when I try to launch the game from steam nothing appears to happen. When I try and launch it from the command line with ./KSP.x86 or ./KSP.x86_64 I see the following at the terminal before the program exits: Set current directory to /home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program Found path: /home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 displaymanager : trying .X11-unix client :0 has 1 screens displaymanager screen (0): 1920 x 1080 Using libudev for joystick management Importing game controller configs I then tried deleting the game and reinstalling it (without addons) and now the same thing still happens (I just see the above text in the terminal). I've also verified the game data and that hasn't found anything. I even deleted the game and redownloaded it one more time (again leaving it stock) and still it won't launch. The game doesn't create a new window and I don't get a KSP.log file, I just see the text from above in the terminal. The arch linux wiki mentions launching the game with "LC_ALL=C" so I've tried both "LC_ALL=C ./KSP.x86_64" and "LC_ALL=C ./KSP.x86" I also do have pulse audio running and the ttf-ms-fonts package installed from the AUR. Also I'm running Awesome WM for my window manager if that matters. Does anyone have any ideas on how I can get this to run on my machine?

Hi, since 1.1 I've experienced frequent issues starting KSP (both x86 and x64). I use debian 8 w/ gnome 3. KSP was initially installed through steam. Attached is an exerpt of a load from the syslog of the machine. There are two important things to note: 1) while the syslog says gnome-shell, I believe it's actually ksp running inside gnome. I often start KSP from a terminal for more output, and 2) KSP typically doesn't crash in this situation until the gnome session is completely terminated. From a user standpoint, ksp creates it's window and either before the loading screen appears or sometime during loading everything will flicker, the gnome borders will disappear and the screen will be replaced with a message saying that something had gone wrong in gnome and the session must be exited. No further user input can be made except to accept and destroy the session. This affects both modded & unmodded installs. It affects KSP when running from steam, or started without steam running. I experience the same issue with a single monitor and with two monitors. Has anyone else experienced similar issues, and if so, has anybody found work arounds or solutions? gpu: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) cpu: i7-3720qm @ 2.6ghz ram: 8gb system ram

KSP Version: no longer work, I can't check version on splash screen but it's always updated by Steam and the buildID.txt is build id = 01289 2016-06-21_20-12-27 Branch: master What happen: I was playing all week nights, with a few random crashes but I'm not complaining on those, game was mostly running fine and then... - I paused the game while on rescue operation in orbit - Since music still plays after Alt-Tab to read docs on the web, I decided to set music volume to 0... Escape-> Settings -> Music volume 0 -> Apply After that no more music but the window app game is frozen and then gone... And I can NO LONGER START THE GAME in anyway. Tried after rebooting PC, nothing happen when I start the game from Steam. No splash screen, nothing. It was (mostly) fine before that setting change, I could play for hours. No mods, no add-on, Steam verified install Step to replicate: see description of what happened, but I'm enable to try to replicate: it no longer start. Last lines of KSP.log: [LOG 21:50:31.995] Game Paused! [LOG 21:50:45.826] Launcher start settings screen: False [LOG 21:51:10.296] Launcher here(in write): False [LOG 21:51:10.372] [MessageSystem] Reposition 12.0902 228753 [LOG 21:51:10.372] [GenericAppFrame] Reposition 12.0902 228753 [LOG 21:51:10.372] [GenericAppFrame] Reposition 12.0902 228753 [LOG 21:51:10.373] [GenericAppFrame] Reposition 12.0902 228753 [EXC 22:09:35.566] DllNotFoundException: CSteamworks Steamworks.InteropHelp.TestIfAvailableClient () Steamworks.SteamController.Shutdown () SteamController.KSPSteamController.OnDestroy () SteamController.KSPSteamController.OnApplicationQuit () Start by command line: user@mypc:/data/Steam/steamapps/common/Kerbal Space Program > LANC=C ./KSP.x86_64 Set current directory to /data/Steam/steamapps/common/Kerbal Space Program Found path: /data/Steam/steamapps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/data/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/data/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/data/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.4 client has 4 screens displaymanager screen (0)(DP-0): 1920 x 1200 Using libudev for joystick management Importing game controller configs And that's all. Nothing happen after. My system: PC Intel x86_64 + NVidia, Linux Mint KDE 17.3 64, 8GB RAM, French locale. Classic keyboard and mouse, no fancy controller or joypad. One screen attached to the graphic card. Steam games in custom directory, no problem before and no problem to start other Steam games. Lots of space on disk. My attempts: I edited settings.cfg to set back music to more than 0 (0.3), and I also put back Full screen and resolution that wasn't correct (that's strange). I have a copy of the unedited file. I changed Steam KSP startup option as suggested: LC_ALL=C %command%_64 My question / request: I would be very grateful to anyone would could help me or point me toward a bug solving process, but right now I can't even find a clue EDIT: looking into that thread that look promising... EDIT 2: SOLVED! (workaround) Just delete or rename that file: ~/.config/unity3d/Squad/Kerbal Space Program/prefs Here is the offending prefs file content, a bug in KSP has written crazy resolution: <unity_prefs version_major="1" version_minor="1"> <pref name="Screenmanager Is Fullscreen mode" type="int">0</pref> <pref name="Screenmanager Resolution Height" type="int">23</pref> <pref name="Screenmanager Resolution Width" type="int">1</pref> <pref name="UnityGraphicsQuality" type="int">5</pref> <pref name="UnitySelectMonitor" type="int">-1</pref> </unity_prefs>

Hello all! I'm running a clean install of KSP 1.1.3 on Ubuntu 16.04, kernel version 4.4.0. I've got dual Xeon E5-2670s, a GTX 1060 6gb and 64gb of ram, so I don't think my problem is a hardware limitation. Any scene with any 3D rendering, regardless of graphics settings, (including the kerbals floating in space on the main menu) uses 100% CPU (100% of all 32 cores!) and I'm getting terrible frame rates. I'm getting 10-40fps on different scenes, with terrible stuttering. Is there a fix for this unreasonable cpu usage?

Recently I ran into a performance issue - when flying a vessel and when in map view of an active vessel the frame rate drops to very low number (1 to 5 FPS) and my nvidia control panel shows very low GPU utilization. However, in the KSC and in Tracking Station the game is nice and smooth and GPU is properly utilized. In detail When I start the game, in the KSC the game runs fine and smooth and it is clearly using the GPU as can be seen from this image (GPU uitilization can be read in the left window): GPU utilization in KSC When I go to the tracking station, the game still runs fine and smooth and is also using GPU: GPU utilization in Tracking Station And now it begins. When I fly the vessel (or Melina as in this example), the game drops to about 1 to 5 FPS. The weirdest thing is that now the GPU is almost idle (it fluctuates between 0% and about 20%): GPU utilization flying a vessel. More to that, the debug window shows 25 FPS but that is not true, it is painfully laggy with about 1 to 5 FPS as I have already written. The same happens when I switch to map view - again about 1 to 5 FPS, again very low GPU utilization: GPU utilization in Map View. Again the 25 FPS in the debug window is not the real frame rate. However this behavior started only recently (a day or two, maybe? I'm not entirely sure). I have neither modified any mods nor the KSP itself. Maybe some system updates happened but I'm not sure about that (since I didn't track this as I found out about this problem just as it happened). OS: Ubuntu Gnome 16.04 > uname -srvmpio Linux 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux KSP version: 1.1.3.1289 (from Steam) Installed mods: (all installed via CKAN) [x] Science! (xScience v4.20) CapCom - Mission Control On The Go (CapCom 2.4) Contract Parser (ContractParser 4.0) Deadly Reentry Continued (DeadlyReentry v7.4.7.1) Docking Port Alignment Indicator (DockingPortAlignmentIndicator 6.4) Ferram Aerospace Research (FerramAerospaceResearch 3:0.15.7.2) Kerbal Alarm Clock (KerbalAlarmClock v3.7.1.0) Kerbal Attachment System (KAS 0.5.9.0) Kerbal Flight Data (KerbalFlightData R21) Kerbal Inventory System (KIS 1.2.12.0) Magic Smoke Industries Infernal Robotics (InfernalRobotics v2.0.5) Magic Smoke Industries Infernal Robotics - Legacy Parts (InfernalRobotics-LegacyParts v2.0.0) MechJeb 2 (MechJeb2 2.5.8.0) ModularFlightIntegrator (ModularFlightIntegrator 1.1.6.0) Module Manager (ModuleManager 2.6.25) NavUtilities (NavUtilities 0.6.1) PersistentRotation (PersistentRotation 1.6) Portrait Stats (PortraitStats 11.0) Procedural Fairings (ProceduralFairings v3.17) Progress Parser (ProgressParser 5.0) RemoteTech (RemoteTech v1.7.1) ShipManifest (ShipManifest 5.1.2.2) Surface Mounted Stock-Alike Lights (surfacelights 1.2.4.0) Toolbar (Toolbar 1.7.12) TweakScale - Rescale Everything! (TweakScale v2.2.13) Waypoint Manager (WaypointManager 2.5.3) GPU: Nvida NVS 4200M (a lot of info about the GPU can be seen in the screenshots) GPU driver: 364.19 (installed via Ubuntu's Additional drivers) Thanks for any help and hints.

I recently started playing KSP after a break and the new patch. When I loaded the game, it stopped running, froze, and when I attempted to re-load the game I found that my save files had gone missing from the menu. After manually locating them and suspecting corruption, I made a new save game. The new save game -- default -- did not appear on the menu. In effect I cannot save any game. Weirdly, when I tried to save a new default game I was given an overwrite warning. I do not appear to have an output log. I am currently running Ubuntu.

I can't see a lot of UI elements, such as most of the Settings screen or the Training menu. I've attached screenshots to show what I mean. Note that everything is there, just invisible, as when I click various parts of the list of training missions, the displayed name and description does change. I'm on 64-bit Linux, and this happens with both the 32-bit and 64-bit KSP binaries. I have version 1.1.1.1250 of the game through Steam. This is a completely fresh, clean, unmodded installation. I've tried this on two different computers with the exact same results: one running Ubuntu 16.04 with Intel graphics, and one running Kubuntu 16.04 with AMD graphics. I note this sounds like "No text shows up in the settings menu" in the list of common problems, but I confirmed that I already have the fonts installed that are supposed to fix it.

I'm interested in the game.. Looks like lot of fun.. Too bad I didn't discover earlier. I have a skylake (i5-6500) CPU with 16 GB RAM with Intel graphics (integrated HD 530) running antegros Linux (like arch) I just want to know from the community if intel graphics would be sufficient and how does KSP generallly behave with Linux? -Thanks Vijay

Hi, I just bought KSP (Steam), but unfortunately it does not fully working for me: In no single menu, any text, boxes, buttons ... is shown: I've read about a possible fix for my Problem, so I've installed the Microsoft True Type Fonts ( apt-get install ttf-mscorefonts-installer) and it seems like the OS (Ubuntu 16.04) is recognizing them (able to use them in libre office). But again - same problem: no content is shown. Don't know what to do next, hope you guys can help me. Additional System information: OS: Ubuntu 16.04 - Xenial Xerus 64Bit CPU: Intel® Core™ i5-3317U CPU @ 1.70GHz × 4 GPU: GeForce GT 635M / Intel HD Graphics 4000 - Ivy Bridge KSP-Version: 1.1.0.1230 (Steam)

Hello Linux x86_64 here, Ubuntu 14.04 LTS, Gnome Classic (metacity, no compiz or other graphical crap), nvidia-340. I am seeing a fairly consistent crash on startup. I am running a 2x 1920x1080 setup, but the problem happens even in single-monitor mode. After launching KSP_x86_64, a black game window appears (sized to be about 1920x1080, plus window decorations). A few seconds later, the (still black) game window flickers, killing my window manager, all running Xorg clients, and my entire Xorg session, meaning that I have to log in again. This is quite reproducible. I found that the problem is a lot less likely to happen if I edit ~/.config/unity3d/Squad/Kerbal Space Program/prefs and delete any lines containing 'Screenmanager'. However, usually these lines will return if the game is restarted, meaning that I have to do this every time the game starts. Sometimes, even deleting the screenmanager lines does not prevent the game from crashing the whole graphical interface, but it generally helps. Any thoughts? Edit to add: These are the lines that I have to delete in 'prefs'. I imagine the actual resolution is a little lower than 1920x1080, due to sizes of window borders and window decorations. Perhaps Unity's initial attempts to attain this resolution (before KSP does its own internal window resize) is what's causing the disaster. <pref name="Screenmanager Is Fullscreen mode" type="int">0</pref> <pref name="Screenmanager Resolution Height" type="int">1053</pref> <pref name="Screenmanager Resolution Width" type="int">1912</pref> During the startup phase (before the screen with the progress bar and three kerbals), it is very easy to crash the game (and the window manager, and X) just by trying to move the game window or to resize it.

It's hard for me to reproduce; I thought it might have been something to do with adding parts then removing them, but if I fiddle with a vessel in the VAB for a while, it pretty reliably crashes. There's a copy of what it spat out on the console and Player.log here. This line spits out on the console before a back trace and memory dump: *** Error in `./KSP.x86_64': double free or corruption (out): 0x00007f3a1fb414d0 *** So it's probably a double free. I'm running KSP.x86_64 on Debian: 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17) x86_64 GNU/Linux

If youre infuriated by the stupidly slow speed of the zoom in the VAB/SPH, you can fix it by changing VAB_CAMERA_ZOOM_SENS in settings.cfg. For some reason this defaults to 0.1, instead of 0.5 as it should be, and is for FLT_CAMERA_ZOOM_SENS (which is the same thing, but for when youre flying a ship). Sadly, there is still no known fix for the ineffectively slow rotation speed in IVA scenes.

Hello! Long time lurker, first time poster here. I've found myself in quite a special situation and I was hoping some linux users could help me out here. I have a mid range PC I'm trying to run a DMP server on and the server runs well, it works fine. As of right now I use TMUX to run the server outside of the terminal window The problem comes in when I try to run the server headless. I use putty to SSH into my server and the server ONLY allows NEW connections when putty is connected. If I or anyone else connects before I close the SSH window the connection is maintained. The specific error that DMP spits out is "handshake error: invalid username". This post was kind of jumbled so if I can provide any info that might help please just ask. I hope that someone here can help. Thanks everyone.

I recently decided I'd try and fix 1.1 on my PC because I found a workaround to the crashes I had before. Here is what I have done so far: Download 1.1.3 via Steam. KSP will not launch. run `ln -s /dev/null libpulse-simple.so.0` in the KSP directory, and set `LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH %command%_64` as launch options. KSP now launches, but menus are empty. I then added `-force-glcore` to the launch options. KSP launches and menus are readable, but bad shadow glitches occur. Everywhere this is mentioned online it states to mess with the graphics settings. I tried to fix the shadows via the settings, but have had no luck so far. I also can't click `apply` in the settings, it does nothing. Besides the shadows, everything seems to be working fine. EDIT: Setting Shadow Cascade to 2 (via the in-game pause menu) fixed the shadows, but the main menu settings is still broken.

I've just downloaded the KSP zipfile for linux, unzipped it and launched KSP. All working fine so far. But I've noticed that the unzipped directory contains duplicate files: a KSP.exe and Launcher.x86 that are identical, and similarly a KSP_64.exe and Launcher.x86_64 . Is there a reason for this duplication? Did a symbolic link accidentally get transformed into a real file at some point? Is it safe for me to delete one of the duplicates (which one?) and replace it with a symlink?

Ever since patching v1.1.1 to v1.1.2, startup on Linux (Ubuntu 14.04 LTS, x86_64, nvidia) results in the following error. steve@hypernelson:~/KSP_linux$ ./KSP.x86_64 Set current directory to /home/steve/KSP_linux Found path: /home/steve/KSP_linux/KSP.x86_64 Mono path[0] = '/home/steve/KSP_linux/KSP_Data/Managed' Mono path[1] = '/home/steve/KSP_linux/KSP_Data/Mono' Mono config path = '/home/steve/KSP_linux/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.4 client has 2 screens displaymanager screen (0)(DP-2): 1920 x 1080 displaymanager screen (1)(DP-1): 1920 x 1080 Using libudev for joystick management Importing game controller configs PlayerInitEngineNoGraphics settings: Could..... not preload global game manager #0 i=0 Failed to initialize player steve@hypernelson:~/KSP_linux$

As above. Seeing repeated hard crashes to desktop at random intervals. No pattern, no warning, no (relevant) exceptions in Player.log. This is a modded install, crashes also present in stock game though less frequent. Mod list (from log): STDOUT: *** Error in `/home/steve/Games/KSP_linux/KSP.x86_64': free(): invalid size: 0x00007f19141b0d40 *** Aborted (core dumped) Stacktrace: Full log. I have many of these (with traces), some die with "free(): invalid size", but more commonly "double free or corruption". Not certain they are the same. Reproduction steps: Unknown. Strikes at random, primarily during scene changes but also encuontered during normal play in editor & flight scenes. This is Debian 8.4, kernel 4.5.0-0.bpo.1-amd64, Nvidia 361.42. H/W: I7-3280, 16GB DDR3, Nvidia GTX680. IIRC this was raised during pre-release, any word on progress? This is making the game effectively unplayable as I see a crash every ~1hr.

The new 1.1 version of KSP insta-crashes at the beginning of the loading screen, and this is what the log shows. --- Kerbal Space Program - 1.1.0.1230 (LinuxPlayer) OS: Linux 3.19 LinuxMint 17.3 64bit CPU: AMD FX(tm)-8320 Eight-Core Processor (8) RAM: 7969 GPU: AMD Radeon HD 7900 Series (2722MB) SM: 30 (OpenGL 4.5 [4.5.13399 Compatibility Profile Context 15.201.1151]) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8 Log started: Tue, Apr 19, 2016 16:30:02 --- It cuts off after that. I've tested this on 32/64bit versions for both Steam, and the non-Steam versions, and I get the same crash without loading anything.

I'm having serious issues with KSP crashing out on startup with 1.1.1. Am I the only one seeing this?

I have two separate issues with heavily modded game (CKAN lists 76 mods - http://utoopia.eu/img/test.ckan - list by Ckan). 1.0.5 worked well with around same set of mods. 1. Stations issue - One issue is with space stations only - and stations use some Near Future Construction 0.5.5 mod (cant upgrade because some parts are removed from 0.6 - maybe need to make new station - change central part with big docks to some alternative mod - and do savegame edit - but this is last resort). Currently sometimes station wobbles, trusses will go to infinite length, game wont allow depart from station and claim's its moving. On screenshot I noticed science lab is missing and seems to be away. Trusses are supposed to connect science lab to jet fuel tanks/engine pylons. 2. IVA everywhere issue - Other issue is with EVA and some satellites where IVA view is poping up behind kerbal on EVA or satelite core. Its quite disturbing - cannot see around - is Kerbal next to door already? Have to move around sideways to see more - IVA is only behind kerbal - so moving sideways allows to turn IVA to side also to take fewer space from screen. Also - kerbal portraits from right-lower corner are missing. Issue came some 2-3 days ago, probably because some mod updates arrived to CKAN. Edit: IVA issue seems to have been fixed a day before 1.1.1 update by some mods. In prerelease game was working fine, mods were just not working (depite being there). Issues are raising now with updates.

Version: Linux 1.1.0 x64 Operating system: Mint 17.1 KDE Mods used: Kerbal Engineer Redux 1.1.0.2 SpaceY Heavy Lifters 1.12.1 ModuleManager 2.6.21 (included with SpaceY) I'm having a weird issue where my computer is unable to open any of my KSP installs, regardless of version, as it won't do anything when I click the executable. This I don't think is a KSP glitch, but I got here through a series of game crashes first. I was re-entering the atmosphere early on in my hard career mode, my vessel flipped over and burned up and I had to redesign a new one. I built essentially a stack of FL-T200s with a Swivel engine on it. That was too tall so I offset it into the pod a tiny bit until it was small enough for the tier 1 launchpad. Pressed launch with Jeb and two tourists inside and the game crashed. ...this is where I didn't make a copy KSP.log before starting it again. I did scroll through and saw a lot of stuff about wheel modules not working or something when the game was loading. Load to menu, open save, click on vessel sitting on launchpad, crash again. Open game again, it loads about 100 pixels tall and I can't click on anything. I tried to resize the window and it snapped to show just the window bar at the top and wouldn't budge again. Closed KSP. Open AGAIN, it instantly loads into the unusable window bar thing and won't work. Getting desperate, I removed all my mods and tried to launch on both x86 and x64, neither of them actually did anything when I clicked them, nor showed up as a process in system monitor. I rebooted my computer, redownloaded KSP, copied from my SSD to my HDD and still got nothing. This is probably an issue on mine rather than KSP's side but the game crash before this happened did make me suspicious. Last-minute update before posting: I did get KSP to open by running it as root from the command line, and it doesn't crash on loading the vessel. I blame the computer.

Issue: At startup, a window with just a black background, approx 1024x768, is shown for a couple of seconds, then the programme just shuts down. This issue is rather similar to this one, but at least in my case it does not affect the X session. Tried: 32 bit version, 64 bit version (by changing progr. properties in Steam client), both from Steam client and from terminal: same result. Executables in Steam KSP folder have x permission enabled. My system: *) KSP: 1.1.0 Steam version, fresh install, no mod, run under Linux (no previous version ever installed, just bought it!). *) HW: 4-core i5 3.33 GHz, 12GB memory, ATI HD 5770 1GB mem, 2 x 1280x1024 displays. hardinfo report can be found at here. *) SW: Linux Mint 17.3 (based on Ubuntu 14.04 LTS), latest available Catalyst driver. *) Player.log can be found here. No KSP.log generated (or I could not find it). I had great expectations from this programme and I am rather disappointed by this unfortunate start. I am a developer myself (of other kinds of sw) and I know too well bugs do happen; this seems a very basic issue, though. I also understand it might be rooted in Unity3D, rather than in KSP code: another example of how Unity3D multi-platform support sucks! Thanks for any help, M.