VerifiedShow Details
Unknown
If you speak Spanish I let you know that if you want to install Spanish Mix from Svenchu you must have Lux Wine and follow the guide of Nexusmods of KH PC Patch Manager, you must put KH PC Patch Manager and a file called DotNetZip.dll in the same folder to work and open the program without problems, just follow the steps in the official guide.
SteamDeck=1 prime-run gamemoderun %command%
the cutscenes' frame timing (at least for Kingdom Hearts II) is a little off or something because the cutscenes feel choppy, even for 30 FPS. Also, When you put the game in fullscreen, the game doesn't run at full speed, so i have to put it in borderless or fullscreen to make it run at full speed
SteamDeck=1 WINEDLLOVERRIDES="dinput8.dll=n,b" gamemoderun %command%
No problems noticed, and thats while playing with mods
Game runs fine.
KIngdom Hearts 1.5 + 2.5 runs fine right out of the box with Proton Experimental. No tinkering/forced compatibility.
Activate Umu Proton Runtime in Advanced options
install dotnet48
Epic version installed throught Heroic. Use latest proton GE and add dotnet48 with winetricks throught Heroic. Activate 'Use UMU as Proton Runtime' in Advanced settings of Heroic. Following these steps the games selector fully work and you have FMV with video and audio.
SteamDeck=1 gamemoderun %command%
PROTON_VERSION="Proton Experimental" flatpak run com.github.Matoking.protontricks 2552430 regedit
This problems only occurs when you try to start game with nvidia gpu on wayland, on xorg works OOTB. I downloaded the proton version recommended by @Nyms and add edit regedit with protontricks and faced same issue of fullscreen but on at least on Gnome i just set game to window mode and switch back to fullscreen and worked fine.
After yesterday's update, the game finally runs without crashing from my RDNA3 gpu. Played for 3 hours without any issues
SteamDeck=1 gamemoderun %command%
Definitely still need SteamDeck=1 for the cutscenes but otherwise works wellv
SteamDeck=1 %command%
This is an update to my previous reports. After updating to Mint 22, the game now launches a new game properly on KH1. I was able to do some initial stuff, then save and reload without any issues. I'm not too far in the game, for now, so there may be some unknown issues I haven't encountered yet.
SteamDeck=1 %command%
Installed the custom Kingdom Hearts launcher mod by SandeMC which works without issues.
The game audio has slight background crackling at times. This is an issue with the game itself and occurs on Windows as well.
Alt+tabbing the game would sometimes result in the game remaining fullscreen but the game screen getting cropped slightly in the corners. Fixed by restarting. Unsure whether this is a Proton issue or a game issue.
This game takes a bit of tinkering to get to work on wayland, but it is well worth it to skip the need to switch between X11 and Wayland.
SteamDeck=1 gamescope --force-windows-fullscreen -- %command%
I couldn't get the fullscreen to work, probably is because I'm using Polonium window tiler
If I wasn't using gamescope my controller wouldn't be detected by the game
This game crashed constantly for me when I am on Wayland but after a lot of trial and error I finally got it to stop crashing.
You basically need to run the experimental native wayland proton. I followed a guide I found installed this proton version: https://github.com/Frogging-Family/wine-tkg-git/actions/runs/10342900947 You need the extract the archive and find the proton_tkg_9.15.r0.g92374493 folder and put that in the steam compatibilitytools.d folder and restart steam. After that I added a file to the games register to make it use native wayland driver. I used protontricks like this: protontricks 2552430 regedit I created a file in my documents folder called wayland.reg and filled it with this:
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Wine\Drivers] "Graphics"="x11,wayland"Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Wine\Drivers] "Graphics"="x11,wayland"
In regedit I pressed file and add file, went to documents and choose wayland.reg. In steam I changed the proton to TKG proton for kingdom hearts, and now the game was running natively on wayland. But when starting the game the screen would open off center and my controller wouldn't be detected. What ended up fixing it was running the game with gamescope, now the controller is recognized and the games screen is working well enough, I can't get the game to fullscreen but I can maximize it and that is enough for me.
Hope this helps someone!
In KHBBS during Ventus's final boss fight, pressing "Retry" after you die can sometimes leave the game in an infintely loading state regardless of the storage medium.
MANGOHUD_CONFIG="read_cfg,fps_limit_method=early,fps_limit=60" %command% -skipintro
Set the in-game "Frame Rate" option to 60, and "Refresh Rate" to On. The game's framerate is erratic due to weird interpolation behavior above 60, and cutscene audio will desync without specifically in-game vsync enabled. MangoHud's fps limiter then fixes the frame pacing, and fixes the cutscenes' severe lag when enabling vsync without it.
Rare flickering on shadows in KH1. Not observed in other games (yet?)
Cutscenes lag and/or desync from audio, without my listed launch options.
Make sure to use MangoHud's options. Gamescope's limiter (quick settings UI) helped frame pacing, but it was not perfectly flat, and FMV cutscenes would still desync.
SteamDeck=1 %command% -skipintro
It is worth noting, as others have aready done, that using Wayland will cause issues. Swapping to X11 and using "SteamDeck=1 %command% -skipintro" launch options have lead to being able to play without issue other than an occassional audio desync during cutscenes.
SteamDeck=1 mangohud gamemoderun %command%
Cutscenes run at a choppier framerate in some instances
i3wm doesn't like the switching between launcher and games so do make it work you either have to run in gamescope or use something like Steam Metadata Editor to add separate launch options for each .exe
Otherwise runs fine, I had issues with cutscenes being choppy occasionally but that may be an issue on my end with g-sync issues
Game crashed on wine assertation
SteamDeck=1 %command%
I'm able to view game selector menu, but once I choose a game, the game crashes with the following error:
Assertation failed! Expression: "!status && "vkAcquireNextImageKHR""
This occured for me on both Fedora and EndeavourOS, but doesn't occur on the Flatpak version of Steam.
Overall game has run near perfectly. Performance is great, and it looks good.
I have had an issue on occasion when starting up, when switching from the game selection menu to the game you picked, it will sometimes lockup with a blackscreen. Infrequent, but has happened a couple times.
After 75 hours of gameplay, everything runs perfectly, didn't crash even once. The only issues were the fmv's, fixed launching in deck mode.
env SteamDeck=1 gamemoderun %command%
It's crazy for a game that just released on steam to run so flawlessly. That's why I never wanted to buy from Epic. I knew the steam version would run perfectly (and this was on day 1!)! The only issue were the FMV cutscenes in the beginning and end of the game, fixed launching in deck mode.
Tinkering with this was a bit of a pain but I solved all my issues in one morning, so I'd say definitely worth it.
gamemoderun mangohud PROTON_NO_FSYNC=0 SteamDeck=1 %command% -reboot=true -useallavailablecores
Couldn't save past opening tutorial while using Wayland as compositer. Switch to X11 to solve.
Game crashes after a couple minutes using Xbox series X controller, no solution found besides using keyboard & mouse.
Save yourself the headache, use keyboard & mouse, run X11 as your compositer until this game works on Wayland.
10w TDP
The game does not currently support 16:10, which adds black bars to the top and bottom of the screen, which then makes the screen a lot smaller. To circumvent this, set the "Scaling mode" in the Performance Tab to "Stretch".
SteamDeck=1 %command% -skipintro
Last week this game worked on Wayland, but now it's just crashing. If you're having recent issues there might be an issue with wine on wayland right now. The solution for me was to use X11, for now. I tired downgrading the linux kernel and nvidia drivers but it was still crashing.
If you're having issue and you're on Wayland try using X11.
gamemoderun mangohud PROTON_NO_FSYNC=1 SteamDeck=1 %command%
Install vcrun2022 and dotnet48 to use KHPCPatchManager mods
Well some of you might have noticed your game cutscenes are slowing more than 30fps, i discovered in some forums that this games doesn't run well with G-sync, but i have AMD and not NVIDIA graphics, then i remembered that the equivaent of G-sync for AMD is Freesync, and also in other Protondb pages there are games using the disable Fsync Flag which is enabled by default using ProtonGE, thats why i enable it and then it fixes the cutscene running slower :>
SteamDeck=1 DXVK_FRAME_RATE=144 %command% -skipintro -useallavailablecores
Without changing your launch options, you won't get the cinematic cutscenes. Other than that, runs fine
This is the EPIC version, the cutsceenes will play with latest Proton-GE (9 and newer), but blackscreen with audio only.
install dotnet48
Install dotnet48 via protontricks or it will loop back to Launcher when selecting a game.
Select Borderless or windowed.
Blackscreen FMV
This is the EPIC version, the cutsceenes will play with latest Proton-GE (9 and newer), but blackscreen with audio only, so at least you will be able to skip the ending and get a clear save file (select use steam runtime in heroic or system libraries in Lutris). I tried everything i could possibly think of since steam version works fine cnanging settings etc., mf-install worsens the situation and the cutsceenes crash the game again, i even tried the fmv from the steam version but with no luck still blackscreen but it will occupy ~20GB less diskspace so its worth it if you can just replace the fmv in the corresponding subfolders in the EPIC folder, but be carefull some subfolders are renamed in the steam version from en to dt.
If you allready played the games and dont care for the cutsceenes you will enjoy it but, if you first time player it's a big pass. Hopefully GloriousEgroll can work something out with the knowledge the steam version might provide, after a view wasted dasy i've given up for now...
Some audio crackling is present in Re:Chain of Memories
More of a neutral recommendation; either runs well or it doesn't. Launch option needed for FMVs to play.
SteamDeck=1 %command%
Some minor menu SFX missing. Some combat SFX dropped during intense action.
Happens on my hardware with some level and menu transitions.
Windowed mode goes fullscreen during some loading screens (usually when transition between game and launcher).
Occassional sudden frame drops during gameplay (not cutscenes; those are a different problem). This is with an iGPU, but it happens erratic enough in scenarios that usually run fine, so I'm considering it unexpected.
Performance drops steeply and FMV audio becomes dsynced when framerate is capped, regardless if vsync is enabled. (This is especially strange given the games' vsync bug and common solutions to it.) Solution: set "Frame Rate" to "Unlimited" or some such in settings.
Across the board, this port has many infamous bugs that did not apply to me, including constant crashes on RDNA3 GPUs from AMD and instability with vsync on. Finding solutions to these bugs can be uintuitive and inconsistent across setups. Mods will fix minor annoyances once they are ported from the EGS version. Be prepared to refund as necessary.
SteamDeck=1 %command%
the launch options fix the cutscene issues some people, including me in an earlier post, have, but I still get crashing that kills my pc and can only be fixed with shutting off my psu.
Played over 65+ hours, Kingdom Hearts 1, Kingdom Hearts: Chain of Memories, 365/2, KH2. Absolutely no issues, game ran flawlessly at all times.
SteamDeck=1 %command%
J'y joue également sur le Steam Deck et, a priori , la configuration graphique est sauvegardée dans le Cloud. Après avoir changé la config coté Deck, je n'arrivais plus à lancer le jeu sur le PC. Le souci semble venir de la définition + le mode d'affichage à utiliser. En remettant tous les paramètres à leurs valeurs par défaut coté Deck, j'ai pu rejouer sur le PC.
En fonction de la configuration d'affichage, la manette pouvait ne pas être reconnue. Souci de focus de fenêtre d'après ce que j'ai pu lire sur les autres commentaires.
Freezes de quelques secondes de temps en temps. Je suis sous NVidia + Wayland, ça peut être une explication.
Le jeu est jouable. Il faut modifier la ligne de commande, utiliser Proton GE et ne pas modifier les options graphiques.
Works perfectly as long as you add the SteamDeck env var, which is needed for the cutscenes to play. Set it to borderless fullscreen.
SteamDeck=1 %command% -reboot=true
Needs to be set to BORDERLESS fullscreen (not normal fullscreen) or it may crash when minimized
A flawless experience as long as you set it up properly like I explain here. The "-reboot=true" argument is just to skip the intro logos. Also, this is on Wayland.
SteamDeck=1 %command%
Can crash when minimized
Needs the SteamDeck env var for the videos to play. Minimizing it can lead to crashes, I suspect it's a stability issue of Nvidia+Wayland but I'm not sure.
All games crash after starting new game
I can install and open the menu, but everygame, KH I/II/III ALL CRASH.
Every time I select a game from the main menu or load a save file for a game it will minimize, resize, and re-fullscreen (borderless or no borderless).
Having tested all the games within this collection and the two others recently released on steam (2.8 and III) it seems that all the games not running on unreal 4 (so prior to 0.2) do not play cutscenes. I will be able to hear audio, and sometimes see subtitles, but there's no image. X backstory doesn't work at all.
This is consistent across all the kingdom hearts titles recently released on steam.
Runs basically perfect, other than some scaling hiccups which are easily fixed in the in-game menu.
TDP 5W GPU 400 MHz
Screen was squished until I switched between windowed and fullscreen twice.
gamescope -W 1920 -H 1080 -w 1920 -h 1080 -r 144 -F nis -b -- env SteamDeck=1 %command%
This is the only game in my library that I need gamescope to run properly. I use i3wm with picom as a basic compositor, and without gamescope the launcher runs fine but KH1 opens to a black screen with audio only (I assume the others do as well, but didn't try them). Running with gamescope solves this. There are a few quirks with gamescope however:
First, in regular fullscreen mode if the game window ever loses focus (i.e. by switching workspaces), then the game will ignore all keyboard and controller inputs upon regaining focus. This can be solved by running the game in borderless fullscreen (both via the in-game settings and with the -b option for gamescope).
Running gamescope in borderless fullscreen will cause the game to launch as a regular non-fullscreen window, but setting it to fullscreen with Super+F after launch works fine. I also found that gamescope will run the game internally at a much lower resolution than my actual monitor's resolution, hence it is necessary to specify all the -W -H -w and -h options for proper scaling. I also added the -r option to set my desired framerate and "-F nis" to use the NVidia scaler.
With all those gamescope flags in place and the SteamDeck=1 env variable set (for FMV playback) the game works perfectly fine.
Unable to continue after starting new game
This is an update from my previous report. KH1, 2, ReCOM and BBS are now able to load into the main menu properly. I can start a new game, but I am presented with a black screen and sounds from cutscenes (the SteamDeck=1 launch argument unfortunately doesn't make any cutscene work in my case). After that, there is only a black screen with no sound and the game is kind of frozen. KH 358/2 days and Re:Coded haven't been tested in my case, but I suppose the result will be the same.
Locked 30 FPS Cutscenes, steady 90 FPS Gameplay. Long battery life > 6 hours.
TDP set to 8
Lots of audio crackling. No fix found so far
