VAB/SPH inaccessible due to graphical bugs (game unplayable)

[Elen Sila]

KSP version – 1.0.2.0 (Steam, no mods installed).

Operating system – Ubuntu 14.04, 64-bit.

CPU – Intel Core I3-3217U.

GPU – Intel Ivybridge Mobile.

Memory – 5.7 GB.

What happens – on creating new game, space center, VAB, and SPH are all plagued by graphical bugs. VAB and SPH are completely unusable.

Screenshot gallery – http://postimg.org/gallery/36gpfwy2y/50b2ab05/ .

Bug report – http://bugs.kerbalspaceprogram.com/issues/5104 .

Edited June 4, 2015 by Elen Sila
changed tag to "solved".

[sal_vager]

Hi Elen Sila, your first pic is exactly like what we see when anti-aliasing is enabled on hardware that doesn't support the built-in Unity AA, so please try disabling anti-aliasing in the KSP settings.

If your graphics driver allows it, you can force anti-aliasing via the driver.

You also have this line in your log:

ERROR: ld.so: object '/home/jps/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

This can happen when using a 32bit program on a 64bit system and vice versa, but as it's just Steam it's not a big deal as you can start KSP from the KSP.x86_64 directly.

[Elen Sila]

Hi Elen Sila, your first pic is exactly like what we see when anti-aliasing is enabled on hardware that doesn't support the built-in Unity AA, so please try disabling anti-aliasing in the KSP settings.

If your graphics driver allows it, you can force anti-aliasing via the driver.

I disabled anti-aliasing, and the problem from the first screenshot went away. Thanks!

You also have this line in your log:

ERROR: ld.so: object '/home/jps/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

This can happen when using a 32bit program on a 64bit system and vice versa, but as it's just Steam it's not a big deal as you can start KSP from the KSP.x86_64 directly.

I ran the program directly from its installation directory, and the problem from the second and third screenshots went away. Thanks!

However, this is a rather inconvenient fix. I don't like creating desktop shortcuts for things, and would prefer to be able to run KSP directly from the Steam browser, like I run all my other games. Might there be any other fixes you could think of?

[sal_vager]

I'm not entirely sure, I get the same error when I start KSP via Steam as well but I don't get the missing VAB/SPH, and googling is turning up blanks, as does "ldd gameoverlayrenderer.so", it's not reporting any missing libraries.

My guess is it's using 32bit libraries supplied with Steam which aren't working on Linux 64bit, but there's no 64bit Steam client.

I'm going to have to look at this some more, but if you have the Steam overlay enabled for KSP, it may be an idea to turn it off.

Here's some info on LD_PRELOAD, it just loads a library, which we know is this overlay file.

This old page says to install ia32-libs to get 32bit programs to run on 64bit, but that package is deprecated and not available.

I think without a 64bit gameoverlayrenderer.so we're stuck.

But it may be worth looking at this, Arch users seem able to fix anything and they suggest installing the 32bit version of your gfx driver, which for Intel is the Mesa driver, so you could try sudo apt-get install libgl1-mesa-glx:i386

Edited June 3, 2015 by sal_vager

[Elen Sila]

I'm not entirely sure, I get the same error when I start KSP via Steam as well but I don't get the missing VAB/SPH, and googling is turning up blanks, as does "ldd gameoverlayrenderer.so", it's not reporting any missing libraries.

My guess is it's using 32bit libraries supplied with Steam which aren't working on Linux 64bit, but there's no 64bit Steam client.

I'm going to have to look at this some more, but if you have the Steam overlay enabled for KSP, it may be an idea to turn it off.

Well, turning the Steam overlay off fixes the problem…. Only now I can't take Steam screenshots.

Here's some info on LD_PRELOAD, it just loads a library, which we know is this overlay file.

This old page says to install ia32-libs to get 32bit programs to run on 64bit, but that package is deprecated and not available.

I think without a 64bit gameoverlayrenderer.so we're stuck.

But it may be worth looking at this, Arch users seem able to fix anything and they suggest installing the 32bit version of your gfx driver, which for Intel is the Mesa driver, so you could try sudo apt-get install libgl1-mesa-glx:i386

Okay so, this is weird. I did what you said, then reactivated Steam overlay for the game, then ran it from the Steam browser, and the problem disappeared! I'm now able to use the Steam overlay, and the VAB and SPH are both accessible again!

But the weird part is that, as you can see from that screenshot, it claims that I didn't actually install anything. It seems to be saying that I already had everything installed that I tried to install. But if that's the case, then why would the bug have gone away? It happened consistently every time I tried to start a new game, before. And yet now it's gone, despite that it would seem as though I haven't done anything.

I wish I would have checked, before deactivating the Steam overlay, and after reactivating it but before attempting to install that driver, whether I was still getting the graphical bug in the VAB/SPH. Then I might have known for sure what fixed it, or if it truly did just fix itself on its own (as it seems to have).

Ah well. Thanks for your help! The problem is resolved.

Edited June 4, 2015 by Elen Sila
forgot link