Unknown
I tried to do all the stuff from guides on steam forum and nothing worked for me
Couldn't manage to launch it. Maybe it's possible but this game was never stable even on windows so I have no clue if it is possible.
Followed PCGamingWiki guide to set 60 FPS
Crashes a lot. Not Proton problem. Fix: https://steamcommunity.com/app/261110/discussions/0/522728813811121054
Works perfect after modifying KidEngine.ini
The game works pretty bad out of the box, but some tweaks makes the game perfect. Windows also has the same problems.
Stop the crash: Used the PC Gaming Wiki's method 3 edit to the kidengine.ini The same wiki shows how to use different resolutions (like the steam deck native one) and 60 FPS, so I did that and it was perfect. (with 60FPS you will also need to change the quick time event timers which the wiki also explain). I beat the entire game like this (1280x800 at 60FPS) and the game only crashed one time. Turns out the "Mondo Girls 3" mission needs to be played at 30FPS, so before you select this mission, use the 30FPS cap that the steamOS has and you are good.
Keep in mind that if you change the location of the game (SSD to micro SD for example) the modifications you did in the files will be lost.
Rare crashes
Game crashes randomly.
I was trying to resume from my cloud save, but the game always crashes during the cutscene that plays at the beginning of Episode 6. Tried playing other missions, but they would also crash at random points. This was already a pretty horrendous PC port (crashes only happened on Linux/Proton, not on Windows), so my recommendation is to play the Xbox 360 version on Xbox One/Series if you can.
It's a good game, but I personally do not like the button mashing parts. If you ike hack and slash games this one is definitely one for you.
Used pc gaming wiki's method 3 edit to the kidengine.ini it worked like a charm and have not a had a single crash so far.
Since the game is running at 30 fps natively I limited everything I could to 30 fps which boosted my battery life
The game will crash at one point or another due to the nature of it being not supported on the steamdeck yet. With the changes to the kidengine you should be golden.
PROTON_USE_DV9K=1 %command%
tweaked game files per user Xeloses' instructions (pcgamingwiki crash fix method 3), QTE timing fix and 60fps cap
PROTON_USE_D9VK=1 %command%
Edit "KidEngine.ini" as described here: pcgamingwiki.com (method 3)
Game crashes after 1 or 2 missions without an INI-file tweak.
~
The best config I've found for myself is D9VK + Proton Experimental, the game never crashes with this setup.
A quick tweak lets this run like a dream, even on weaker hardware. The port is still mediocre, though.
Modified ini file (see https://www.pcgamingwiki.com/wiki/Killer_Is_Dead#Issues_fixed [Method 3])
Tested with Xbox One controller.
Played through a couple missions. Game ran perfectly.
Not Proton specific: Had to apply the audio config edit to get the game to run past the main menu (https://www.pcgamingwiki.com/wiki/Killer_Is_Dead#Issues_fixed)
Not required but also adjusted the max resolution and frame rate cap
As game crahes in a cinematic, I had to apply the fix on KidEngine.ini as described here: https://www.pcgamingwiki.com/wiki/Killer_Is_Dead#Issues_fixed
Given the game and other reports, you probably need a machine that's a step above the system requirements.
Had to use Method 3 from this section on PCGamingWiki to prevent crashes on the first mission: https://www.pcgamingwiki.com/wiki/Killer_Is_Dead#Issues_fixed Not sure if this would have been necessary on Windows. This introduced some crackling in the audio.
Also, you may need to use Method 1 or 2 from the same section to prevent crashes on a mission later in the game (both should produce the same result). I didn't play enough to encounter this issue, but I applied Method 2 just in case. The fix may is often needed on Windows as well.
See my notes above. Fixes were necessary to prevent crashing.
Frame dips were large enough to hamper the gameplay experience, even on 800x600 with Low settings. I did run this on a laptop, but its specs meet the minimum requirements and Youtube has evidence of this game running smoother on weaker hardware. Perhaps Proton introduced some overhead?
Vsync cannot be disabled, regardless of menu confirmations or .ini file alterations. Not sure if this problem also exists on Windows.
Xbox One controller used without issue. Check PC Gaming Wiki for common issues and tweaks.
Runs fine most of the time.
For me it always crashes during the second mission.
Sadly, I couldn't test it well, because it always crashes during the second mission, but I think it's my problem as it happens with older Proton versions too.
Playable but has a minor launch issue
Game always launches minimized/in the background, have to Alt+tab to bring up the game.
Game run perfectly but performance is not great.
FPS fluctuate between low 30 to lock 60. VSYNC off.
The games renders perfectly with d9vk now, but the framehate and frame times are terrible. The games works now but the performance still suffers.
60 fps config file works as well wasn't able to test controller I don't have it on me
Started just fine without any DVXK or D9VK. Had sound crackling issue. Sound issue was easily fixed with "pulseaudio -k". Not sure if it's a common issue or just with my system. Disabling Esync looks to give you an FPS boost but doesn't seem required.
I can confirm that missing textures are fixed with d9vk (https://github.com/Joshua-Ashton/d9vk). Now it runs perfectly!
the game started to work with the latest 4.2-4 proton. Controls and sound are perfect but graphics have some texture and rendering issues. Tested with d9vk gives a much more pleasant experience.
With Proton 4.2-3 the game starts out of the box for the first time for me, but Wine's rendering has too many graphical glitches. I installed manually D9VK and it worked, the rendering looked much better, with this the game seems to be playable.
Unknown(< 1 hour with Proton)with 4.2.3 the game works out of the box.
Unknown(< 1 hour with Proton)Doesn't want to start, no error message, just a crash
Unless I'm doing the tricks below wrong as described by previous users, the game did not start for me using winetricks nor protontricks to force the installation of .NET 4.0 twice, only leaving me a bunch of fatal errors being spit out by WINE when attempting to launch, making the game unplayable before it even has a chance to start.
UnknownTried the dotnet40 winetricks trick to no avail. Tried other stuff like installing vcrun2012 and directx9 but they didn't work. That's weird because I have been able to run every other windows game under proton, and I run it under wine (via playonlinux with steamwine).
Unknown
Crashes at launch. Using Proton 3.16-4
Cannot get it to load, no black screen or anything, the process starts and then stops. Tried the dotnet stuff mentioned in one of the Gold reports to no avail.
Unknown(> 10 hours with Proton)After following the posts with the winetricks dotnet40 the game still didn't launch. However I did come across this post for installing all of wine's dependencies https://www.gloriouseggroll.tv/how-to-get-out-of-wine-dependency-hell/ which after that seems to have done the trick. Lutris also appears to have an install script that when accompanied with the full dependencies install seems to have done the trick. Game is flawless after that.
Unknown(> 10 hours with Proton)Unknown(2+ hours with Proton)Game runs great with some stuttering during cutscenes and while the game complies shaders for in -d3d11 setting (The same smooths out as I play it). As other posts have stated I had to run WINEPREFIX="/Your Steam Location/steamapps/compatdata/261110/pfx" winetricks dotnet40 twice as well as tweak one of the config files to prevent crashes during cutscenes. Fix for the cutscenes is posted in the steam forums here https://steamcommunity.com/app/261110/discussions/0/522728813811121054/
Unknown(2+ hours with Proton)Unknown(an hour with Proton)Somebody already said this, but you have to run WINEPREFIX="/Your Steam Location/steamapps/compatdata/261110/pfx" winetricks dotnet40 twice (run it and install everything and then run it again) But after that the FPS is pretty good and it runs just fine.
Unknown(an hour with Proton)
won't start even with the winetricks dotnet trick
Unknown(< 15 minutes with Proton)Seems to work fine after forcing installation of dotnet40 through winetricks TWICE.
Unknown(< 15 minutes with Proton)Doesn't want to start, no error message, just a crash
Works perfectly if the following command is used on the terminal TWICE (yes, use it once on the terminal, wait for it to end, and then use it again): WINEPREFIX="/Your Steam Location/steamapps/compatdata/261110/pfx" winetricks dotnet40
