
davidthefrikr
Published
Boring Man's Windows build runs like native. The game is fully playable. Controls are okay by default but I'd recommend customizing them.
The game's native Linux build does not run in the Steam Deck's gaming mode. The game needs to be ran via Proton for it to work in gaming mode.
The game works straight out of the box, however the battery life without manually setting limits is not the best.
TDP limit set to 6W, FPS locked to 30
Text is small in various menus as it was made to be displayed on a bigger screen
With the amount of addons I have installed, binding all the keys that I want to use to various action sets and controls is a bit of a chore since there isn't enough buttons on the Deck for absolutely everything a player would want to do. I switched to the x86-64 beta and ran Garry's Mod using the Steam Linux Runtime.
gamescope -W 1920 -H 1080 -r 165 -- %command%
Mouse got locked to one side, it couldn't move past the middle of the game window over to the right side, no matter if the game was windowed or in fullscreen
Game launched using Gamescope to fix issue
I have a dual monitor setup, so this might've caused the mouse to not be captured properly in the game's menus
Game window briefly appears before closing
-nobattleye
The game runs perfectly out of the box on Steam Deck. Audio doesn't desync during gameplay, like how it does on Windows.
TDP limit set to 6w, refresh rate set to 60 hz and fps limited to 60 fps
-vulkan -novid
Full screen via Proton makes the game fail to create a D3D device, full screen via native makes the game locked to 60 hz
Occurs exclusively while playing workshop maps, some maps will consistently crash the game on Linux native, it's mitigated through running the game on Proton
Proton version fails to find public matches due to VAC, hosting a game is fine
Game runs fine but battery life is a bit lacking and audio crackles without custom launch options
PULSE_LATENCY_MSEC=60 %command%
9 tdp limit @ 40 fps
Text too small
Audio crackling, fixed with a launch option
On native, audio kept reverting to surround 5.1
On native, fullscreen locked refresh rate to 60 hz and windowed/borderless windowed caused the game to be centered between both of my monitors rather than being centered on one of them
The game runs and works out of the box with good performance without any tinkering necessary.
TDP limit set to 6W, FPS limited to 30 FPS, resolution changed to 1024x576, shadow and post processing quality set to mid, vsync off, texture quality set to high
Despite being Deck verified, the game drops FPS constantly with the recommended settings OOTB.
FPS dips to 20 when playing through a new area, despite downloading a shader precache from Steam. When playing through the area again, the framerate improves but frametimes are inconsistent.
Game works out of the box with the only caveat of weird windowing issues (which may stem from the game itself and not due to Proton)
Resizing the window is bugged; maximizing the window sometimes has the game not resize with it so you get a huge white border around the actual gameplay window, while half of the time it reverts back to its original resolution. Resizing the window by dragging 1 side at a time partially works, but same border issue applies.
The game is fully playable on Steam Deck and it runs as expected. The controls take some getting used to, but it works.
TDP limit + FPS limiter
game saves don't sync with windows, otherwise game works
The lack of cross-platform cloud saves makes it very annoying if you want to switch from one platform to another.
Yakuza 4 runs almost perfectly on Steam Deck with Proton Experimental, with the caveat of excessive power draw (up to ~23W on battery).
Yakuza 4 runs almost perfectly on Proton Experimental with the caveat of battery life suffering, with around 23W of usage.
Battery life suffers with only around 2 and a half hours of gameplay before it drains to 0.
Yakuza 5 mostly works with the only issue being related to cutscenes. A player can watch these on YouTube to get around the issue.
Some cutscenes play the wrong audio, like the beginning cutscene with Daigo getting into a taxi. If the audio is too short, then the cutscene ends abruptly.