sal_vager

Looks like the Unity engine is crashing before anything from KSP is loaded, this can happen when the engine can't find a 3D graphics driver which is essential for a Unity game to run, or when the Unity engine requests a graphics window that is too large for the window manager to cope with, causing OOM Killer to kill the Unity/KSP process.
So make sure you have a 3D graphics driver installed and working (make sure 3D applications work) and delete the KSP settings.cfg and the prefs file at ~/.config/unity3d/Squad/Kerbal Space Program/ before starting the game.
If it still doesn't work after that you will need to provide more information on your system, see the sticky on getting support

Hi BadLeo, on searching your issue it seems you need to check your power settings in Windows, make sure the notebook is plugged in and is set to Performance mode, not to a powersaving mode.
In powersaving mode the Nvidia can be disabled, this is why KSP is using the Intel GPU, this overrides the Nvidia panel settings.
If you still have trouble then I suggest you install the latest Nvidia graphics card driver, some Windows updates can break drivers even though they seem to be installed, don't forget to reboot so the changes take effect.
Hope this helps.

Heya, KSP looks for save files whenever the load dialogue is opened, so it's fine to copy the saves back either while KSP is running or before, you may want to avoid overwriting your scenarios and training folders though if your backups are from an earlier release.
Hope this helps.

Looks like you need to install a graphics card driver and restart the PC, KSP will not work with the default Windows driver.

Please ensure the stick is plugged in before starting KSP, as KSP needs the enumerated list of controller names that the Unity engine makes when it is started.
If the controller does not have a hardware name that Unity can find using Input.GetJoystickNames() then KSP won't be able to use it, sorry

Yes!, before deleting everything I can tell you the issue, one craft in the VAB folder is corrupted, it could be the craft you were using or the autosaved ship, move either of those to another folder and try again, this should work while KSP is running, you just need to reopen the vessel load window.
Also, moving to tech support.

Actually yes, this is what progress looks like 
I think you need this.
Because of this.
http://bugs.kerbalspaceprogram.com/issues/11382
Which Unity knows about and have switched to SDL in Unity 5.6, which might fix it.

Hi reinderien, I can only assume the distribution you are using does not have libcurl installed, you may need to install both the i386 and 64bit versions to get both versions of KSP to start.
Unity officially supports Ubuntu and SteamOS, which should have libcurl installed by default.
I know that 1.2.2.1622 works on Linux Mint 18.1 and Xubuntu 16.04 and 16.10, you may also want to ensure libxcursor is installed as it is required by the Unity engine and some recent distros are omitting it.

Hi @KerbalAustronaut, there is a problem with KSP on MacOS sierra, so I assume you're using sierra, basically Apples Gatekeeper won't let it run.
But this should fix it.

I find this happening sometimes, it's almost like 1 pixel of mouse movement is too far, have you tried moving the view to see if it has an effect?

You confused me with this then,
 
By all means, see if there is any change.
Also, try resetting KSP's settings, do this by deleting the settings.cfg in the games folder, and to ensure there's no unwanted settings also delete the prefs file from /home/username/.config/unity3d/Squad/Kerbal Space Program/

Still works, see Stone Blues post.
 

Hi @Dalgaim, I am sorry to tell you but this is a bug in the Unity3D game engine sending bad window dimensions to the operating systems window manager, this occurs with Unity3D tutorial projects as well, that contain no KSP code or shaders, and selecting different render modes in the Unity3D editor doesn't change this (options are OpenGLcore first, OpenGL2 first, or auto).
Unity Technologies have been informed but no fix has been provided yet, the only 100% workaround I know of is to use the xfce window manager xfwm, which can handle the bad call.
There's more info here.
I'm using Cinnamon currently, and I leave KSP alone until it's finished loading, but even then it still crashes Cinnamon sometimes when I drag KSP.
Sorry I can't help any further with this, it's totally beyond Squads control.

Hi @Tarsirrus, have you tried right clicking on them in the SPH and setting their control authority to -100 ?
Control surfaces in KSP check their position relative to the CoM, so they can invert as fuel is consumed, so try moving them a little as well.

Nevermind, I remember, it's the difference in eye offset between male and female Kerbals, if you want the lower view you need to use a female.

It's also in the Launcher.

It depends on what you mean by slow @53miner53, the asset bundles should not add more than a few seconds to the load time unless you are running Hamachi/LogMeIn or similar, or have other unused network adapters.
Loading can be slow even with one network adapter, but keeping your drivers current should prevent that (don't rely on the drivers built into Windows).

@CAKE99 can you try a fresh download?
Also if you can spare the bandwidth, does the 32bit version work for you?

This should do it.
 

Hi @omelaw.
Run in AMD compatibility mode forces the Unity command line argument -force-gfx-direct
Do not produce log adds the -nolog command line argument.
Run in framless window adds -popupwindow
Run in extended character set mode prepends LC_ALL=C on Linux and OSX.
Run 64 bit player calls the 64bit binary on the platform if there is one (not needed for OSX)
Hope this helps.
 

Alt+enter is a Unity engine thing, not programmed by Squad, and doesn't even work on Linux or OSX.
Unlike the fullscreen option in Settings, alt+enter just stretches the window without giving KSP the chance to resize things properly.

Okay I think I know what's happening, these errors show up in logs after players have used the aero overlay, then highlighted their vessel by mousing over it.
Try disabling the highlighter in flight, it's a settings screen option, you should find these crashes stop occurring.

Hi @AaronLS and @Ultimate Steve, Backspace was used for reset camera and for the abort action group, so was causing trouble, so the camera reset was changed to backquote ( ` ) to the left of the 1 key and above the Tab, also making it a bit more ergonomic.
Hope this helps!

Maybe try symlinking to the file, here's how to do it on Windows and Linux.

Hi @iSilver, KSP is limited to what the Unity3D engine supports.
Hope this helps.