Last Pirates: Die Together FPS and Performance Fixes

October update: what to check now

With VSync enabled, the FPS-limit option is hidden after the October 1 fix. Smaller maximum PC texture sizes reduce memory use, but the official notes do not promise a particular FPS gain. Test remaining issues on your own hardware and current settings.

September changes that affect this guide

2026-09-10: Head Crab became a jellyfish; two unnamed threats, new equipment, 20 achievements and a rebuilt location/chapter order reshaped the run.

2026-09-09: The developer announced Verified status with working mapped controls and readable text.

2026-09-03: A small startup-loading improvement, despite the dramatic announcement title.

2026-08-28: Right-click fish healing became faster, while loading-screen reconnect, Deck input and GPU occlusion fixes shipped.

What official patches already changed

The Aug 19–21 sequence records session and general optimization, enemy-spawn prefab warmup, fewer loot-heavy frame drops, coin optimization, and a laptop auto-quality fix. These are current factual changes, not promises that every PC now holds one target frame rate.

The best baseline is a fully updated build with known settings, not a launch-day comparison.

1 · Establish a clean baseline

Finish the current Steam update, restart the game, and note the map, scene, crew size, display mode, resolution, quality preset, and whether the drop appears immediately or after a long session.

This turns “low FPS” into a repeatable case and separates one heavy scene from a whole-session regression.

2 · Compare preset and auto quality

The Aug 21 notes specifically mention fixing automatic quality selection on laptops. Test the current automatic choice once, then compare one lower preset at the same resolution.

Change one variable at a time. If several settings move together, the result cannot identify the expensive layer.

3 · Use normal system checks

Close unnecessary high-load background work, confirm the game is using the intended GPU on a multi-GPU laptop, and install a normal stable driver from the hardware vendor if yours is clearly outdated.

Do not download random DLLs, registry packs, unofficial executables, or unsupported launch-flag bundles. They create risk and make the comparison harder.

4 · Verify installed files

If the current client behaves abnormally after updating, use Steam’s installed-files verification and retest the same scene. This is reversible and stays within the supported delivery path.

A successful verification does not prove hardware health, but it removes one common client-integrity variable.

5 · Diagnose the scene

Compare an ordinary room with enemy-spawn moments, coin-heavy areas, large loot piles, and long-session play. Official fixes name those workloads, so scene labels make a report useful.

If only loot-heavy hauling drops, link the case to route and object count context without claiming an exact universal threshold.

6 · Report a reproducible case

Include CPU, GPU, RAM, operating system, resolution, preset, display mode, build/update date, map, crew size, scene, approximate before/after FPS, and whether file verification changed anything.

A community post such as “67fps on my 5070ti” signals demand, but a useful diagnosis needs the surrounding variables.

Direct answers

Frequently asked questions