Kerbal Space Program

Also reported as 1.1prerelease Bug #7493

Lysius wrote:

Also reported as 1.1prerelease Bug #7493

Oh, sorry. I looked to see if it was already reported, but apparently I didn't look hard enough. Feel free to delete this.

sal_vager wrote:

Aristaeus, try running KSP with the -force-glcore command line argument, this is a Unity engine argument that forces Unity to detect and use the best OpenGL version on the system.

https://docs.unity3d.com/Manual/CommandLineArguments.html

It's working! Thanks a lot!

For me, using the '-force-glcore' option causes startup crashes: http://bugs.kerbalspaceprogram.com/issues/9461
'-force-glcore33' works better (no crash), provided I disable shadows in settings.

I've the same issue on my Debian Sid, using GOG's version of KSP, with radeonsi driver on R9 380X.

Using -force-glcore makes the game crash, but the game works (and the settings bug is fixed) with -force-glcore33 or -force-glcore40. Oddly with -force-glcore41 (the last official supported OpenGL version on stable Mesa for radeonsi) the whole game screen is entierly black (apart from mouse cursor).

I'll try -force-glcore42/-force-glcore43 with latest git Mesa (which has support for OpenGL 4.3 on radeonsi) later on.

Thanks for the info guys.

kilobug please keep us updated.

I've been looking at other bug reports, and it affects all users using Mesa 11.x series as far as I can tell.

This is pretty much anyone using Linux except those using fglrx (who experience other issues) and people using the NVidia proprietary drivers, who have no issues that I know of.

This bug is likely upstream in Unity and makes me question Unity's QA department if a huge chunk of the UI code fails on the driver that ships with most Linux distros. It's as if they only tested it on nVidia proprietary drivers.

So I did a few more tests (Debian Sid, Radeon r9 380X).

Using stable mesa (11.2.1) from Debian Sid (which officially supports OpenGL 4.1) :

• using no option or -force-glcore31 gets the bug as described : various menus (options, load, ...) are empty ;

• using -force-glcore or -force-glcore42 gets a segfault ;

• using -force-glcore32 to -force-glcore41 leads (apparently randomly) to one of the two outcomes : 1. everything works nicely 2. the whole screen is black except for the mouse pointer.

Using git mesa (from oibaf's ppa) (which officially supports OpenGL 4.3, but only with LLVM 3.9, which I don't have) :

• using no option or -force-glcore31 gets the bug as described : various menus (options, load, ...) are empty ;

• using -force-glcore gets a segfault ;

• using -force-glcore42 with MESA_GL_VERSION_OVERRIDE=4.2 set too (to force attempting to use GL4.2 despite missing llvm) works fine ;

• using -force-glcore32 to -force-glcore41 works fine.

I'll try to make some tests with LLVM 3.9 later on.

So at least some improvement with latest git, hopefully when we'll have Mesa 12.0 with LLVM 3.9 stable in a couple of months it'll work great with stable software.

For now, the best solution is to use Git Mesa (with oibaf's ppa it's pretty easy on a Debian-based distro) and -force-glcore41 switch (for radeonsi cards).

Tested quickly on my laptop, which has an integrated i3 Haswell GPU, with the same software (Debian Sid, Oibaf's PPA, KSP from GOG), I have the same behavior : some empty menus by default, but all works with -force-glcore33 (didn't try other options, the game is slow to load on this low-specs laptop).

Same here.

KSP version 1.1.2.1260
Mesa 11.2.2
LLVM 3.7.1
radeonsi driver (Radeon R7 370)

-force-glcore helped. Much thanks for that.

Here are some observations from another piece of hardware:

Intel Core i7-6560U (Skylake)
Intel Iris Graphics 540
3200x1800 screen (in fullscreen mode at full resolution for these tests)
Kerbal Space Program 1.1.2 64-bit
Arch Linux x86_64
xf86-video-intel version: 1:2.99.917+654+ga508b11
mesa version: 11.2.2
llvm-libs version: 3.8.0

I'm using KDE/kwin, but I used openbox for these tests to avoid any confusion with http://bugs.kerbalspaceprogram.com/issues/7695 . According to glxinfo, OpenGL 3.3 is the highest version supported.

Arguments:                     Result:

none                           empty settings, menus, etc., exactly as in OP screenshots
-force-glcore                  everything seems to work fine
-force-glcore30                empty settings, menus, etc., exactly as in OP screenshots
-force-glcore31                empty settings, menus, etc., exactly as in OP screenshots
-force-glcore32                everything seems to work fine
-force-glcore33                everything seems to work fine

This problem is universal with all versions of OpenGL on Linux Mesa drivers.

It seems to be fixed by running fulllscreen at 720x1280 on widescreen monitors. I'm not sure what resolution it works at on non-widescreen.

As a note, could someone test with the Force GLES settings.

It wouldn't be a good idea to include those lines by default as it might cause issue with other players, and as they are Unity commands and not from Squad we cannot provide support if they don't work.

It definitely is a driver issue, for example this issue doesn't show with Nvidia drivers, I've not heard of it with nouveau either.

The problem here is that there's nothing Squad can do about issues at the graphics driver or game engine level, except to recommend the player uses a working driver.

But it's good to know that the oibaf ppa solved this for you, at least on your laptop, that suggests that this issue will eventually be resolved as the mesa driver improves support for features used by Unity.

It wouldn't be a good idea to include those lines by default as it might cause issue with other players

+1

Such a workaround can be suggested for users, but should not be hard-coded.

It definitely is a driver issue, for example this issue doesn't show with Nvidia drivers, I've not heard of it with nouveau either.

When a buggy code (causing 'undefined behaviour' according to the specification) is working with one driver and is not working with another one, then it is not a driver issue, but the engine code issue. And this might be the case here.

The problem here is that there's nothing Squad can do about issues at the graphics driver or game engine level, except to recommend the player uses a working driver.

Squad may also work with driver and engine providers to fix the bugs. The first think I would try is to reproduce this error with newer Unity version (even if other parts of the game are not ready yet) and if it helps, try to get the fix back-ported.

I confirm that on my two setups (desktop with Radeon RX380 using mesa/radeonsi, and laptop with Haswell integrated graphics, using mesa/intel) the issue is fixed on version 1.2.0 (from gog). Congrats ! :)