Portal Knights Patch 4.2 Notes | Bug Fixes & Changes

Player Take

What This Patch Actually Means for Players

Quick reality check on Portal Knights Patch 4.2: some fixes land clean, a couple reintroduce old pain. I'll flag both so you're not blindsided. Here's the practical takeaway: 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 4.2. 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.

Key Changes

Balance & Feature Changes — With Player Impact

Change	What It Means for You
New the dropped loot added to the deep caverns loot tables	Gives a reason to revisit that biome you abandoned at hour 20.
Memory leak in long sessions patched	You can leave the world running overnight without the RAM climbing to the moon.
Save corruption on auto-save during chunk load fixed	Huge. Back up anyway, but the dreaded zero-byte save is mostly gone.

Bug Fixes

Bugs Squashed in Patch 4.2

🐛Fixed a bug where the equipped relic tooltips showed the wrong stat values.

Player impact: Removes a recurring frustration for endgame players.

🐛Fixed a bug where the vanguard hero/the battle rifle stats didn't apply after respec.

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: 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: Removes a recurring frustration for endgame players.

🐛Resolved a bug where party members loaded into different instances.

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

Crash & Error Fixes

How to Fix Crashes & Errors After Patch 4.2

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 4.2.
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.

💥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.

💥Crash on entering the new zone or fast-traveling

Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~600MB 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
Friends list intermittently shows offline users as online.	Investigating	Reloading the social tab usually clears it.
Cross-save may delay inventory sync by up to 20 minutes.	Investigating	Wait a few minutes before assuming items are lost.
HDR displays may clip whites in the {area} menu.	Being worked on	Lower HDR peak luminance to 1000 nits in the system menu.

FAQ

Frequently Asked Questions About Patch 4.2

The exact questions players search after this patch drops:

QWhen is the next patch after Patch 4.2?−

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.

QIs my save file compatible with Patch 4.2?+

AYes. Patch 4.2 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.

QWhy is my FPS lower after Patch 4.2?+

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

QDo I need to download the whole game again?+

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

QWere any the dodge roll nerfed in Patch 4.2?+

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.

Bottom Line

Final Summary

Patch 4.2 is a solid, if unglamorous, update for Portal Knights. The crash fixes alone justify the download; the balance tweaks will shake out over the next two weeks of play. Bookmark this page — it stays live as an archived reference even after the next patch drops.

👉 This page is permanently archived. Read the latest Portal Knights patch notes →

⚠️ Important Disclaimer

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