Crash on loading - Ubuntu 15.04 64 bit with NVIDIA Quadro K1000M

[cfusting]

Behavior is as follows:

1. Start from the command line or launcher.
   
2. Screen goes black.
   
3. Screen returns to desktop with normal KSP loading screen in window. Mouse moves but the loading screen does not change.
   
4. Music starts.
   
5. Computer is totally unresponsive besides mouse moving. Cannot alt-tab or change workspaces. Eventually can get to virtual terminal to shutdown but this takes some time.
   

KSP version is: 1.0.2.0

From the Players.log log we have:

The referenced script on this Behaviour is missing! (many times)

Serialization depth limit exceeded at 'ThermalLink'. (many times alternating with the following)

Serialization depth limit exceeded at 'OcclusionData'.

I previously ran KSP on ubuntu 12 without issues on this machine. Any ideas?

Edited June 11, 2015 by cfusting

[sal_vager]

Hi cfusting, it's most likely the graphics driver, KSP really needs the proprietary driver for AMD or Nvidia cards, and make sure the driver is loaded, it's easiest just to reboot.

Ubuntu 15.04 has the Nvidia 346 driver in the repos now.

[cfusting]

Hi sal_vager. I am using the 346 driver as you suggest.

[sal_vager]

Hmm are you using the KSP.x86 or the KSP.x86_64? The x86 version can fail to run properly without some i386 components from the mesa driver.

Can you please upload your KSP.log to hastebin for me?

[cfusting]

I've been trying KSP.x86_64, although I did for kicks try the 32 bit version with the same result. Here is my KSP log: http://hastebin.com/zenoderezi.vbs

Also note my driver is 346.59 from nvidia-346 the recommended proprietary driver.

[sal_vager]

KSP detects the card so that's something, have you rebooted since installing the driver?

And are you using anything like Bumblebee?

[OddFunction]

I had issues like this when my resolution was set to anything other than 1920x1080. If you are not in 1080p, go to your settings.cfg and change these lines to what you see below:

SCREEN_RESOLUTION_WIDTH = 1920

SCREEN_RESOLUTION_HEIGHT = 1080

Maybe it will help. Maybe not.

[cfusting]

Yep restarted (few times actually). Note I was always using the 346, just from a different repo before.

I'm not using Bumblebee. I set the graphics card to discrete in the BIOS on startup to avoid the complications optimus can cause.

[cfusting]

mega_newblar's advice led me to the solution, set FULLSCREEN = True.

This feels like a bug. I'm going to submit it.

Thanks everyone for the help!

Edited June 11, 2015 by cfusting