sal_vager

Support for DirectX 11, 12 (or 10 for that matter) depends entirely on the Unity3D game engine which by default exports to DirectX 9 on Windows platforms, and OpenGL ES on Linux and OSX. Looking at KSP it's not the kind of game that relies on graphical fidelity, there will be much greater gains to be had from the physics engine improvements. Also you can already force DirectX 11, it's somewhat broken but it works, it's up to Unity to fix this however.

Gentlemen I'll not ask again, stay on topic and refrain from personal attacks and arguing with each other. On second thought, this thread has strayed from its original topic and there's not much left to be said, you are all able to follow this in the news to see how it develops, but this is a site for a computer game, not political argument, so this thread is now closed.

I've been looking at far too many Linux support threads today, I thought I'd brought up that command here as well. LC_ALL=C just corrects for some languages swapping the comma and period when used with numbers, as it's working when KSP.x86_64 is used directly you should be fine. It may be the Steam overlay, it doesn't work well on 64bit Linux, try turning it off in the Steam client options.

They are all the same, they use something called Mono, which is a cross platform version of .NET If you stopped using LC_ALL=C I'd try it again, as while it's built into the KSP.x86, it wasn't added to KSP.x86_64 as at the time it was still considered experimental and unsupported by Squad. Because of what LC_ALL=C fixed it'd be a good idea to delete the settings.cfg again, basically always start KSP.x86_64 with LC_ALL=C just in case.

Okay it looks like an addon this time, the last lines show this: So I think you need to update it

Glad it's working though I may have done more harm than good on this occasion My advice, don't mess with the drivers unless you have to Have fun with KSP on Linux and if you have any issues I'll try my best to help.

Another member, E.Nygma, says he solved this by changing to the Mate desktop with the Slim display manager, would you be able to test this?

Does this still happen when you run the KSP.x86_64 without additional commands?

Okay try starting KSP.x86 and KSP.x86_64 directly from the game folder, this avoids Steam causing any issues. I just spotted this near the end of the log. It may indicate a bad file even with the new install, can you doublecheck it by running a Steam cache verification please.

The open source drivers do share a lot of parts, so it may be worth testing the drivers from the Oibaf PPA, these are more recent than those in the Ubuntu repositories and include updates to X as well.

The good thing about Linux is that it doesn't really matter what desktop environment (DE) you prefer, you can install nearly all of them on any distribution, so for example Kubuntu is just Ubuntu with the K desktop instead of Unity. Most distributions have alternate DE's in their repositories and it's usually just a case of installing them, logging out selecting the new DE from the login options and logging back in. Ubuntu 15.04 has both Slim and Mate (and many others) in the repository so they can by installed graphically via Synaptic or from the terminal with "sudo apt install mate-desktop slim" for example. Display managers (DM's) are installed the same way, changing to another DM is not too much harder and can be done by running "sudo dpkg-reconfigure gdm" in a terminal or by editing a file, more info here. Slim is just providing the login screen though before starting the Mate desktop, what's also interesting is that E.Nygma is using the oibaf drivers, these are more recent x server and mesa drivers which may simply not have this issue, regardless of DE or DM.

Not run into issues with it on Ubuntu 64bit, not for a while anyway, it did used to be bad but there were some changes made to it around .90

Yeah Steam doesn't like Nouveau, and Valve just recommends you use the proprietary driver.

Okay, the card is newer than the available drivers support for that version of Ubuntu, meaning you'd need to add the official personal package archive (PPA) that contains them or use a newer version of Ubuntu, as due to updates there's separate repositories for each version. If it helps I'm using Ubuntu 15.04 here, which has the 346 driver in the repository. But I suggest just installing the driver you previously used as it was working, and then posting the KSP.log from the games folder, and Player.log from ~/putyourusernamehere/.config/unity3d/Squad/Kerbal Space Program/ so I can see what's going on.

So you didn't try libgl1-mesa-glx:i386 first, okay well I'd have liked to have known if that would have solved it, and I'd have liked to have seen your logs which I mentioned a few times, as they would have told me why it wouldn't start. But look on the bright side, now you can start from a clean slate What's your gfx card btw?

The one I linked But it shouldn't be needed yet, sorry I don't want to confuse you. KSP does run fine on the driver from the Ubuntu software repository, it should run "out of the box" on an Ubuntu 14.04 LTS 32bit install, but as that comes with the open source graphics driver pre-installed by default, performance with KSP is slow. Ubuntu has a graphical tool to install proprietary drivers but it's a bit old now, so probably the easiest way to make Ubuntu ready for KSP on Steam with Nvidia hardware is to open a terminal and use: sudo apt install nvidia-331 nvidia-settings steam Reboot after it's done and that should be it, that will get the 32bit KSP working on a 32bit Ubuntu OS, for 32bit KSP on a 64bit Ubuntu you'd need this: sudo apt install nvidia-331 nvidia-settings steam libgl1-mesa-glx:i386 That installs the 32bit stuff so 32bit KSP will start on a 64bit OS. 64bit KSP should only need the first line (sudo apt install nvidia-331 nvidia-settings steam) to run on a 64bit copy of Ubuntu, but Steam will start the 32bit by default, so the Steam launch option needs this added to it: &command&_64 And the KSP.x86_64 is not marked as an executable file, so it needs to be set as executable by right clicking on it and changing its properties. If you had an AMD card the commands above would be a little different: sudo apt install fglrx fglrx-amdcccle steam And: sudo apt install fglrx fglrx-amdcccle steam libgl1-mesa-glx:i386 Respectively. Then you just start Steam, login, and play If there's an error it's generally a good idea to google first as someone will have run into it, another search for your error shows this on the steam forums <--- link So it definitely looks like the graphics driver is having an issue, and as you are using a 64bit OS I suggest you try this first: sudo apt install libgl1-mesa-glx:i386 And checking that the KSP.x86_64 is marked as executable, then try removing the Nvidia driver and reinstalling if that doesn't fix it

There's a few in the repo, the latest one is numbered 331 though it's possible to add more recent versions with Ubuntu's official repo for proprietary drivers, there's install instructions there too.

It's still in development

Yeah default behaviour is to not clutter the desktop with everything you install, that's just untidy, but if you right click the application in the menu there should be the option to add it to the taskbar or the desktop. It's really hard to tell you the particulars of your system without physically sitting in front of it and seeing how you have it set up, but your system files should be there, try enabling hidden files with Control+H

Okay, I have not run into this one personally but a quick google shows this. http://ubuntuforums.org/showthread.php?t=2293235 I guess something broke, I don't know what driver you installed but if you stick to the one in the repo (331 I think) and the Steam client from the repo (not the one from the website) it will be fine.

Oh wait a sec I'll find the link, Steam ships with a broken library. Edit: Here you go. https://askubuntu.com/questions/614422/problem-with-installing-steam-on-ubuntu-15-04

Will a quicksave then quickload fix this?

ChewieRolo, yep, the claw vessel just shot off into space leaving the adapter behind, It's like gravity just switched off for those parts.

Yeah It'll do that if you don't change username to your user name, but if it didn't list anything then KSP has all the libraries it needs. The KSP.log and Player.log will still be written if KSP.x86_64 starts but crashes, and those logs will say what is going on, if they aren't made then try starting KSP..x86_64 via the terminal, it might say something like "no permission to run this program". If so, the KSP.x86_64 can be made executable in the right click properties.

Alt+Enter should still work to swap between windowed and fullscreen Crocket, that will save you having to go to the settings screen