VerifiedShow Details
Unknown
Without special settings i see fps drop to ~20 and unstable.
in match fps falled to ~20
Videos are finally working under Proton Experimental, removing the blocking of story mode progress.
As I wrote in my first review, story mode is very important for a game when it does not have that many players online. Now that Proton Experimental has changed the way videos are played, I can set the record straight.
Unsupported video or sound
Unsupported video or sound
If using Proton GE 9.x, video shows up but sound is gone. If using default Proton (Experimental), some videos cannot be played.
%command% -v
Controller was detected but keyboard was not
game would run with keyboard input on steam proton 4.11-13 but would crash almost immediately after getting into the menu. 9-11GE plays fine aslong as you run it with %command% -v to disable cutscenes but keyboard input will not work.
Não abriu no Proton estável (9.0-2), foi necessário utilizar o Proton GE (9-10) para conseguir abrir, provavelmente por causa do vídeo de introdução. No mais, tudo funcionando sem problemas.
LD_PRELOAD="/usr/\$LIB/libgamemodeauto.so.0$LD_PRELOAD:/usr/\$LIB/libgamemode.so.0" PROTON_LOG=1 %command%
Proton cannot play the intro because it doesn't support the .wmv video file extension, while all the intro is .wmv, you need to convert the .wmv video intro file and several arcade ending cutscene file to .mp4 and then renaming file extension type to .wmv to make it work, this way the game thinks the files is .wmv and load it while in reality it's .mp4 file that we just converted it from .wmv, all of the .wmv file can be located in the game file just click the cog icon button and then Manage > Browse Local Files, it's in the "video" folder . Here's the script i used inside the video folder:
for fmv in *.wmv; do echo "Transcoding $fmv"; ffmpeg -v quiet -stats -i "$fmv" "${fmv:0:-4}.mp4"; rm -rf "$fmv"; mv -- "${fmv:0:-4}.mp4" "$fmv"; done
otherwise if you just want to play the game without cutscene use the
-v
arguments in the launch options to skip all video cutscenes.
This game is dead brothers, play with your friends :). Don't even think about going online, this game doesn't even have proper Rollback netcode that modern fighting game have.
The game is perfectly playable with Proton Experimental and probably with the latest stable Proton version. You just have to make that video cutscene convert thing that i just said OR just use the
-v
argument if you don't care about arcade ending cutscenes.
Was working fine before but when trying to use multiple controllers it breaks everything, resulting in having to hard reboot the Steam Deck.
Steam OS stopped working resulting in to having to hard reboot.
Would either only recognize one controller or none at all
Short, green flash, when a video should have played. This blocks from story mode content.
gamemoderun %command% -v
Videos would not play under any circumstances.
Definitely tinkering needed. The -v parameter will skip the initial video and thus allow you to start the game. However, this forces you to miss story mode content.
Either videos could never work in my distro, or else don't work with 7.0-6. Cannot get videos to play, not with older Proton versions, not with MF install script.
Works perfectly using Proton 7.0-5 Flatpak community build. Didn't need to use the -v argument after %command%.
Just tested with 4.11-13, it works.
%command% -v
%command% -v need for all ptoton versions(proton v7 or before) otherwise you get black screen and/or other glitches. (except proton experimental).
Missing background and missing characters in-game.
I used Proton Experimental flatpak community build 7.0-20221115
prime-run %command%
video cutscenes not showing up properly.
i wish there was a way to bring video cutscene to work and play.
Black background and enemies are not appearing in screen.
Using Proton 7.0-3 flatpak community build runs smooth but the gameplay is completely borked so don't use it. I opted to use Proton 4.11 official Steam build and it works perfectly. Even online.
Severe graphical issues make the game unplayable on Proton/Linux.
Only things that appear on-screen where the playable character and the UI. BAckground stages and opponents were all pitch black. Sometimes only the oponents show up and my character turned black. Tried arcade & practice modes, both had the same issue.
-r
Just add the arguments -r on steam and play smooth
Runs perfectly on Experimental. Playing on default Proton leads to unrendered characters and stages, but everything is perfect on Experimental. Looks beautiful on the smaller Steam Deck screen.
%command% -v
Without the -v, the game would sit on a blank screen at startup.
Please note that I removed that argument when writing this report to double-check, and it actually plays the video now, so either it's been possibly fixed or it's only needed for the initial run.
-r
Yeah, compared to the other KOF games on Steam, this one requires a little bit more tinkering...but not a whole lot to get it working compared to something like anything that's still listed as Borked on here. If you have a high refresh rate monitor, you're gonna want to add "-r" (without quotes) to get it to not play at turbo speed.
If you want to not have any graphical glitches and the increased chance of a crash, then Proton 4.11-4.13 is the Proton variant you want to specify for compatibility. It might not play the intro/cutscene videos, but you can look all those up on YT afterwards if you want, and that's assuming you're playing the singleplayer for the story, something that I only do once with any FG myself, personally.
All of this should apply to the Steam Deck, btw. I haven't personally used the device yet (ordered it after I had to go to work on the day the reservations opened, hence I gotta wait until July-September to get mine), but for Steam Deck users who are curious, these are the settings you want to use to get this game working with no problem if the Steam Deck lets you try a game out like it does on standard desktops and laptops.
Fighters and backgrounds are sometimes missing
Crashes at startup intro if not using launch option "%command% -v"
Parameter on launch command
Low performance and missing graphics in story mode
Two screens and KDE effects slows the game
The opening video not plays without the -v parameter, and crash the game.
Without bypassing the intro video the game crash, this is a major issue.
The game expects a Xbox 360 gamepad
The game crashes after the title screen unless you bypass the intro video using the %command% -v launch option.
Runs as well as it does on Windows.
The online is laggy and bad, but it's equally bad on Windows.
Before installing I came to see the comments, so to prepare, I took advantage and took the variables of those who have played and added before starting to play:
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_USE_WINED3D=1 gamemoderun %command% -r
The game ran like it was native
Run great out of the box with Proton 5.10 and with 5.13 with a small tweak
To run the game with Proton 5.13 you must set the parameter -v on the Launch Options to skip the intro video (it crashes when trying to load it with WMP). If you are using other tools, such as gamemode, the command would look like "gamemoderun %command% -v".
If you use schedtool to schedule the game process for FIFO, make sure to set the core affinity to 0x1 otherwise it hangs when loading the fights (e.g: "kofxiii.exe -F -p 15 -n 4 -a 0x1")
The game runs flawlessly out of the box !
You MUST run the game with Proton 5.0.10, because newer versions (Proton 5.13) will not get past the splash screens.
Game ran fine on Proton 5.0-10. No Issues! No additional settings.
Using Proton 5.13-1 the game repeatedly crashed before it got to the title screen. Use a lower version until the issue is patched.
Game does't play cutscenes video. I tried many method with protontricks, winetricks to install wmp9, media fundation, even weird things like K-lite codec pack, but no, the game doesn't play videos.
No video cutscenes
Good running experience
I had to force the use of Proton 4.11-13 instead of my default 5.0-4 but it ran perfectly after that.
