Search the Community

Not sure where to post this since I'm new but I had severe performance issues with the Final Frontier mod installed under Linux that weren't present under Windows. It took me roughly 3 days to figure that out so I hope this helps somebody having the same issue.

Is there an estimate of time or cost or additional devs to get KSP2 to Gold status on ProtonDB in re: Linux Support? Is there a Linux build, and what are the regressions with ProtonGE and Steam's Proton Experimental? ProtonDB > KSP2: https://www.protondb.com/app/954850 https://www.protondb.com/app/954850?device=pc - PROTON_NO_XIM=1 - Toggle full screen in game but also -popupwindow (Bazzite is a Fedora Silverblue rpm-ostree distribution with support for Steam Deck and also Intel/NVIDIA/AMD; which ships ProtonUp-Qt with which ProtonGE 9-2 (2024-03) can be installed.) Are there Unity on Linux bugs that could be bumped?

Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Pop! OS Linux (Freedesktop SDK 23.08 (Flatpak runtime) (64 bit)) | CPU: AMD Ryzen 7 3800X 8-Core Processor | GPU: NVIDIA Corporation NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 | RAM: 15934 Mb There was a prior bug report: I discovered I was having the same issue as this prior postor using Linux, but the solution the threat ended on did not work for me. I did not have to enable any other options; Proton version is 8.0-5. Sounds like this may be a Linux-specific problem?

i recently installed ubuntu on my computer, and i tried running ksp on it and it keeps crashing just as its finished loading and often crashes the whole system with it. My computer is, admittedly, underpowered for ksp (1.4ghz core 2 duo, 4gb of ram and intel integrated gpu) but it was running fine on windows so i think its an os problem . I dont know how to send the logfile, but i looked through it and there were some warnings, but none at the end of the loading, which is when it crashes.

Microsoft or Apple (or Linux)? Which do you prefer?

