Player Take

What This Patch Actually Means for Players

Logged about six hours on The Last of Us Part II since Patch 2.3 hit the servers. The patch notes read one way; the actual feel is another. Here's the gap. What the notes won't tell you: the headline numbers don't tell you how the patch actually feels. I ran 4 hours across 4 sessions on PC and a couple of these changes ripple further than the notes suggest.

The bugfix lands in a weird spot for The Last of Us Part II. A few fixes that players have begged for since the last update finally shipped, but two of them reintroduce old friction in a new jacket. Worth reading the Known Issues below before you grind anything time-sensitive.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
The ranged carry companion AI no longer gets stuck on terrainThey actually keep up during traversal now. Small but huge QoL.
Texture streaming pop-in on the dungeon reducedThe city skyline stops flickering when you pan the camera fast.
Auto-save frequency increased in the open fieldLess replaying after a crash. Still, manual save before bosses.
The stamina system exploit patchedSpeedrunners lose a skip; the intended route is the only one now.
Quest the side quest progression blocker fixedIf you were soft-locked, reload an earlier save and re-trigger.
Bug Fixes

Bugs Squashed in Patch 2.3

🐛Fixed subtitles overlapping during {scene} cutscenes.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Corrected a camera glitch triggered when entering the lobby on a mount.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Corrected wrong localized text in OCE client for the battle pass.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Fixed a crash when opening the inventory immediately after a loading screen.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Fixed the tournament leaderboard not updating after a completed match.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Resolved a bug where party members loaded into different instances.
Player impact: Removes a recurring frustration for endgame players.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 2.3

Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:

💥Crash on entering the dungeon or fast-traveling
  1. Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~500MB there.
  2. Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
  3. Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
Quick workaround: Unequip the new {item} before entering — a bad model reference is the likely culprit.
💥Blue screen / driver timeout (amdkmdag / nvlddmkm) mid-match
  1. Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 2.3.
  2. Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
  3. Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.
Quick workaround: Underclocking the GPU memory by ~100MHz stops the timeout for affected cards.
💥Infinite loading screen after the patch
  1. Sign out of the launcher and back in to refresh your session token.
  2. On console, clear the persistent cache (hold power for 10s, cold boot, then relaunch).
  3. Check the game's server status page — the login queue is failing silently.
Quick workaround: Switching to a wired connection and avoiding VPNs clears the hang for most players.
Advertisement
Known Issues

Known Issues Still Being Worked On

These problems are acknowledged but not yet fixed. Here's the status and a temp workaround for each:

Known IssueStatusWorkaround
Some players still see the old the recon class/{weapon} stats until a full client restart.AcknowledgedRestart the client after the patch downloads.
High refresh rate monitors may cap at 60fps in borderless mode.Pending fixUse exclusive fullscreen until the next hotfix.
Friends list intermittently shows offline users as online.InvestigatingReloading the social tab usually clears it.
HDR displays may clip whites in the the city district menu.Being worked onLower HDR peak luminance to 1000 nits in the system menu.
FAQ

Frequently Asked Questions About Patch 2.3

The exact questions players search after this patch drops:

AStart by verifying game files and updating your GPU driver — the Patch 2.3 build raised VRAM use, so dropping textures from Ultra to High fixes most splash and fast-travel crashes. The full step-by-step is in the Crash & Error Fixes section above.
ABased on the cadence this year, expect the next update in roughly 3–5 weeks. Archived patch notes stay live on this page permanently so you can always look back.
AA few. Check the Key Changes table above — anything tagged 'nerf' or 'rebalanced' shifts the meta. Nothing got gutted, but two popular setups lost some uptime.
AThe patch added denser the hub assets. Cap your framerate, lower shadow quality one notch, and close background overlays — that recovers the lost frames for most rigs.
ANo. Patch 2.3 ships as a delta patch. Console players may see a larger download if they skipped the last two patches, since those get bundled in.
Bottom Line

Final Summary

If you held off updating because of the early crash reports, Patch 2.3 is now safe to grab on most rigs. The fixes above cover the worst offenders. See you in the next patch notes — this page stays permanent.

👉 This page is permanently archived. Read the latest The Last of Us Part II patch notes →

More The Last of Us Part II Patches

Other The Last of Us Part II Patch Notes

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of The Last of Us Part II Patch 2.3 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by The Last of Us Part II's developer or publisher. For the authoritative, official patch notes, visit the game's official channels. All trademarks belong to their respective owners. Crash fixes and workarounds may vary by hardware, platform, and game version.