


Despite it running, fine on linux, I would not recommend playing/buying it since the game is abandonded, instead play the first, natively
Mostly because of the games garbage performance to begin with
Works well, no tinkering needed so far

MANGOHUD_CONFIG="fps_limit=60" mangohud %command%
lavfilters
With no tinkering the in-game videos stutter and skip frames. I fixed this by installing lavfilters with protontricks. The game as far as i know has no means of limiting the frame rate. This was fixed using mangohud.

Recently started crashing
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
I'm not sure if it is a problem with the game itself or if it is due to a recent update in Fedora 40. But, whatever is going on, I started having crashes shortly after starting play. Mainly crashes at the VAB, but will crash on the launch pad or anywhere else given enough time.
Crashes at "Creating Vessel..." when starting new campaign
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%

The game lunches fine without any arguments on my system, though the videos were not playing in game, so I switched to proton GE and it fixed the issue

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Audio stopped playing after alt-tabbing and remained when going back to the game window
VAB and menu is normal, but when at space center and in flight, the entire view is taken up by heavy, multi-colored artifacts.
Mouse sensitivity was very high, and after alt-tabbing away and back, input was completely gone

KSP2 is still in early access and I have had to explore a few workarounds that shouldn't be needed after full release.
Input lag from keyboard when using larger vessels--can take up to 7 seconds for the game to register a change in keyboard input. Have not found a solution to this problem, although others report using PROTON_NO_XIM=1 as a launch option fixes it for them.
Borderless window mode crashes when I move the mouse to the other monitor and click on other programs outside of KSP 2. I have to treat the game like it's running in fullscreen mode to avoid crashing.
In my system, the launcher opened without any issues. Other users may still want to use the launch options others have listed because it's easier to just bypass the launcher.

When starting a save, it freezes at "Pumping sim once". The game becomes entirely unresponsive and never recovers.
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command% -popupwindow
Occassionally, when it freezes, it causes my entire desktop to freeze, forcing me to switch tty and kill it in that environment. I have never gotten the game to run properly.

the game won't launch without this argument : `bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%`
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command% -popupwindow
borderless doesn't work, it's exactly ther same as fullscreen, to get true borderless on linux you need to use the -popupwindow
cli arg and set the game to windowed
tinkering is REQUIRED if you want to play this game

PROTON_NO_XIM=1 eval $( echo "LC_ALL=C PROTON_LOG=1 %command%" | sed "s/PDLauncher\/LauncherPatcher.exe'.*/KSP2_x64.exe'/" )
Low framerates at higher resolutions and graphics settings.

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
below 5 fps

Crashes and low framerates
When using a resolution smaller than your monitors in fullscreen there are black box artifacts along the bottom of the screen.
5 - 15fps along with a lot of input lag
This game is in a pretty rough state. Constant crashes, poor performance and bad audio. If you're hoping to play this game only on linux you will be sorely dissapointed. I did try the launcher and it worked.

gamemoderun %command%
Input did not register before fix
Had to add the .exe as a non-steam game for it to work at all.

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Mangohud would cause a crash at campaign load after "[System] Loading Research and Development completed..."

mangohud gamemoderun bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Works flawlessly with no graphical glitches/bugs
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- prime-run %command%
Game crashed on startup without launch config to circumvent launcher

Works out of the box.
The publisher mentioned, that Linux integration is on their extended roadmap. However, I think they fixed the linux integrartion with their latest patch "For Science!". Works just fine.
Le jeu plante au lancement d'une campagne.

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
The launcher still fails, but if you run the command to skip the launcher, the game runs fine with a great FPS and no issues.
Installed and started without any tinkering. Played several hours, through to Mun orbit. Pleasantly smooth experience.
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
The game often CTD's when tabbing back into the game, after having tabbed out.

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Launcher stil not work but you should befine with the launch options.

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Launcher does not work. Just use launch options to launch from exe.
Hard to read handheld. Fine when docked.
Runs around 25fps when in flight. Otherwise runs fine for the deck.
Using Cryoutilties with recommended settings.
As I understand it the game runs just as well on linux as it does on windows with a device of equal capabilities

