Kerbal Space Program 2 (954850)

[Xinayder]

Compatibility Report

• Name of the game with compatibility issues: Kerbal Space Program 2
• Steam AppID of the game: 954850

System Information

• GPU: GTX 970
• Driver/LLVM version: nvidia 525.89.02-1
• Kernel version: 6.1.12-zen1-1-zen
• Link to full system information report as Gist: https://gist.github.com/Xinayder/f7b3da5cf3cb0c676694d6c7850962ff
• Proton version: Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Massive performance issues even when running the game with the lowest graphics settings. Tutorial/cutscene videos only update their frames once the video is paused, probably due to low FPS.

Reproduction

Launch the game, start a new campaign.

steam-954850.log
KSP2_x64_d3d11.log
KSP2_x64_dxgi.log

[kisak-valve]

Hello @Xinayder, it should be noted that your video card is significantly below the game's listed minimum specs with 4GB of vram in your video card. It's very likely that the game is using system ram with the render hot path and that's bad for performance.

[roman-ra]

I can confirm that the game runs very poorly even on an RTX 3070 (mobile) which is well above the minimum specs.

Tried the following Proton versions:

• Proton Experimental
• GE-Proton7-49

[Makoto29]

I have a RX 6600 | 8GB | PCIe 3.0 | 720p paired with a 5800X3D and can tell exact the same story. However, I would really love to see someone with more VRAM investigating this.

[sfjuocekr]

I run a 5800X3D, 64Gb RAM and 3080 FE (10Gb).

edit: actually, the game starts when it does not exhaust VRAM and it freezes when it does.

[kolAflash]

I also got low FPS.

• https://steamcommunity.com/app/954850/discussions/0/3772364949847852485/
• https://www.protondb.com/app/954850#i23qzwILpR

---> EVERYONE with low fps: Can you give your OS version?
(and if applicable custom library and kernel versions)

 

But I got just around 7 fps at a small rocket launch with low graphics settings. Changing the graphics settings doesn't influence the fps at all (also 7 fps with high settings).
radeon-profile shows 100 % GPU and 100 % GPU RAM (8 GB) usage. Minimum requirement is 6 GB.

System:
OS: Debian GNU/Linux 11 (bullseye, standard Debian 11 Kernel 5.10)
GPU: Radeon RX 590 (8GB memory, amdgpu driver)
CPU: Ryzen 7 5800X (32 GB memory)
Steam+Proton: Standard settings
(Proton >= Experimental 2023-02-24 seems to be needed for the launcher - Proton-7.0-6 isn't working for the launcher)

Because of DXVK >= 2.0 in Proton >= 7.0 I'm using vulkan-1.3.238.
(compiled myself, because DXVK-2.0 requires vulkan>=1.3 and Debian-11 has vulkan-1.2)

 

Alternative:
Disable DXVK by setting the option PROTON_USE_WINED3D=1 %command%. Unfortunately this gives you some graphic bugs on the planet surface (terrain outside Space Center not rendered). But this way I got easily > 25 fps and the rocket looks fine!
With WINED3D the GPU memory is between 70% and 90% usage (8 GB).

PROTON_USE_WINED3D=1 screenshot with glitches

 

P.S.
See also: https://www.reddit.com/r/KerbalSpaceProgram/comments/10sq0qv/proton_support_for_ksp2_linux/

[ruabmbua]

I think I will take a look with the radeon gpu profiler. Need to check out this tool anyway ;-)

[ruabmbua]

Ok so tried it out on a amd 5900x + 5700xt, and I get about 15fps with a mid-sized starter rocket when launching from the pad and flying near KSC.

I then tried with different graphics settings, but no matter how low / high they are set, its always about 15fps. I think this is actually a good sign, there is probably a perf bug somewhere, that takes away most of the performance.

[Blisto91]

So there seems to be a few things going on.

1. The game seems to use an ungodly amount of vram. In the range of 9GB just in the overview scene.
2. This is a Unity game which can act a bit weird on high core CPU's so i can get upwards of twice the performance in the overview scene by limiting my 32 threads to 4 with WINE_CPU_TOPOLOGY=4:0,1,2,3

[ruabmbua]

Unfortunately I could not record GPU traces, the game crashes the driver when enabled. I can confirm that it fills up all of my VRAM.

[kolAflash]

So there seems to be a few things going on.
[...]
2. This is a Unity game which can act a bit weird on high core CPU's so i can get upwards of twice the performance in the overview scene by limiting my 32 threads to 4 with WINE_CPU_TOPOLOGY=4:0,1,2,3

Interesting!
I used to do something similar when running native Linux KSP1. It also improved the performance of the game and the rest of the system.
taskset --cpu-list 0,2,4 COMMAND

[OctoRocket]

I have a 1660 Ti (mobile) and am stuck at ~5 fps in the overview and the VAB. I am also experiencing a black screen upon pressing alt+tab.

