Yakuza 4

From RPCS3 Wiki
Yakuza 4
Developer(s) Ryu Ga Gotoku Studio
Publisher(s) Sega
Series Yakuza
Release date(s) JP March 18, 2010
NA March 15, 2011
EU March 18, 2011
Release type PlayStation exclusive
Genre(s) Action, Adventure
Mode(s) Single-player
GameID(s) BLES01081 (IRD), BLUS30643 (IRD), NPEB02036, NPUB31510
See also... Check Compatibility
Open Issues
Search Google
Wikipedia Page

Yakuza 4 (Japanese: 龍が如く4 伝説を継ぐもの Hepburn: Ryū ga Gotoku 4: Densetsu o Tsugumono, lit. Like a Dragon 4: Successor of the Legend) is the sequel to Yakuza 3, and the first Yakuza game that did not feature the involvement of Daisuke Sato, the current series producer and one of the members involved since the very first game.

The available mini-games are pachinko, fishing, onsen, table tennis, hanafuda and karaoke, including duets with non-player characters (NPCs). In Haruka's Wish, the player must raise Haruka's trust level. Each main character has a side game or goal which must be completed, and many side games are related to trophies.

Akiyama may create friendship (Japanese: 馴染み Hepburn: Najimi) with some NPCs by buying them items, or with some storekeepers by being a regular customer. His other mission, Create a #1 Hostess! (Japanese: No.1キャバ嬢をつくろう! Hepburn: No.1 Kyabajō o Tsukurō!), is to scout girls for the cabaret he owns. A girl is improved by dressing her up and training her. After she becomes number one, the player can choose a final outfit for her and she will appear at the cabaret. A similar challenge in the Japanese version of Yakuza 3 was cut from overseas versions. Saejima's mission, Create a Fighter! (Japanese: 格闘家をつくろう! Hepburn: Kakutōka o Tsukurō!) is to train fighters to win tournaments after 50 rounds or less of training (building up movesets). Different movesets allow different moves to be performed. Tanimura's mission, Resolving Police-Radio Disputes (Japanese: 警察無線トラブル解決バトル Hepburn: Keisatsu Musen Toraburu Kaiketsu Batoru), is to keep the peace on the streets of Kamurocho. Radio reports tell him where to find incidents, and the player must defeat the perpetrator. In Kiryu's mission, Team Encounter Battle (Japanese: チームエンカウントバトル), seven gangs attack him and he must fight to reach each gang leader.

Each character has his own style of fighting and special moves as their body frames are different. Kiryu focuses on the powerful blows of Karate and Boxing, Akiyama prefers swift attacks combining Taekwondo and Wrestling, Saejima favors brawling attacks using Judo and Street fighting, Tanimura uses the defensive maneuvers of Aikido and Kung Fu that he learned from his fellow Police Officers.


Only options that deviate from the default configuration to ensure best performance are listed below. The full list of default options is available here.

CPU configuration

Setting Option Notes
SPU block size Mega No improvement to performance but reduces the number of SPU cache objects

GPU configuration

Setting Option Notes
Renderer Vulkan Recommended to get the best performance.
Resolution scale threshold 512 x 512 Prevents weird borders from showing up when upscaling.

Known Issues

Random crashes

The title suffers from random crashes and currently there are no methods to prevent the crashes.

The random crashes can be fixed by enabling Accurate GETLLAR in the debug menu - No longer possible since PR 6056.

Special Notes

Reducing log spam

Due to the high amount of warnings spammed in the log, this title tends to crash during extended gameplay sessions. So it is recommended to restrict logging of certain errors to allow better performance while ingame. Please note that you cannot submit logs in the GitHub tracker or Discord server with this modification. If you wish to report bugs or seek help for this game, you MUST remove the below change before generating the log for this purpose. If you wish to restrict logging:

  1. Launch RPCS3
  2. Right-click on the game and press Configure
  3. When the Settings Menu opens, hit Save and close the emulator
  4. Navigate to RPCS3\config\custom_configs\config_GAMEID.yml and open the file using a text editor
  5. Scroll to the bottom of the file and replace the last line with the following:
Log: {sys_semaphore: Fatal, sys_fs: Fatal, sys_vm: Fatal, sys_memory: Fatal, RSX: Fatal, sys_lwmutex: Fatal, sys_spu: Fatal, sys_event: Fatal, sys_rsx: Fatal}