Runs like native.
The game runs without problems.
There is a mission several hours into the game where you need to follow shinji to the top of a building. There are loading zones between the floors of this building, the final loading zone that lead to the roof caused my game to get stuck on an infinite loading screen (stuck at 64FPS for some reason?).
I verified my files, changed proton versions, all the usual trouble shooting steps but every time I tried it would lock up, to get around this issue I had to copy my saves to a GOG copy of the game through the heroic launcher, progress, save, copy back. very strange issue.
I experinced a semi-game breaking bug that others have reported at different points in the story but this is not an issue with proton and I belive this game to be working as "intended" on a windows machine
Zero issues on the continuation of Kiryu's journey
I was able to complete with no issues encountered in my playthrough. Smooth 60FPS at 1440p for the most part, only dropping on the most dense of areas. Also, played using a xbox core controller on spinning rust with no hiccups.
solid 120pfs, controller vibration is really strange compared to yakuza 0 but i guess its just a game thing
Vibration is a little wonky.
Runs without any issues
PROTON_SET_GAME_DRIVE=1 %command%
It did not detect my monitor settings correctly, so the UI was extremly squished and impossible to read. I had to manually edit graphics.ini which in Pop OS can be found in:
~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata/834530/pfx/drive_c/users/steamuser/AppData/Roaming/Sega/YakuzaKiwami
There I set the ResolutionX and ResolutionY to my monitor resolution, as well as WindowX and WindowY. I also set RenderScale="1.000".
gamemoderun %command%
Camera might act funny when in small spaces, such as SEGA Arcade.
1280x800 has patterned bars on top and bottom in cutscenes but full screen in-game, 1280x720 has black bars throughout. Up to you but I preferred the latter.
Disabled touch screen because touching it even slightly would cause the camera to swing around wildly at incredibly high speeds.
6TDP 40hz 800p /w all high settings
Occasional momentary audio crackling.
What with being on the same engine and only made one year after Yakuza 0, this game runs practically identically with a native 800p, all high settings, 6TDP and 40hz getting you an approximate playtime of 2~3h or so. The only differing thing I spotted was occasional audio crackling which I think was related to waking the game up from sleep, but that tended to go away after playing for half a minute or less.
The game has problems with folder path size. Move it to a short path or use symlinks/SteamTinkerLaunch to launch it from the game's bottle
Problem with folder path size. Appears to fail with Flatpak steam. Either move it to a library with a shorter path, or make a symlink in the game's bottle and use SteamTinkerLaunch to launch it from there.
Black screen pops up after a few seconds, immediately closes
Tried other proton version, including GE. Tried reinstalling, disabling pre caching, nothing makes a difference
RADV_TEX_ANISO=8 %command%
The launch option cleans up some of the blurry textures that the game's own anisotropic filtering doesn't deal with properly, most noticeably on characters' clothes when viewed up close (during cutscenes or such)
This game obviously shares its' engine with 0, and supposedly 5 was built on the same engine. Apparently the engine used is an upgraded version of the engine used for the PS3 releases of 3, 4, Dead Souls and Kenzan. Thankfully none of the issues apparent with running 5 on Linux/Steam Deck crop up here, so I guess some difference exists between the engine used for 5, 0 and Kiwami.
Anyway tl;dr this works 100% and deserves a verified check for sure.
once i went afk with the game running, computer logged out and turned off the monitors, when i logged back in, the game crashed
On rare occasions, after suspending and later resuming the steam deck, game would resume with crackling sounds.
Played both in handheld mode and plugged into the TV, handheld works perfectly in steam deck's natvie resolution, while TV had to be upscaled from steam deck's resolution with FSR. Both worked in perfect 60fps.
Used to play perfectly, but then I was suddenly unable to launch the game
I've played about 1/3 of the game with no issues whatsoever, but since last week the game will no longer launch at all. I get a black screen, and then a crash. Proton log shows 0 infoirmation that would imply an issue like this according to the ProtonDB Discord server members I talked with. Steam didn't update, the game didn't update, Proton version is the same. Baffling issue that I can't seem to replicate anywhere else (my Steam Deck can still run the game just fine).
If you are able to replicate this or have more skill in reading logs please let me know in the ProtonDB Discord server
Applying PS button icon mods
Since I use PS controller, I use PS Button icon mod to match it
The game crashes on startup
I've tried to switch to older proton versions, even GE-Proton but nothing made a difference
Worked greate and played entire game with no issues
On X11 I found if I ever exited, it would not be able to return to the screen
Didn't try Wayland
works pretty well
Works fine with default proton
Dualsense has to be plugged in after game launch to display Playstation prompts
Runs perfect out of the box!
Game is awesome, give it a try!
External drive the game is installed to is mounted in a subdirectory of the user's home folder
This may apply to Steam Deck users who have installed Yakuza Kiwami to external storage. This provides a workaround to the fact that the game typically crashes when installed to external storage as I have previously reported (https://www.protondb.com/app/834530#4jielHs9hM). The workaround is thus: the mounted drive containing the steam folder should be mounted within the home folder. This workaround was not first discovered by me, but I have verified that it works, and I've forgotten where I originally came across this workaround.
DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 2070" %command%
On systems that use NVIDIA Optimus, you may need to specify with DXVK what GPU you want to use with DXVK_FILTER_DEVICE_NAME="some device" %command% rather than adding __NV_PRIME_RENDER_OFFLOAD=1 to the launch options. It matches on substrings so you don't have to enter the full name of the GPU. Not sure if other games do this
