Yakuza 3

Yakuza 3
Developer(s)	Ryu Ga Gotoku Studio
Publisher(s)	Sega
Series	Yakuza
Release date(s)	JP February 26, 2009 NA March 9, 2010 AU March 11, 2010 EU March 12, 2010
Release type	PlayStation exclusive
Genre(s)	Action, Adventure
Mode(s)	Single-player
GameID(s)	BLUS30494 (IRD), BLES00834 (IRD), BLJM60132 (IRD)
Quick links	Check Compatibility Open Issues Search Google Wikipedia Page

Yakuza 3 (Japanese: 龍が如く3 Hepburn: Ryū ga Gotoku 3, lit. Like a Dragon 3) is the third main entry in the Yakuza series, continues the adventures of Kazuma Kiryu from Yakuza and Yakuza 2. The game takes place in Kamurocho, from the first two games, and in a brand new location called Ryukyu.

Yakuza 3 introduces new gameplay elements such as:

• Seamless Battle: Seamless Battle is a streaming data-based loading-free system that allows the game to directly connect the adventure mode and the battle mode (called "Kenka") without the usual black loading screen.
• Chase Battle: Chase Battle is a new battle mode which replaces the regular brawling (Kenka) with a running sequence set within a certain area. Both the chaser and person being chased have a stamina gauge that decreases if the character runs, is hit with a thrown object, or collides with a passer-by. When the stamina gauge is empty the exhausted character stops the chase. Throughout the course of the game, a minor character, Mack Shinozuka, will train Kazuma, improving his running performance.
• Revelation (Japanese: 天啓 Hepburn: tenkei): Ten revelations will allow Kazuma Kiryu to learn new Heat Actions in Adventure mode; in a manner that is similar to the system introduced in the previous game: Ryū ga Gotoku: Kenzan!. This time Kazuma uses the built-in camera on his cell phone to record new moves and techniques. These are acquired through hints and incidents spotted in First Person View. Learned Heat Actions are posted on Kazuma's blog, called "Kamuroblo", which uses the same template as producer Toshihiro Nagoshi's blog.
• First Person View: When pressing R3 on the DualShock 3 during Adventure Mode, the standard third person view switches to a person mode, a first for the series. This perspective allows for better observation of the streets and people in them, but looking at certain people in the eyes while using First Person View will provoke them, causing them to attack. First Person View is disabled in certain indoor places and at certain angles.

Configuration

Options that deviate from RPCS3's default settings and provide the best experience with this title are listed below.

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}