Jump to content

KSP Unloadable on Linux

Tortoise
 Share

Recommended Posts

Tortoise

Tortoise

Posted
Posted

Hello,

I can't seem to get my KSP to load on my Ubuntu installation...I'm using the KSP for Linux download on the website. The first time I downloaded it, I got it to load into KSP but some menu options were invisible so I restarted it and tried to load into KSP again, but the 2nd time it didn't load in. So I re-downloaded KSP and extracted it, then tried to load it again but the loading bar didn't move at all after 10 minutes. I searched for logs but there were no log files produced. The only thing I can really provide you with is a screenshot of the folder:

Fk7UwKB.png

 

Launcher.x86_64 didn't work so I tried KSP.x86_64 and that's when the bar got stuck loading at it's first point. (I believe it said something like "Loading assets ..." or something along those lines).

 

Link to comment
Share on other sites
Kerbal101

Kerbal101

Posted
Posted

Hello, Tortoise.

This is a known problem since 1.1.
The core issue is current Unity 5 OpenGL renderer that appears to have issues with Linux graphics stack.

Prior, in 1.0.5, the x86_64 Linux build was rock-stable with the only graphical issue being incorrect fairing rendering in SPH / VAB:

After 1.1 with upgrade from Unity4 to Unity5, the fairing bug was fixed, however this happened:

http://bugs.kerbalspaceprogram.com/issues/9341

 

The best solution is to force Unity5/KSP to use a subset of OpenGL using "-force-glcore" parameter, which may cause KSP to sometimes hang on start, but after that works good.

I have tried the suggested in the bug above method to edit the KSP configuration manually and reduce the resolution of screen. This fools font renderer and fixes the fonts, but it also causes Navball burn gauge glitch - it starts to look weird. Also it brings rather interesting effect of subpixel antialiasing at zero GPU/CPU cost (because whole screen is rasterized into one-pixel-smaller final 2d render viewport), which also causes KSP to go unstable over time and then reset the resolution automatically. Which means bugged text is back on next start.
 

Example of similar post:

 

Link to comment
Share on other sites
AmenRa

AmenRa

Posted
Posted (edited)

Having the same issue. KSP_X64 1.05 worked flawlessly. I upgraded to 1.1.3 and it crashes the X desktop when starting.
I performed a fresh install of 1.1.3 and removed my ~/.config/unity3d folder. Still have the issue.

OS: Gnome Ubuntu Desktop16.04.00 LTS x64 (with all updates) 

Build.txt
build id = 01289
2016-06-21_20-12-27
Branch: master

/var/log/syslog 

Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: disconnected
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): connected
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): Internal TMDS
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): 330.0 MHz maximum pixel clock
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: disconnected
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): connected
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): Internal TMDS
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): 330.0 MHz maximum pixel clock
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:40 eerlon gnome-session[10481]: (gnome-shell:10539): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
Jul 22 06:57:40 eerlon gnome-session[10481]: (gnome-shell:10539): Gdk-ERROR **: The program 'gnome-shell' received an X Window System error.
Jul 22 06:57:40 eerlon gnome-session[10481]: This probably reflects a bug in the program.
Jul 22 06:57:40 eerlon gnome-session[10481]: The error was 'BadAlloc (insufficient resources for operation)'.
Jul 22 06:57:40 eerlon gnome-session[10481]:   (Details: serial 52097 error_code 11 request_code 12 (core protocol) minor_code 0)
Jul 22 06:57:40 eerlon gnome-session[10481]:   (Note to programmers: normally, X errors are reported asynchronously;
Jul 22 06:57:40 eerlon gnome-session[10481]:    that is, you will receive the error a while after causing it.
Jul 22 06:57:40 eerlon gnome-session[10481]:    To debug your program, run it with the GDK_SYNCHRONIZE environment
Jul 22 06:57:40 eerlon gnome-session[10481]:    variable to change this behavior. You can then get a meaningful
Jul 22 06:57:40 eerlon gnome-session[10481]:    backtrace from your debugger if you break on the gdk_x_error() function.)
Jul 22 06:57:40 eerlon kernel: [55299.299182] traps: gnome-shell[10539] trap int3 ip:7f935a53ca6b sp:7ffd09ecd4d0 error:0
Jul 22 06:57:40 eerlon gnome-session[10481]: gnome-session-binary[10481]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
Jul 22 06:57:40 eerlon gnome-session-binary[10481]: WARNING: Application 'gnome-shell.desktop' killed by signal 5
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: disconnected
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): connected
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): Internal TMDS
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): 330.0 MHz maximum pixel clock
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: disconnected
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): connected
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): Internal TMDS
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): 330.0 MHz maximum pixel clock
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (II) NVIDIA(0): Setting mode "DVI-I-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (II) NVIDIA(0): Setting mode "DVI-I-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DVI-D-0: nvidia-auto-select @1920x1080 +1920+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: disconnected
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): connected
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): Internal TMDS
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): 330.0 MHz maximum pixel clock
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: disconnected
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): connected
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): Internal TMDS
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): 330.0 MHz maximum pixel clock
Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0):
Jul 22 06:57:41 eerlon gnome-session[10481]: current session already has an ibus-daemon.

 

