Tomb Raider Patch 5.4 Notes | Bug Fixes & Changes

Player Take

What This Patch Actually Means for Players

Patch 5.4 for Tomb Raider just went live and the community is split. I tested the changes across three sessions — here's the honest breakdown. The part most players miss: the headline numbers don't tell you how the patch actually feels. I ran 6 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.

Performance-wise the patch is a net positive on my rig. Frame pacing is more stable, though the new assets in the latest area pushed my VRAM usage up. Budget-card players, heads up.

Key Changes

Balance & Feature Changes — With Player Impact

Change	What It Means for You
Quest the side quest progression blocker fixed	If you were soft-locked, reload an earlier save and re-trigger.
Texture streaming pop-in on the city district reduced	The city skyline stops flickering when you pan the camera fast.
Auto-save frequency increased in the dungeon	Less replaying after a crash. Still, manual save before bosses.
The vanguard hero companion AI no longer gets stuck on terrain	They actually keep up during traversal now. Small but huge QoL.

Bug Fixes

Bugs Squashed in Patch 5.4

🐛Resolved an issue where the crafting bench would silently fail under high ping.

Player impact: Removes a recurring frustration for endgame players.

🐛Fixed a bug where the quest item tooltips showed the wrong stat values.

Player impact: Closes a loophole that was skewing leaderboards.

🐛Corrected a camera glitch triggered when entering the lobby on a mount.

Player impact: Stops a soft-lock that affected a small but real slice of players.

🐛Corrected a UI freeze when scrolling the social menu on controllers.

Player impact: Quality-of-life win the community has wanted for weeks.

🐛Fixed duplicated the equipped relic appearing after a server reconnect.

Player impact: Stops a soft-lock that affected a small but real slice of players.

Crash & Error Fixes

How to Fix Crashes & Errors After Patch 5.4

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

Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~400MB there.
Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
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.

💥Game closes to desktop right after the splash screen on Patch 5.4

Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
Update your GPU driver to the latest AMD build — the May/June branches break on this patch.
Delete the cache folder at Documents/TombRaider/cache, then relaunch.
If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).

Quick workaround: Running in Windowed mode bypasses the crash for most users until the next hotfix.

💥Infinite loading screen after the patch

Sign out of the launcher and back in to refresh your session token.
On console, clear the persistent cache (hold power for 10s, cold boot, then relaunch).
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.

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 Issue	Status	Workaround
Cross-save may delay inventory sync by up to 25 minutes.	Investigating	Wait a few minutes before assuming items are lost.
Voice chat volume resets between matches.	Known	Re-check your voice settings each session for now.
HDR displays may clip whites in the the open field menu.	Being worked on	Lower HDR peak luminance to 1000 nits in the system menu.

FAQ

Frequently Asked Questions About Patch 5.4

The exact questions players search after this patch drops:

QWhen is the next patch after Patch 5.4?−

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.

QHow do I fix the crash after the Patch 5.4 update?+

AStart by verifying game files and updating your GPU driver — the Patch 5.4 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.

QWhy is my FPS lower after Patch 5.4?+

AThe patch added denser the menu assets. Cap your framerate, lower shadow quality one notch, and close background overlays — that recovers the lost frames for most rigs.

QIs my save file compatible with Patch 5.4?+

AYes. Patch 5.4 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 stamina system fields on first load.

Bottom Line

Final Summary

If you held off updating because of the early crash reports, Patch 5.4 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.

⚠️ Important Disclaimer

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