tuzok
Members-
Posts
11 -
Joined
-
Last visited
Reputation
1 NeutralRecent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
KSP 2 and Proton
tuzok replied to Geonovast's topic in KSP2 Technical Support (PC, unmodded installs)
In a Linux users performance survey becomes obvious that the limiting factor should be amount of Video RAM. And that AMD users with 8 GB are faring better. -
KSP 2 and Proton
tuzok replied to Geonovast's topic in KSP2 Technical Support (PC, unmodded installs)
Sorry, 8 GB RAM is well below 12 GB minimum requirements. It is supposed to run very poorly without sufficient RAM... -
By the way, could you please run this command on your GPU on either host and guest while running KSP2 at kerbin? while true; do cat /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/current_link_speed; sleep 3; done cat /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/max_link_speed; You likely need to modify PCIe slot to your GPU, this is mine: lspci -s 0000:01:00.0 01:00.0 VGA compatible controller: NVIDIA Corporation GA106 [GeForce RTX 3060] (rev a1)
-
Seriously? Have you mentioned running KSP2 under Virtual Machine at the very last lines of your post dismissing it should not have any effect? Understand that KSP2 Devs might not even understand what Qemu/KVM means. Sure, PCI-passthrough GPU may have huge performance potential, but KSP2 is really not polished, well optimized game, that could benefit your graphics computing power without other dependecies, yet. We found that nVidia 8GB GPUs were doing really high amount of PCIe transfers when running under Steam Proton. Perhaps its similar with Windows and AMD GPUs too, thus likely Qemu PCI-passthrough is the bottleneck. What was you guest VM allocation? 16 GB RAM? Please do change your title from "fps 2.5" to something meaningful like "Qemu GPU passhtrough - only 2.5 fps". No need to mock this Early Access game with your unusual scenario.
-
KSP 2 and Proton
tuzok replied to Geonovast's topic in KSP2 Technical Support (PC, unmodded installs)
The FPS drop is likely related to amount of Video RAM. A guy with 3060 12 GB is running just fine, but I with 3060 8 GB am running only ~9 fps on kerbin. Are clouds causing the behaviour? It was reported the problem does not manifest if you load a save in space until you get back to kerbin... As a matter of fact, we found that the difference with my computer running ~9 fps and the other guy's computer running >20fps may be actually PCIe 3.0 vs PCIe 4.0 capable CPU! Can anyone confirm something similar from AMD graphics, please? -
KSP 2 and Proton
tuzok replied to Geonovast's topic in KSP2 Technical Support (PC, unmodded installs)
I got something! When my FPS dramatically drops, the KSP2 keeps doing excessive PCIE transfers! Does that 7% memory numbers look as bad as I imagine? $nvidia-smi dmon -s tu # gpu rxpci txpci sm mem enc dec # Idx MB/s MB/s % % % % 0 11075 8424 100 6 0 0 0 10799 8688 100 7 0 0 0 10230 8493 100 6 0 0 0 9352 6909 100 7 0 0 -
KSP 2 and Proton
tuzok replied to Geonovast's topic in KSP2 Technical Support (PC, unmodded installs)
Okay, I have to admit I have been wrong. Either DXVK_HUD=full and nvidia-smi dmon shows that bottleneck is indeed graphics: nvidia-smi dmon shows SM utilization to 100% (main menu was giving about 30% load): 0 51 55 - 19 8 0 0 7500 1560 0 41 54 - 15 7 0 0 7500 1807 0 35 53 - 0 0 0 0 7500 1807 0 32 54 - 100 28 0 0 7500 1777 0 51 54 - 3 2 0 0 7500 1935 0 42 53 - 41 1 0 0 7500 1935 0 62 57 - 100 11 0 0 7500 1935 0 66 57 - 100 9 0 0 7500 1935 0 71 57 - 100 7 0 0 7500 1935 0 72 57 - 100 9 0 0 7500 1935 0 71 57 - 100 9 0 0 7500 1935 # gpu pwr gtemp mtemp sm mem enc dec mclk pclk # Idx W C C % % % % MHz MHz 0 70 57 - 100 7 0 0 7500 1935 0 70 58 - 100 7 0 0 7500 1935 -
KSP 2 and Proton
tuzok replied to Geonovast's topic in KSP2 Technical Support (PC, unmodded installs)
+-----------------------------------------------------------------------------+ | NVIDIA-SMI 525.89.02 Driver Version: 525.89.02 CUDA Version: 12.0 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| | 0 NVIDIA GeForce ... Off | 00000000:01:00.0 On | N/A | | 30% 55C P0 60W / 170W | 7610MiB / 8192MiB | 100% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=============================================================================| | 0 N/A N/A 2258 G /usr/bin/gnome-shell 159MiB | | 0 N/A N/A 3683 G /usr/bin/Xwayland 13MiB | | 0 N/A N/A 3728 G ...gl=desktop --shared-files 58MiB | | 0 N/A N/A 4529 G /usr/lib64/firefox/firefox 167MiB | | 0 N/A N/A 10066 G ...e/Steam/ubuntu12_32/steam 9MiB | | 0 N/A N/A 10984 C+G ...ce Program 2\KSP2_x64.exe 7130MiB | +-----------------------------------------------------------------------------+ Guess what! 9 fps or not, its not being dragged down by graphics! Geforce utilization is merely 30%!!! Why! Its not fuel system either, I got that with only Kerbal swimming at sea! -
KSP 2 and Proton
tuzok replied to Geonovast's topic in KSP2 Technical Support (PC, unmodded installs)
I got KSP2 running including its Launcher out-of-box with Proton - Experimental under Fedora 37. While I had 220 fps on main menu, I got only 6-9 fps on launchpad. But I somehow was able to snap something inside KSP2 after switching off/on v-sync or changing Fullscreen to Borderless window. Then fps got raised to 20 fps at launch pad and kept performing well till next crash. Which happened during re-entry after attempt to eject from pod around 10000 m above ground after my only chute was torn by aero-forces. Snapping into reasonable performance probably occurred after turning on v-sync. Unfortunately, I have not been able to replicate that ever since. PROTON_USER_WINED3D="1" Does not make any difference for me. I am running KSP2 just with command: "PROTON_LOG=1 %command%" Fedora 37 (wayland), Proton experimental, Ryzen 5600G, 16 GB RAM, Geforce 3060 GTX -
Hi, I have installed KSP2 with Proton Experimental on my Fedora 37 (using Wayland) and KSP2 launcher run without any problems, no fiddling with Launch options were needed. Launcher downloaded some update and then I run the game - everything was working including the introductory video and I landed at the space center. But then I hit alt-tab and KSP2 crashed when returning back. Since then I haven't been able to load the created game nor create another new game. After reboot, I have finally succeeded with creating new game without new player experience... :-/ Fedora 37 (wayland), Proton experimental, Ryzen 5600G, 16 GB RAM, Geforce 3060 GTX (I got working Space Engineers through Proton earlier, thus most library dependecies should be have been resolved before trying KSP2).