sal_vager

Okay, maybe it's using the wrong resolution, your Player log has this. If you delete the prefs file at ~/.config/unity3d/Squad/Kerbal Space Program/ and the settings.cfg from the ~/.steam/steam/steamapps/common/Kerbal Space Program/ folder will the KSP.x86 file start KSP when used directly?

Sorry to go back to sound @reinderien but can you try this?

Okay so graphics have got to be fine, have you tried checking KSP's permissions? It can fail to run if files are read only.

@reinderien here's some things to try. https://unix.stackexchange.com/questions/27918/getting-opengl-to-work-under-ubuntu

I think AMD dropped the proprietary driver for the HD 7 series, but the open driver should be detected by hardinfo. As for other games, KSP runs on Unity 5 so the best games to try are Pulsar lost colony, Besieged and Satellite reign, unfortunately I don't know of any demos that use Unity 5.

By the way @reinderien I am using the open source xserver-xorg-video-radeon driver.

I just realized it was in an archived section, I have moved it to the public tracker so it is now accessible. I have not heard of issues on Lubuntu for a while, and I know KSP will run on Linux, your logs are odd in that htey end very soon after launching, there is not even time for KSP to be loaded, your Player log should have lines like this. So it suggests the Unity engine is having a problem on your PC, I know you have the LibXcursor library so it can't be that, but I am at a loss to know what is wrong here. One clues is this from your hardinfo report. This is not right, and the Unity engine requires direct rendering to be able to display an image, here is mine for example. I'm using an R7 GPU built into my AMD-A8 CPU. So it looks like your graphics driver is bad @reinderien, and you will need to fix it.

Ahh, Lubuntu, if I remember right Lxde does not include Pulseaudio and the Unity engine requires it. Please take a look here. Specifically at Kspflo's post here. And Lysius's post below about using this with Steam. Hopefully this will fix KSP for you @reinderien.

Hi John, any such links to a product or service would need to be approved by Squad, try asking @Badie or @UomoCapra

Hi @reinderien, I'm sorry to see you're having further issues, but I don't think I can help with the information you have provided. Can you please tell me which Linux distribution and version you are using, and your hardware. You can get a hardware report using the hardinfo Linux package, available in most package managers. Does the KSP.x86 work for you? And can you describe what you see when you run KSP,x86_64 please.

Yes! @DarkOwl57?

I honestly have no idea what to suggest at this point. I know AFBW uses SDL to talk to xinput on Windows, I don't know what Unity uses to get xinput values, something proprietary I guess. Unity on Linux and MacOS grabs the raw input, maybe that's why I don't have this issue. I remember Microsoft broke xinput with the 10th anniversary update, but surely that's fixed by now.

Just a thought, are you using a USB hub? With many hubs I've used only the first four ports provide the full 2 amp supply and even that is split between the ports. For example I have a USB webcam that struggles to work and produces a corrupt image if I use port 5, 6, or 7 on my hub, or if other things are plugged into ports 2, 3 and 4 with the webcam in port 1, so I have to plug it into the PC directly. It's possible your sticks just aren't getting enough power. If you have spare USB ports on the back of the PC try those instead.

This is a rather old thread but it's important to know what -nolog is and what it does. First, it's a Unity3D engine command line switch, not something Squad added to KSP. Second, it only disables the Unity3D log, which is the output_log.txt on Windows, and the Player.log on Linux and MacOS. The KSP.log is not affected. So if you have a mod spamming the logs it's best to deal with that mod, as log writes will still occur.

Closing as the OP says it's 'solved' and I don't want this becoming an argument.

I'll just Quote Red here. As far as I know a second gas giant was discussed, but that is not the same as promised. Edit: If anyone can find a promise for Gas giant 2 I'll add it to the Already Planned section of the Common Suggestions thread.

Just going to quote this bit. And this bit, the Mission files will be like craft and saves, and can be shared with other players, whether created by a modder or anyone else If a craft or save requires mods you still need to install those mods, so a Mission that uses mods would require those to be installed.

I think some people are getting confused and seeing the month but not the year. The cut-off point to be eligible for the expansion for free is May 2013. That date has nothing to do with the release of the expansion.

Moved these to a new thread, please keep discussion of iffy versions of modular flight integrator out of the main thread, thanks :)

1.2.9 is the pre-release for 1.3 which is the localization update, the expansion is another thing that is coming between a short and long while.

This is incorrect, 1.3 will be soon as 1.2.9 is already in pre-release for public testing, but the expansion will not be ready for a while.

Hi @JChasaDog, I'll quote the Kerbal Space Program FAQ to answer this one. Your account will still show that you bought KSP before the cut-off date so you will still be eligible. Hope this helps.

Did you change the UI scale? That needs a restart to work properly.

Surely you jest.

Closed by OP's request. Please see this thread.