Player Take

What This Patch Actually Means for Players

Logged about six hours on Dying Light 2 since Patch 7.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 5 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.

Netcode feels more honest after Patch 7.3. I'm getting fewer 'how did that register?' moments, which is the boring but important win. The flashy balance changes get the clicks; the rollback fixes are why you'll actually stay.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
HDR brightness clipping on the finale cutscene fixedNo more blown-out highlights in that one cutscene.
The frontline bruiser companion AI no longer gets stuck on terrainThey actually keep up during traversal now. Small but huge QoL.
Texture streaming pop-in on the open field reducedThe city skyline stops flickering when you pan the camera fast.
Bug Fixes

Bugs Squashed in Patch 7.3

🐛Fixed an achievement not unlocking when the condition was met offline.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Fixed subtitles overlapping during {scene} cutscenes.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed duplicated the quest item appearing after a server reconnect.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Corrected a UI freeze when scrolling the social menu on controllers.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed a bug where the dropped loot tooltips showed the wrong stat values.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed a memory spike that could cause a disconnect after long sessions.
Player impact: Quality-of-life win the community has wanted for weeks.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 7.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 open field or fast-traveling
  1. Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~700MB 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.
💥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
Voice chat volume resets between matches.KnownRe-check your voice settings each session for now.
HDR displays may clip whites in the the open field menu.Being worked onLower HDR peak luminance to 1000 nits in the system menu.
Controller rumble stays on after disconnecting a pad.KnownReconnect and disconnect the controller again to reset it.
FAQ

Frequently Asked Questions About Patch 7.3

The exact questions players search after this patch drops:

AYes. Patch 7.3 is backward-compatible with saves from the previous version. Back up your save folder before booting up, just in case — the patch rewrites a few the dodge roll fields on first load.
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.
ANo. Patch 7.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.
AStart by verifying game files and updating your GPU driver — the Patch 7.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.
Bottom Line

Final Summary

Net positive for Dying Light 2 players. A few rough edges remain (see Known Issues), but the core experience is more stable post-Patch 7.3. I'll keep this archived page updated if any hotfixes follow.

More Dying Light 2 Patches

Other Dying Light 2 Patch Notes

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Dying Light 2 Patch 7.3 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Dying Light 2'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.