ValveSoftware
Kingdom Come: Deliverance II (1771300)
Compatibility Report
- Name of the game with compatibility issues: Kingdom Come Deliverance 2
- Steam AppID of the game: 1771300
System Information
- GPU: Driver: NVIDIA Corporation NVIDIA GeForce RTX 4080 Laptop GPU/PCIe/SSE2
- Video driver version: 4.6.0 NVIDIA 570.153.02
- Kernel version: .14.0-15-generic
- Link to full system information report as Gist: https://gist.github.com/D-Studio-21th/5b203ccafbd06031f8acb52d09c54aab
- https://gist.github.com/D-Studio-21th/2eb12f64e604bdc7e315d3aa2242f70d
- Proton version: Proton Hotfix/Experimental/9.0.*
I confirm:
- [V] that I haven't found an existing compatibility report for this game.
- [V] that I have checked whether there are updates for my system available.
Symptoms
After 5 minutes of playing, the game starts freezing.
Reproduction
I have a different issue with this game and was told to post it here.
EDIT : Thanks to @JacobSvenningsen I also upgraded Mesa to 25.1.2 and the issue seems to have disappeared !
System Information
OS : Debian Trixie (13) CPU : AMD Ryzen 7 9800X3D GPU : AMD RX 7800 XT Mesa version : 25.0.5 [Issue fixed with 25.1.2] Kernel version : 6.12.27 Proton version : Tested with 9.0.4, Experimental and Hotfix Game version : 1.3.2 (Latest) No mods used Steam Runtime System Information
Description
I purchased the game around the end of April and enjoyed it bug-free for around a week, then I did a system update and since then, every time I load the game, a single PAK file will fail to load entirely. In game this means missing textures and models (showing as white blobs), and occasionally crashes during loading if it hits a critical file.
In the logs, this shows as a plethora of lines with "[ERROR] ReadFile returned 1". But the truly bizarre part of the bug ? Every time the game is launched, the affected PAK file changes, meaning a whole new set of corrupted textures. And of course the previously affected PAK file miraculously works again so it's not a matter of corrupted files.
Affected files (for now)
data\characters.pak data\hlod_prefab.pak data\ipl_characters-part2.pak data\ipl_characters-part3.pak data\ipl_objects-part0.pak data\ipl_objects-part1.pak data\ipl_objects-part3.pak data\ipl_objects-part4.pak
Reproduction
Start a new game or load a save
Things I tried
- System updates
- Validating game files (including deleting all PAK files to force re-download)
- Purging shader cache
Examples
Launch No 1 (Notice the missing texture on the guard)
Game log
Launch No 2 (Notice the missing texture for the road, buildings and vegetation in the center)
Game log
Additional files
Proton log DPKG log of the related update
Managed to resolve it. Went ahead and followed some bad practice and installed the mesa packages from Kisak PPA, bringing Mesa to 25.1.2 Currently it's working using that version of Mesa and using Proton 10.0-1 (beta).
Original post:
I have a different issue which prevents the game from working altogether.
System Information
OS : Debian Sid CPU : AMD Ryzen 9 7900X3D GPU : AMD RX 7800 XT Mesa version : Initially 25.0.5-2. Then upgraded to 25.1.0-1 Kernel version : Initially 6.12.30-1. Then tried upgrading to 6.15.1 Proton version : Tested with 9.0.4, 10.0-1 (beta), Experimental, Hotfix and even Glorious Eggroll 10-4 Game version : 1.3.2 (Latest) System diagnostics
Description
Back in February and March, I played the game extensively with no real issue, but trying to run the game again yesterday, I'm greeted with one of three outcomes:
- The splashscreen shows up and nothing more happens
- A black screen pops up. Alt-tabbing reveals the splashscreen is still present
- Intro logos are being displayed and as soon as the EULA, DLC screen information, or the main menu is reached, it freezes.
When the last outcome occurs, the music is still playing and the cursor can be moved. Pressing one of the buttons, plays a sound which could indicate that the button was actually pressed. It feels driver related, and it might not be Proton specific. Scouring the internet, it seems Windows users are reporting similar issues, which sometimes are reported to be fixed by a reboot, removing the game's shader cache or a driver update. Deleting the game's shader cache can lead to the last outcome (freeze at main menu) to become more likely, but doesn't resolve anything.
Tried upgrading mesa, the kernel, tried different proton version and reinstalling the game to another drive.
Additional files
Log when the main menu is reached vulkaninfo kcd.log kcd_launcher.log
Managed to resolve it. Went ahead and followed some bad practice and installed the mesa packages from Kisak PPA, bringing Mesa to 25.1.2 Currently it's working using that version of Mesa and using Proton 10.0-1 (beta).
Holy crap you just fixed my issue too ! Looks like it is a problem with Mesa 25.0 then.
Kingdom Come: Deliverance II – freeze after Maleshov exit cutscene
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9128. @NoahPladys posted on 2025-10-22T21:59:34:
Compatibility Report
- Name of the game with compatibility issues: Kingdom Come: Deliverance II
- Steam AppID of the game: 1771300
System Information
- GPU: Nvidia RTX 5070 Ti
- Video driver version: 580.95.05 (also tested 580.82.09)
- Kernel version: Linux 6.17.3-arch2-1
- Link to full system information report as Gist: System Info Runtime Report
- Proton version: Proton Experimental, (also Proton Hotfix, Proton 9.0 - 4, Proton-GE 10-21)
I confirm:
- [X] that I haven't found an existing compatibility report for this game.
- [X] that I have checked whether there are updates for my system available.
Symptoms
When exiting the game at Maleshov, it is supposed to play a cutscene, fade to black, and fade into a new cutscene. I get the first cutscene, a fade to black (followed by a ~2 second freeze of any video on my pc, e.g. a youtube video playing on my second monitor), and then just that same black screen for the entirety of the session. At this point there is nothing to do and I have to close the game. Skipping the cutscene before it has finished works and just bring you right back in the game. Seems like it just breaks on the cutscene transition.
Reproduction
Just exit the gate at Maleshov after clearing the guards and signalling Capon to come down. Do not skip the cutscene
Troubleshooting attempted
- Verified game files
- Switched Proton versions (Experimental, Hotfix, 9.0, GE 10-21)
- Cleared shadercache + rebuilt prefix
- Tried both driver versions 580.95 ↔ 580.82.09
- Disabled NVAPI (DXVK_ENABLE_NVAPI=0)
- Enabled PROTON_MEDIA_USE_GST=1
One exception that kind of fixed it (but made the game unplayable), is forcing DX11 with PROTON_USE_DXVK=1 DXVK_ASYNC=1 %command% -dx11. This gave me a black screen, but by blindly clicking and moving to the gate, I managed to start the cutscene and by the audio of the clips I heard that the second clip started playing, so it must be something with DX12
Same here on Arch Linux with Proton 10.0-3. Steam input is disabled. Connected Gulikit ES Pro controller (Xbox controller) via Bluetooth or USB cable does not work in game, seems related to the last patch, according to this thread
A workaround for now is launching the game with:
SteamDeck=1 %command%
My Dualsense controller works OK, both via Bluetooth or USB cable.
Indeed, the controller doesn't work on Linux, and Warhorse will likely not address it, as it's unsupported platform, so all hope in Proton.