I have a laptop with the processing power of half a brick. I have no GPU and KSP is using the graphics part of my Intel i5 CPU. I have Ubuntu 22.04 and I have what I think is the latest Mesa driver available on Ubuntu. I have 16GB of RAM and 8GB of swap. KSP version is 1.12.5. When I am building in the VAB or SPH, occasionally, every few minutes, my entire computer freezes for a minute or so. The music keeps playing, and the computer seems to be taking some input, though when I close the lid it doesn't go into lock mode. After waiting for the minute or so, one of the following happens: It unfreezes and everything goes back to normal, and I can continue playing the game. When this happens though, it starts freezing more often afterwards. KSP crashes. Discord crashes for some reason, and KSP continues playing. (rarely) It doesn't unfreeze for several more minutes, and it breaks a bunch of things in my computer that I have to fix by rebooting. I've been googling this for a few days now, and after checking my logs and comparing it to things, I am almost certain that the issue is with my Mesa graphics driver, and possibly something about something called DRI3. However, I also don't think downgrading Mesa is an available option for me, as I am not very knowledgeable about computers and a lot of important programs have dependencies on it. Also, I tried setting an environment variable on my steam launcher to disable DRI3 so that it would use DRI2 (which people say don't have that issue) and I checked that steam successfully sets the variable but I am not sure it's working and also the issue still happens with the variable set. I just tried recreating the issue. In the SPH, it froze and unfroze once, and then on the next freeze it crashed. I checked the Player.log file, and this is the last few lines: [...] seatExternalCmd added to ship - part count: 8 (Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35) seatExternalCmd added to ship - part count: 7 (Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35) seatExternalCmd added to ship - part count: 7 (Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35) Caught fatal signal - signo:6 code:-6 errno:0 addr:0x3e800031792 Obtained 12 stack frames. #0 0x007f91a6442520 in __sigaction #1 0x007f91a64969fc in pthread_kill #2 0x007f91a6442476 in raise #3 0x007f91a64287f3 in abort #4 0x007f91a329d86d in (Unknown) #5 0x007f91a44160cd in nouveau_drm_screen_create #6 0x007f91a384e9f6 in __driDriverGetExtensions_d3d12 #7 0x007f91a3849612 in __driDriverGetExtensions_d3d12 #8 0x007f91a32bfbc8 in __driDriverGetExtensions_d3d12 #9 0x007f91a330f7cb in __driDriverGetExtensions_d3d12 #10 0x007f91a6494ac3 in pthread_condattr_setpshared #11 0x007f91a6526a40 in __xmknodat I don't think the rest of the log is relevant, since it happens every single time I'm in the editor doing anything, but if you need it I will post the entire file once requested. I've been stumped with this for a long time, and KSP is not very fun when it crashes every time you want to try something new. If anyone could help me with this, I would appreciate it a lot. Thanks! Edit: I have been informed that "nouveau" (see the line in the log just before it crashes) is some kind of driver for Nvidia GPUs. I don't have an Nvidia GPU, and I don't know whether this was installed on Ubuntu by default or if I accidentally installed it trying to install something else (which I don't think is likely). This might be the cause of the issue, or it might be unrelated.

The latest version of the launcher shipped by Private division crashes on Linux Steam under proton. This is a BLOCKER for being listed as supporting Steam Deck for KSP2 and all Private Division Titles relying on Proton to run on Steam Deck. It also is a blocker for many other issues. Here is an upload of my crash logs so far. https://gist.github.com/Ruedii/84ffdc5e26ade36207ddac433c79b6e7

Really happy KSP2 has finally been made available. Posting this because I just want to help out if I can. At this point I'm certain that I'm experiencing this all the time. I especially notice it when the simulation seems to be especially strained. For example: when I'm trying to fly an SSTO with a lot of rapiers through the lower atmosphere of Kerbin. But even when the game is very responsive I still see this to some extent. At times I need to hold a directional key down for a while. I find that when I release the key, the game doesn't immediately notice the release. It behaves as if I'm still holding the button down. It will eventually realize that I've released the key. The amount of time it gets stuck seems to be proportional to the amount of time I had initially been holding the key down. I further observe that there is a memory aspect or queuing behavior that accompanies this. During the time while the game still thinks I'm holding the key down, it seems to be recording any key press/releases in a queue or something. Once it realizes that the key had been released all my key presses during that time are executed in the order I performed them. For example, when I need to hold S to "pull back on the stick" for while while I'm attempting to get my plane to pitch up. Once I release S the game behaves as if the key is still being held down, and the plane will keep pitching further and further up. While the game is in the state where it's ignoring my keyboard input... ...it seems to be all keyboard input. This includes keys like escape. ...Other input doesn't seem affected. The mouse keeps working as normal. This can be particularly odd. For example: Walking somewhere as a Kerbal involves me holding W to walk forward for a long time. It will get into a state where it thinks I'm still pressing W and so it will keep walking my Kerbal forward. And yet I can still steer the Kerbal with the mouse. KSP Version: 0.1.0.0.20892 Operating System and version: Ubuntu 20.04.5 LTS CPU and GPU models, any other system information which could be relevant - AMD Ryzen 5 3400G - NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) Description of the bug: see above - Expected Behavior: see above - Observed Behavior: see above Steps to Replicate: see above Fixes / Workarounds (if known..) - The only workaround I have is to avoid holding a key down for too long. This only works so well. A list of ALL mods. If the list is long, please consider using a spoiler window. - No mods. Other Notes / Screenshots / Log Files (if possible..)

ANSWER: Ensure Keyboard Layout matches your physical keyboard from KSP1.4 onwards (ie, 101-key, 105-key, etc) UPDATED ANSWER: Ensure you only have a single keyboard layout available! Having multiple layouts (eg, to switch between different languages) breaks KSP1.4 onwards. ---- So I re-downloaded a brand-new fresh install of KSP 1.4.3 for Linux using Steam. No changes to settings, no mods. Double checked and the keyboard layout matches my OS layout; changing this has no effect. No errors in the log file. Debian GNU/Linux 9 with KDE desktop. Launch the game, start a new stock game, create the first basic rocket, launch it, and in flight-mode, none of the standard keyboard keys (ie, letters) work. Ditto in the Editor; none of the "letter" shortcut keys work. The number keys and the control keys DO work (Shift/Ctrl to adjust throttle, R-Shift F12 to open Debug menu, ESC to pause, etc). In other parts of the game, the keyboard works normally: Settings - keyboard configuration; I can change the bindings (eg, Full-throttle from Z to F) VAB - naming a ship; I can type in a new name. Debug menu (in flight mode); I can type into the log input box. So it looks like something is blocking the controls in flight mode/VAB/etc. And no, there's no input locks active. KSP1.3.1 works fine. Any ideas?

Now that the situation with Linux gaming will change by the time KSP2 releases(Major handheld console running desktop Linux), will you(Intercept Games/Private Division) be making a Linux port or testing on Proton?

I'm on a new install of Xubuntu and the textures of the components does not seem to be what it should be, various part textures are blurry, such as the image below. Does anyone have any idea why the textures are like this? Texture resolution in the game settings is full res, the rest of the settings are high, I have deleted the settings.cfg multiple times and it made no difference. I have try reinstalling and verifying the game cache, is this just a Linux thing?

Hi, Im wondering if I can install ksp on kali (i need steam) becouse kali is a debian baced and practicly a skin of ubuntu with some different tools. Im trying this tonight so i will post my result here. Thanks, Mine 36

So I'm running KSP 1.9 on Linux, no mods. Start a game, make a rover, and drive Jeb out to the KSC monolith. Have him stand by the long monolith side with the Squad logo, the side that's facing KSC. The monolith will slowly rotate with the planet away from him. You can see the surface texture move with the monolith. If you turn on any time warp, it stops. Is this just me? Edit: if you move him to the short side facing the mountains, it's even more obvious.

Current version: 2.5.1 License - GPLv3+ Description Based upon known launch options of the Kerbal Space Program, I have created a small bash script. It is configured directly by changing the options inside the script. Each line is commented, and if the script is run with any parameter - it will also spill the help. It is not a GUI application on purpose - so it can be chain-launched from existing launchers (.desktop file, Steam, GOG Galaxy etc). How to install: Scroll down to the link, save and paste contents into new file, rename it to "KSP_launcher.sh" and make it executable; Place this file in same directory with KSP binary; Edit it with text editor and adjust options; (Option) Integrate it into your launcher (.desktop file in ~/.local/share/applications, or other launcher) so it runs this script instead of KSP (Option) If you use GOG offline installer, in "start.sh" replace strings "KSP.x86_64" and "KSP.x86", with "KSP_launcher.sh" Run For console help: run the script with some parameter ("./KSP_launcher --help" or similar) How to modify settings: edit the script, change the variable values, save. What script currently allows: - force LC_C to fix disappearing saves/forgetting settings - automatically rotate it with compression or disable KSP logfile completely - turn vsync on/off (both nvidia and mesa/opensource radeon or intel) - force fullscreen or any video resolution - specify opengl / gles level - change R600_DEBUG variable - change Mesa options - start gallium benchmark mode to display fps - protect KSP from shutdown if it asks for too much RAM at once (if you run many mods) - properly waits for KSP to end for cleanup, even if it segfaults - integrated help and options documented inside script - debug mode that shows options it would run some options were deprecated as no longer applicable. Current version: https://pastebin.com/CeVvvdpT previous version (2.5): https://pastebin.com/GVexVATS previous version (2.4): https://pastebin.com/dw1B8fDk previous version (2.2): https://pastebin.com/ctpp53Bd previous version (2.0): https://pastebin.com/2vwj6szQ Warning if you use the "download" button on pastebin.com, instead of copy-pasting raw contents into new text file, then you may encounter the error: "/bin/bash^M: bad interpreter: No such file or directory" To fix it, open this script in text editor and change the line end encodings from Windows to Unix. This done by "pastebin.com", I have no control over this. Heads up of the Linux problems I am aware of, being Linux player myself: - KSP runs hot on GPU Use either nvidia settings panel (for proprietary Nvidia) or radeon profile tool (for AMD, ubuntu PPA) to limit the performance mode of the GPU. In case of Radeon, switch it to manual and low. From my observations, only simulations in atmosphere require a lot of GPU. In VAB/SPH the GPU is perfectly fine in manual low-power mode, consuming 10-20% energy and running cool. Since KSP supports window switching (alt-tab), you can easily adjust performance as you need it. - KSP does not remember settings and always starts in window mode This stopped happening in Linux (for me), but it doesn't seem to be fixed globally. Unity uses comma delimiter set by locale and some locales have "," instead of "." This leads to the problem and solution is to force en_US through LC_ALL=C. This does not prevent using different keyboard layout and does not interfere with game localization. Solution: KSP_unity_forceLC="on", which is default in my script - KSP starts with window of weird size This stopped happening in Linux (for me, since 1.2), but it doesn't seem to be fixed globally. This is because Unity fails to get screen size from window manager. Solution: KSP_ksp_cleanprefs="on" which is default and will remove Unity's "prefs", and you can force the settings for one launch with KSP_unity_forceX, KSP_unity_forceY, KSP_unity_fullscreen variables. - KSP sometimes at loading crashes Xorg session, booting to login Solution: KSP_ksp_protect="on" , which is default in my script - KSP starts with black screen, noticed in Mesa 11 (fixed) Solution: KSP_unity_glcore to "on" or "33" (or higher value, if your GL library supports it) - Bop and Minmus have terrain glitches, noticed in Mesa 12 (fixed) Solution: KSP_unity_glcore to "on" or "41" - RasterPropMonitor shows has pink lines instead of IVA panels (fixed) This is result of having "glcore" enabled, as it breaks the shaders. Here is the bug report. - KSP sometimes crashes I read about this bug being present on Intel opensource drivers. To solve, disable antialiasing in KSP settings. - VAB/SPH floor markers are weird (fixed) (gradient - AMD, covered in flickering noise - Nvidia). This is connected with shader rendering and OpenGL library in the system. On AMD / Mesa 17, the system also freezes at random time and its connected with issue below. On AMD / Catalyst(depricated driver), its reported to be fixed by disabling PPFX edge shaders in settings. On Nvidia (proprietary driver), is reported to happen with driver 378.13 and later. Its possible to workaround this issue by installing Hangar Extender mod. - KSP freezes the system completely (fixed) Freeze happens at random point. The freeze happens earlier, if there are Mods that require a lot of GPU work. After many attempts I have traced this issue to Mesa 17+. Solution: If you have OIBAF or PADOKA Mesa installed, try removing them and downgrading to "hwe" Mesa. This is likely DRI3 issue, but no option I know helped, its somewhere in the Mesa userspace stack. Upgrading kernel does not help. If this interests anyone, I am using x64 Kernel 5.x and NixOS. For driver, I use opensource radeon driver, running with R9 280 (still!). Enjoy!!

Hi everyone, I know that this question has already been asked for Windows users, but I know how to download older version of the game on windows, both with Steam and the launcher of Galaxy of Gaming. The problem is that on Linux there is no Launcher for GoG and on the website I have not managed to download the 1.7.3. (I like to play RP-1) I could do it on Steam, but on steam I do not own the extensions. I tried with Lutris, and the website. No luck so far. I asked this question on the Lutris forum last week, no answer. I just asked this question on the customer support of GoG, and still no answer. I have the feeling that this forum might be my best chance. Thanks.

I've installed KSP in my, now main OS, Manjaro. With the vanilla game i had no problem, but after installing a couple mods, around 20, the frames in the VAB drop to around 3-5 per second. The problem is that in game, with a 120 plus parts the game runs absolutely smooth. Any suggestions?

Hello everybody! I am very excited to update to the new release, but it is running at around 5 frames per second anywhere other than the main menu. The menu is perfectly smooth. I have tried to set the graphics to lower settings, but that didn't improve the situation. My computer is an Ubuntu Laptop that isn't a gaming machine by any means and has pitiful memory, but it runs 1.7.3 fine. I bought the game through Steam if that helps. I did a clean install, but the behavior persists. I already looked through the KSP.log file, but I didn't see anything unusual. I saved a copy of the file if anyone wants to look at it. Thanks for looking!

Hi I'm running Ubuntu 18.04 with the GOG version of KSP, and when I launch the game I immediately get a black screen and the cursor followed by a crash to desktop. This is a fresh install with all the dlc and no mods. Here is a link to my log file, Player.log

I'm currently running Pop! OS Linux distro, and I was wondering as to how I would be able to install KSP. My main problem, is that I have the GOG Galaxy version of the game, I have tried using Lutris to install the game, but each time I get an error saying "Error("Destination path '/home/name/.cache/lutris/installer/kerbal-space-program/unzip' already exists",)" I have obviously checked this each time before installing and its not there. In case its of any help: I have ensured that Lutris has read and write permissions

Since Linux gamers do not get update scripts but have to DL whole client when updating to newer version i suggest that updated version would come with a script, that optionally can be run, that asks are there older version from which to import settings, saves and mods. On the other hand since some updates may break mods, these selections should all be selectable separetly... not forgetting those awesome screenshots!

so i'm only really making a return because i have an ion-powered craft with burn times ~1 hour, but i can't enable physics warp for some reason. everyone says to do alt + . but it doesn't work for me for some reason. maybe because i'm on linux? i really don't know. (sorry if this is in the wrong place, only ~85% sure it should go here but i'm kinda desperate so :/)

