How to improve FPS in Like a Dragon: Pirate Yakuza in Hawaii (PC)
Like a Dragon: Pirate Yakuza in Hawaii is RGG Studio's (SEGA) action spin-off starring Kazuma Kiryu, who abandons the turn-based combat of the latest mainline entries to return to a real-time combat system in the style of the early Yakuza games, now with a pirate theme: boarding actions, naval combat with your own ship, and exploration of a fictional archipelago inspired by Hawaii. Built on the Dragon Engine, the same engine that powers Like a Dragon: Infinite Wealth and Gaiden, it inherits its usual technical profile: solid overall optimization, moderate graphical demand compared to other open-world AAA titles, and a workload split between the GPU (lighting, water, naval combat reflections) and the CPU (NPC density on the urban streets of Honolulu and the simulation of street life the saga is known for).
This is what you'd gain with a NVIDIA RTX 3050
Want the RTX 3050 at the best price?
Check the current price on Amazon.
Calculations based on our FPS model combined with the % gain of each setting (measured in public benchmarks).
1. Quick wins (no visual loss)
Start here. Each one adds a little, but together they give +37% free FPS.
Shadow Quality
The Dragon Engine's dynamic shadows are among the settings that cost the most GPU on Honolulu's dense streets, with multiple NPCs, vehicles, and streetlights generating real-time shadows.
Water/Reflection Quality
Water and reflection quality directly affects naval combat, one of this spin-off's new pillars, where the engine calculates sea reflections and splashes around the ship in real time.
NPC/Crowd Density
As in the rest of the Like a Dragon saga, pedestrian and traffic density in Honolulu's urban areas is one of the factors that adds the most load to both the CPU and GPU at once.
Global Illumination/Lighting Quality
The Dragon Engine's dynamic lighting constantly recalculates the archipelago's nighttime neon reflections and daytime tropical light, a cost that's more noticeable on mid-range GPUs.
Motion Blur
Motion blur adds a small post-processing cost with no relevant benefit in a fast action-combat game where reading hits and dodges clearly matters.
2. Medium impact settings
Here's where most of the FPS is. Minor visual impact, major performance impact.
Texture Quality
Character, outfit, and tropical environment textures cost mostly VRAM rather than raw compute power, so High is usually enough on most modern GPUs.
Ambient Occlusion
Reinforces visual contact between characters, street furniture, and ship structures, but at its maximum level the cost doesn't pay off in a noticeable way during combat in motion.
Draw Distance/LOD
Draw distance across the archipelago and Honolulu's streets, with buildings and vegetation loading at greater distance, has a notable cost inherited from the saga's compact open-world design.
Anti-Aliasing (TAA)
Temporal antialiasing on the Dragon Engine cleans up edges nicely in scenes with lots of urban and marine detail, but at its highest level adds a noticeable sampling cost at 1440p/4K.
3. Upscaling (DLSS / FSR / XeSS)
The biggest gain in the game. Compatible with almost any modern GPU.
AMD FSR
+18% FPSThe Dragon Engine has added FSR support in the saga's more recent entries (like Infinite Wealth), and it's reasonable to expect similar support in this spin-off; it works on any GPU regardless of manufacturer.
4. Tips by GPU
NVIDIA
- •If the game includes FSR, enable it in Quality mode at 1440p/4K to gain extra margin in naval combat, one of the scenes with the highest GPU load.
- •Keep Game Ready drivers updated; SEGA and RGG Studio usually publish PC performance patches after launch for Dragon Engine titles.
- •It's not a game that requires dedicated ray tracing or NVIDIA proprietary technologies; a mid-range GPU is more than enough for stable 1080p/1440p.
AMD
- •Enable Radeon Anti-Lag to reduce input lag in the real-time action combat's exchanges of blows, more demanding on reflexes than the turn-based combat of other entries.
- •FSR in Quality mode is a solid option if you notice occasional drops in Honolulu's busiest areas or in naval combat with lots of water effects on screen.
- •Check that Smart Access Memory (Resizable BAR) is enabled in the BIOS, since Dragon Engine games tend to benefit measurably from this technology.
Sistema
- •Install the game on an SSD; the Dragon Engine depends on read speed for streaming Honolulu's urban streets and reduces hitches entering and leaving zones.
- •Close third-party overlays (Discord, capture software) if you notice occasional micro-stutters during street fights with many NPCs around.
- •Expect the occasional brief shader-compilation hitch in the first few hours of play or after major updates, common in proprietary engines like the Dragon Engine.
5. Known game issues
CPU spikes in Honolulu's busy urban areas
As in the rest of the Like a Dragon saga, streets with heavy pedestrian traffic, shops, and simulated side activities all at once can generate occasional framerate drops tied to the CPU more than the GPU, especially on older processors.
Stutter in transitions into naval combat
Some players report a brief hitch when moving from exploration on foot or by ship into a naval combat or boarding sequence, likely tied to loading assets specific to those scenes.
Shader compilation hitches after updates
As with other Dragon Engine titles, it's common to notice occasional hitches in the first sessions after a major patch while the engine finishes preparing new shaders; it usually stabilizes after several play sessions.
6. Frequently asked questions
Do I need a powerful GPU to play Like a Dragon: Pirate Yakuza in Hawaii?▾
Does the game have DLSS, FSR, or XeSS?▾
What setting gives the most FPS with the least visual loss?▾
Why do I notice hitches in naval combat if the rest of the game runs smoothly?▾
Want to know exactly how many FPS YOUR PC will get?
Enter your GPU and CPU in our calculator and measure the real impact of each setting.
Calculate FPS for Like a Dragon: Pirate Yakuza in Hawaii →Calculations based on consensus of technical sources and our own FPS model. More about our methodology →