%command% -popupwindow
In-game change the graphics configuration to Windowed mode. Then add the -popupwindow
command line argument to make it a proper borderless window, as suggested on PCGamingWiki. This solves Alt-Tab issues.
Based on version 0.2.0.0 of the game on Epic. Early access so there are some bugs, but that's most likely not caused by playing on Linux.

gamemoderun %command%
If you only have 8GB of VRAM this game will probably have extreme lag on maximum settings, despite running fine on Windows.
To fix this reduce the texture quality to low and use "gamemoderun %command%" in launch options, and restart the game. Afterwards the game is playable.
Restart the game after changing the graphics settings, otherwise you won't see an improvement. This took me too long to discover.

Game crashes when it is not in focus (i.e. alt-tab during borderless)
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
the launcher is borked, launching without it works fine

gamemoderun %command%
Runs just as I expect it would

The game will consume 7GB of VRAM at low texture settings, be sure to have enough available or the game will crash/run very poorly.
If you have a GPU with more than 8GB of VRAM you shouldn't have to worry.

Using the amazing launch commands the others figured out, the game ran fine by bypassing the launcher.
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Due to the "0.2" nature of the game, many minor assets are misaligned such as fins. The physics appeared to be siumulated correctly.
Hopefully 2K and Take-Two Interactive (Take2) don't screw this up, their launcher is already causing havoc. No doubt not helped by firing all the original programmers.

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Avoid launcher with this params and play smooth even with videos using proton 7.0-6

Works just fine out of the box
Game is running great after the for For Science! update wihtout needing any tweaks. Still has some bugs but nothing exclusive to Linux.

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
When launching without skipping the PrivateDivision Launcher, i would get very low performance, arround 8-12 FPS at minimum setttings. But with the launch options i get stable 50-60 fps

With the current patch (For Science) it has finally become playable and enjoyable for Linux users.
eval $( echo "%command%" | sed "s/PDLauncher\/LauncherPatcher.exe'.*/KSP2_x64.exe'/" )
Edited "SteamLibrary/steamapps/compatdata/954850/pfx/drive_c/users/steamuser/AppData/LocalLow/Intercept Games/Kerbal Space Program 2/Global/Settings.json" to manually set a custom resolution.
Sometimes when alt-tabing the FPS drops significantly. It can be fixed by changing the resolution to a random value and then back to the desired value.

Launcher is borked. Game runs by adding the Executable as a non steam game.
After installation the launcher would not load in any version of proton. I got a window but then I got an error message and the launcher was automatically closed.
I therefore did the following to add the game's exectuable as a non-Steam game by:
- clicking on "Add a Game" at the bottom of the library page.
- Choosing Add a non-Steam game and
- then browsing to the game's executable "KSP2_64.exe" .
- Having done this I chose to run the game using GE-Proton8-21.
After these steps were complete KSP2 ran as expected with no discernable difference to windows play. On my system I was getting 57-60fps with V-Sync on using a 60Hz 1080p Monitor.

eval $( echo "%command%" | sed "s/PDLauncher\/LauncherPatcher.exe'.*/KSP2_x64.exe'/" )
Splash down is about 10m above sea level
Tried with PROTON_USE_WINED3D=1 and would launch but performance was terrible, removed and it''s like a completely new experience. Super smooth, not checked FPS but guess easily 60.

bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Game crashes on New-Game introduction video. Skip it with unselecting 'new player experience'.
Starting the game with update 1.5. Did a simple orbit and landing without issues. Now I am waiting for the compaign update in december :-)

Proton compatibility has broken in v0.1.4.0, no matter what you try. Just doesn't work
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command%
Await to the next version and complain
On windows with the same hardware I got 20-30fps but in the same situation on linux I get 1-2fps