I was wondering what distro other forum users have installed if you dual boot with windows that does not count as a dual boot in this quiz also if you use another distro please explain which one

As the title says.... Is v1.6 for Linux actually released? I play on two different computers, one Windows, one Linux. The Window system got the update to 1.6 first, there were some complaints about mk2 Lander but it all worked out in the end. Later that same day I went to play on my Linux system and I *thought* I had update dialog telling me about 1.6, doing upgrade, etc. I played, got the same warning about the lander and some other parts but it worked. Then trying to play again the next day I get incompatible save errors and it won't load. I started investigating this thinking the save had been corrupted only to realize I'm still playing 1.5.1 Now I'm wondering, did I imagine my Linux system updating? Did it revert? Is it even out?

I"m in need of some help installing making history add-on. I"m running Linux mint on a Quad core Asus motherboard I built. the basic program runs great, so i decided to buy the Making history Add-on. I"ve unzipped the files to a folder on my desktop. But the instructions tell me to run a script called dlc-mhe-[lang]. command. I"ve got no clue how to run this in the Command terminal. after i open the terminal I get this:( ray@ray-quadcore:~$ ) can anyone with some linux experience help me out? Thanks for any help Ray Gott

I've installed the game and the Making History expansion through Steam running on Ubuntu 18.04 (Bionic). With the expansion installed, the game no longer runs. Sometimes it crashes before it can load the main menu. Sometimes it crashes or freezes at the main menu. The farthest I've ever made it was to click through to the Making History select-a-mission screen, at which point the game froze. If I uninstall the expansion, the base game still works fine. Is anyone else seeing this behavior? Anyone come up with a workaround?