[Drago245]

6800XT user here. a small plane resulted in ~20-25 fps, while a decent spaceplane hovered at around 10-15fps for the entire flight. All the while, using 14 gigs of VRAM.

[amokfa]

Does this help? https://www.reddit.com/r/KerbalSpaceProgram/comments/10sq0qv/comment/j9u22io/?utm_source=share&utm_medium=web2x&context=3

[Xinayder]

Tried PROTON_USE_WINED3D=1, the FPS increased to about 7 FPS at the overview (KSC scene).

[kolAflash]

Does this help? https://www.reddit.com/r/KerbalSpaceProgram/comments/10sq0qv/comment/j9u22io/?utm_source=share&utm_medium=web2x&context=3

The PROTON_USE_WINED3D=1 %command% option?
I already reported graphical glitches when using that. (the planets land surface outside the rocket launch area seems to be transparent, wine bugreport)

@amokfa
@Xinayder
---> Does WINED3D work without graphical glitches for you?

PROTON_USE_WINED3D=1 screenshot with glitches

[SigmaRichards]

I did some testing on framerates between my to boots, Windows 11 and Kubuntu 2204 partitions.
I'm running 3700X, 32GB, and 5700XT

The game was running on low preset - I didn't change anything else. I used the games built-in FPS counter. For the launch test, I used the stock "Jumping Flea" which is very small, but it meant I could recreate the same test. FPS was taken just prior to burnout on engine.

Windows 11:
320FPS Main Menu, 52 KSC and 50 during launch

Proton Experimental

• no launch options: 270 Menu, 5 KSC, 4 Launch
• PROTON_USE_WINED3D=1 : 50 Menu, 30 KSC, 27 Launch
• WINE_CPU_TOPOLOGY=4:0,1,2,3 : 285, 4 KSC, 4 Launch
• WINE_CPU_TOPOLOGY=4:0,1,2,3 PROTON_USE_WINED3D=1 : 80 Menu, 34 KSC, 35 Launch

I also tried on GE7-49 and go exactly the same results. Funnily enough, yesterday I couldn't even launch the game on GE but I can now...

I might also be able to test on a 4090 during the week but I probably can't get a windows baseline.

Edit: Forgot to mention I get the same graphical glitches as kolAflash when using WINED3D

[OctoRocket]

Unlike you, I did not have any graphical glitches with wined3d.

[kolAflash]

@OctoRocket and @SigmaRichards
Please add your reports regarding WINED3D to the wine bugreport.
https://bugs.winehq.org/show_bug.cgi?id=54578
IMPORTANT: Please mention your GPU VRAM and your operating system version (including custom kernel or libraries)!

 

P.S.
@SigmaRichards

How much VRAM does your GPU have?
And can you please add hiw much VRAM was used, especially on Windows. Thanks!

On Windows you can see the VRAM usage in the TaskManager or via your graphics driver.