~/.config/unity3d/Squad/Kerbal Space Program/Player.log 

Selecting FBConfig
GLX_FBCONFIG_ID=167
GLX_BUFFER_SIZE=32
GLX_DOUBLEBUFFER=1
GLX_RED_SIZE=8
GLX_GREEN_SIZE=8
GLX_BLUE_SIZE=8
GLX_ALPHA_SIZE=8
GLX_DEPTH_SIZE=24
GLX_STENCIL_SIZE=8
GLX_SAMPLES_ARB=0
GLX_SAMPLE_BUFFERS_ARB=0
GLX_CONFIG_CAVEAT=NONE

Desktop is 3840 x 1080 @ 60 Hz
Initialize engine version: 5.2.4f1 (98095704e6fe)
GfxDevice: creating device client; threaded=1
GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX: 1048576
OpenGL:
    Version:  OpenGL 4.5 [4.5.0 NVIDIA 361.42]
    Renderer: GeForce GTX 750/PCIe/SSE2
    Vendor:   NVIDIA Corporation
    VRAM:     1024 MB

.....

Load(Texture): Squad/Parts/Aero/wings/Wings
 
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64)

Load(Texture): Squad/Parts/Command/Mk1-2Pod/ladder
 
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64)

Load(Texture): Squad/Parts/Command/Mk1-2Pod/mk 1-2 external shell Variant-Hatch NRM
 
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64)

 

This solution seemed to work for me: 

$ ./KSP.x86_64 --force-glcore

 

Edited by AmenRa
Link to comment
Share on other sites
Kerbal101

Kerbal101

Posted
Posted
6 hours ago, Tortoise said:

Eh, surprisingly none of these solutions worked. Oh well, I'm probably going to just wait for an update and see what happens...Here's the log file though:

https://www.sendspace.com/file/9ehotb

Lets make sure you are doing it correctly.

Go to your KSP Linux installation (I have a GOG version and installed into ~/GOG/KSP), find the actual binary (there are two of them) and open a terminal there.

 

In terminal, run each string below once.
If the game glitches or hangs - close it by alt-tabbing and "xkill"ing.
Attempt to run each string three (3) times, only after third unsuccessful launch try next one.
  

./KSP.x86_64 --force-glcore
./KSP.x86_64 --force-glcoreXX

where XX is one of the following: 45, 42, 41, 40, 33, 32  - like ./KSP.x86_64 --force-glcore32

Here is what this string does: https://docs.unity3d.com/Manual/CommandLineArguments.html  and yes, it works on Linux.
The first will force autodetection,  but the second will force exact OpenGL interface explicitly declaring OpenGL 4.5 featureset (glcore45) or OpenGL 3.3 featureset (glcore33).

Currently Unity5 (KSP 1.1+) seem to have big problem detecting exact featureset of the current system/driver and only limiting exact OpenGL interface manually helps.
Failed detection leads to crashes on start or absent text in the game.

Again, sometimes it won't work on first run, so run each at least 3 times in succession until your issue is solved. Make sure also that you have TEXT in MainMenu->Settings as one of the sideeffects this bug can cause is an absent text in main menu and rightclick on vehicles.
 

