Lies of P Patch 3.0 Notes | Bug Fixes & Changes

Player Take

What This Patch Actually Means for Players

Patch 3.0 for Lies of P just went live and the community is split. I tested the changes across three sessions — here's the honest breakdown. Reading between the lines: the headline numbers don't tell you how the patch actually feels. I ran 5 hours across 4 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
Texture streaming pop-in on the open field reduced	The city skyline stops flickering when you pan the camera fast.
HDR brightness clipping on the intro sequence fixed	No more blown-out highlights in that one cutscene.
The frontline bruiser companion AI no longer gets stuck on terrain	They actually keep up during traversal now. Small but huge QoL.
The parry window exploit patched	Speedrunners lose a skip; the intended route is the only one now.

Bug Fixes

Bugs Squashed in Patch 3.0

🐛Fixed an achievement not unlocking when the condition was met offline.

Player impact: Removes a recurring frustration for endgame players.

🐛Resolved an issue where keybindings reset after every restart.

Player impact: Removes a recurring frustration for endgame players.

🐛Resolved audio cutting out during the ranked queue on certain sound cards.

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

🐛Fixed a memory spike that could cause a disconnect after long sessions.

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

🐛Fixed subtitles overlapping during {scene} cutscenes.

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

🐛Fixed a bug where the dropped loot tooltips showed the wrong stat values.

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

Crash & Error Fixes

How to Fix Crashes & Errors After Patch 3.0

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

💥Blue screen / driver timeout (amdkmdag / nvlddmkm) mid-match

Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 3.0.
Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
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.

💥Crash on entering the city district or fast-traveling

Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~500MB 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.

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 5 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.
High refresh rate monitors may cap at 60fps in borderless mode.	Pending fix	Use exclusive fullscreen until the next hotfix.

FAQ

Frequently Asked Questions About Patch 3.0

The exact questions players search after this patch drops:

QDo I need to download the whole game again?−

ANo. Patch 3.0 ships as a delta patch. Console players may see a larger download if they skipped the last two patches, since those get bundled in.

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

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

QIs my save file compatible with Patch 3.0?+

AYes. Patch 3.0 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 parry window fields on first load.

QWhen is the next patch after Patch 3.0?+

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.

QWhy is my FPS lower after Patch 3.0?+

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.

Bottom Line

Final Summary

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

👉 This page is permanently archived. Read the latest Lies of P patch notes →

⚠️ Important Disclaimer

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