On Linux you can use DXVK_HUD=memory %command% as start parameter in Steam. Or you can probably use some tool of your NVidia driver. (for Radeon there's radeon-profile)

[s-daveb]

For me it only works well (Above 1fps) with PROTON_USE_WINED3D=1 and I had graphical glitches with that option enabled. DXVK does not work very well at all, even with aur/mesa-git-23.1 and setting RADV_PERFTEST=gpl in the environment to enable the new graphics pipeline.

I might try some of the other RADV_PERFTEST options and report back if I get an improvement. (see here)

System Information:

OS: endeavourOS 22.12 ( kernel 6.1.12-arch-1)
GPU: Radeon RX 6600 (8GB VRAM, amdgpu driver)
CPU: Ryzen 5 5600G 3.9Ghz
RAM: 16 GB memory

Proton versions:

• Proton 7.0.6 ❌
• Proton Experimental ✅
• Proton-GE-49 ✅

Update

• Several RADV_PERFTEST options did not help, such as video_decode,cswave32,rtwave64,gpl, etc

[Blisto91]

I don't think the wined3d version included in current proton is very up to date

[s-daveb]

@Blisto91 adding wine to the game command-line, and leaving the proton compatibility options enabled, with WINE_D3D_CONFIG="renderer=vulkan" in the environment seems to get me 13FPS-20FPS in KSC at 720p with no glitching. I'm using multilib/wine-8.2 on arch.

Update

I tried it again in a clean, non-proton WINEPREFIX with the official wine-sanctioned D3D vulkan backend... it launches and everything is dark, and high contrast... but the game crashes on creating a new campaign.

When I disable the vulkan backend, I get the same glitches you see in Proton, with its old D3D.
Seems like standard GL-D3D is we'll get for the time being, with glitches:

[kolAflash]

I don't think the wined3d version included in current proton is very up to date

@Blisto91
Also tested with wine-staging-8.2 outside of Steam/Proton. And it's the same behaviour with WINED3D and with explicitly installed DXVK as well.
See here for details:
https://bugs.winehq.org/show_bug.cgi?id=54578

Actually I think Steam/Proton is just shipping wine >= 8.0 in experimental and that's also the WINED3D version they are shipping.

 

 

@s-daveb
I did some testings with PROTON_USE_WINED3D=1 WINE_D3D_CONFIG='renderer=vulkan' too. Sadly the fps where worse than with DXVK, but there where no glitches as with the WINE_D3D_CONFIG='renderer=gl' default (picture was fine).
https://bugs.winehq.org/show_bug.cgi?id=54578#c1

[RagnarSTS]

To be fair with the wined3d render issues with rocks and trees - this is the exact same behavior demonstrated in space engineers. All the scatter things just really like to float. I think the funny part is that they float - then cast shadows. If they were where they were supposed to be there would be no full shadow.

[SigmaRichards]

I did a test on a different system that has a 4090 with 24GB VRAM on proton experimental.

The game would allocate ~9.9GB on VRAM without any launch options. 85 FPS on launch
With WineD3D it dropped to about 7.2GB with 44 FPS.

I also tested restricting the amount of VRAM it could allocate
Restricted to 8.4GB it would get about 60FPS, if I restricted to any less it would crash.

I don't know why my 8GB card runs the game based on this? I'll have to see how much that is allocating...

[JonathanBrouwer]

I have a 7900XTX. The game uses about 12 GB VRAM out of the 24 GB that the card has, running using DXVK.

Running at ~40 fps at 1440p high settings, but I'm expecting this to be partially caused by my CPU bottlenecking. Mangohud reports a GPU utilization of about ~60% and a CPU utilization of ~50%.

[sfjuocekr]

I have a 7900XTX. The game uses about 12 GB VRAM out of the 24 GB that the card has, running using DXVK.

Running at ~40 fps at 1440p high settings, but I'm expecting this to be partially caused by my CPU bottlenecking. Mangohud reports a GPU utilization of about ~60% and a CPU utilization of ~50%.

Your expectations are wrong if you look at your numbers there is no bottleneck.

The game itself is the bottleneck, it runs potato on Windows as well.

[Xinayder]

I've just upgraded my GPU to a RX 6700 XT and I can say that the performance has been better than it was with a GTX 970.

With the new GPU, I get around 50-60 FPS at KSC (with no launch settings), with PROTON_USE_WINED3D=1 I get between 40-50 FPS. On Windows with my previous GPU I was getting 15 FPS compared to 5.

[JonathanBrouwer]

Replying to #6565 (comment)

I was thinking this because most people reported 100% GPU usage and my CPU (6700k) is quite mediocre in comparison with my gpu

[sfjuocekr]

Replying to #6565 (comment)

I was thinking this because most people reported 100% GPU usage and my CPU (6700k) is quite mediocre in comparison with my gpu

There are many reasons why your GPU would spin to 100%, but all these reasons have one thing in common and that is that you are not CPU bound in any of those cases.

[cemno]

I have the same Problem on my 1070ti. Constant 5fps as if not rendering but something else is the limit. My brother can run it "fine" ~15-20fps on windows with his 970, so my 1070ti should be capable. RAM is 32Gb and CPU is an AMD R5 3600. I suspected a to high vram usage aswell, but i don't know how to confirm.

[ruabmbua]

For me weirdly enough FPS seem to improve over time. Let it run in KSC for 2hours in windowed mode and FPS go to playable.

[ruabmbua]

Update: since the latest patch its playable for me on the ground at KSC.
In close orbit over Kerbin however, the lag starts again.

[Ruedii]

I'm still getting launcher failures.

Game is completely playable when launched manually from the executable using the option to launch non-steam games through steam.

Framerate is still relatively low, and it is GPU-Bound as my CPU is exceptional but my GPU is on the lower end. (I was upgrading the whole system, and a GPU is easier to upgrade than a CPU so I chose feature-set improvement over my previous GPU with only slight performance improvement.)

Here are my logs and system info:
https://gist.github.com/Ruedii/cbdc38090e94940b3314618f456e247a

[kisak-valve]

Hello @Ruedii, these look like some lines of interest from your Proton log:

fixme:ncrypt:NCryptOpenStorageProvider (00000000033293A0, L"Microsoft Software Key Storage Provider", 0): stub
fixme:ncrypt:NCryptOpenKey (0x332e7e0, 00000000033293A8, L"T2GP Launcher local key", 0, 0x40): stub
fixme:ncrypt:NCryptCreatePersistedKey Persistent keys are not supported
warn:seh:dispatch_exception backtrace: --- Exception 0xc0000094.
trace:seh:dispatch_exception code=c0000094 flags=0 addr=00000001403BE905 ip=1403be905
warn:seh:dispatch_exception EXCEPTION_INT_DIVIDE_BY_ZERO exception (code=c0000094) raised