I am also affected by this btw and workaround helped.

Xeon X5647, HD5850, Debian stable with kernel and drivers from backports (kernel4.6, Mesa 11.1.3), opensource radeon driver, current KSP (1.1.3 GOG-12)

Link to comment
Share on other sites
Tortoise

Tortoise

Posted
  • Author
Posted
10 hours ago, Kerbal101 said:

Lets make sure you are doing it correctly.

Go to your KSP Linux installation (I have a GOG version and installed into ~/GOG/KSP), find the actual binary (there are two of them) and open a terminal there.

 

In terminal, run each string below once.
If the game glitches or hangs - close it by alt-tabbing and "xkill"ing.
Attempt to run each string three (3) times, only after third unsuccessful launch try next one.
  


./KSP.x86_64 --force-glcore

./KSP.x86_64 --force-glcoreXX

where XX is one of the following: 45, 42, 41, 40, 33, 32  - like ./KSP.x86_64 --force-glcore32

Here is what this string does: https://docs.unity3d.com/Manual/CommandLineArguments.html  and yes, it works on Linux.
The first will force autodetection,  but the second will force exact OpenGL interface explicitly declaring OpenGL 4.5 featureset (glcore45) or OpenGL 3.3 featureset (glcore33).

Currently Unity5 (KSP 1.1+) seem to have big problem detecting exact featureset of the current system/driver and only limiting exact OpenGL interface manually helps.
Failed detection leads to crashes on start or absent text in the game.

Again, sometimes it won't work on first run, so run each at least 3 times in succession until your issue is solved. Make sure also that you have TEXT in MainMenu->Settings as one of the sideeffects this bug can cause is an absent text in main menu and rightclick on vehicles.
 

I am also affected by this btw and workaround helped.

Xeon X5647, HD5850, Debian stable with kernel and drivers from backports (kernel4.6, Mesa 11.1.3), opensource radeon driver, current KSP (1.1.3 GOG-12)

None of these worked sadly. I tried all of those, even the one without the numbers.

Link to comment
Share on other sites
Requia

Requia

Posted
Posted

glcore is for broken graphics people, if its crashing you need -force-gfx-direct

Though I recommend just using 1.0.5 since that seems to badly hurt performance (or maybe that's just 1.1.3 in general). The Unity 5 upgrade is mainly useful for Windows anyway.

Link to comment
Share on other sites
radonek

radonek

Posted
Posted

If that "'BadAlloc (insufficient resources for operation)'" in syslog is related, you are low on some resource well outside of unity or game. could be memory, file handles, shm or anything… If you want to give it a try, run it through strace and pm me what it says. (command will look like this: "strace ./KSP.x86_64 2> trace.log")
 

Link to comment
Share on other sites
Stone Blue

Stone Blue

Posted
Posted
On 7/21/2016 at 1:52 AM, Deimos Rast said:

also, there is always a log generated, it's just hard to find on linux

go here:

Linux: ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log

Sorry, but I disagree.... There is always a log generated, IF you get passed a certain point during loading...

When I try to start KSP, it crashes JUST as the loading screen starts (black screen, no Kerbal graphic), and there are NO logs generated...

Link to comment
Share on other sites
Deimos Rast

Deimos Rast

Posted
Posted (edited)
4 hours ago, Stone Blue said:

Sorry, but I disagree.... There is always a log generated, IF you get passed a certain point during loading...

When I try to start KSP, it crashes JUST as the loading screen starts (black screen, no Kerbal graphic), and there are NO logs generated...

I see you like being that guy:sticktongue:

Yes, if it makes it past the first screen and doesn't immediately flash closed.

As for your problem, I've found, personally (as in, I can't say this is generally the case), when it consistently crashes before even getting into a loading screen, it's been a graphics driver incompatibility.

I recently updated my graphics drivers and KSP wouldn't load (remember to restart first too:P); I ended up having to juggle things around in my install. If it doesn't load with just SQUAD? Try a different driver. Doesn't make much sense to me, but, it worked for me.

Mileage may vary.

Edit:

sounds like you (OP) have a different problem though.

Edited by Deimos Rast
Link to comment
Share on other sites
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...