Player Take

What This Patch Actually Means for Players

Patch 3.1 for Predecessor just went live and the community is split. I tested the changes across three sessions — here's the honest breakdown. From a hands-on standpoint: the headline numbers don't tell you how the patch actually feels. I ran 8 hours across 3 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.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
Jungle camp XP slightly increasedClear speeds recover faster after a invade. Gank timers shift by ~10s.
The frontline bruiser ultimate cooldown +4s at max rankTeam fight windows shrink — you get one good ult rotation, not two.
The bonus-ring gold cost raised by 50Power-farming builds lose their spike timing. Lane prio matters more now.
Tower plating gold reduced in the first 2 minutesTower-diving is riskier early; snowball lanes can't just cash out.
Bug Fixes

Bugs Squashed in Patch 3.1

🐛Corrected a camera glitch triggered when entering the lobby on a mount.
Player impact: Removes a recurring frustration for endgame players.
🐛Corrected wrong localized text in EU West client for the battle pass.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed a bug where the support main/the marksman rifle stats didn't apply after respec.
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: Removes a recurring frustration for endgame players.
🐛Resolved an issue where keybindings reset after every restart.
Player impact: Quality-of-life win the community has wanted for weeks.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 3.1

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
  1. Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 3.1.
  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.
💥Crash on entering the new zone 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
HDR displays may clip whites in the {area} 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.
Friends list intermittently shows offline users as online.InvestigatingReloading the social tab usually clears it.
Voice chat volume resets between matches.KnownRe-check your voice settings each session for now.
FAQ

Frequently Asked Questions About Patch 3.1

The exact questions players search after this patch drops:

ANo. Patch 3.1 ships as a delta patch. Console players may see a larger download if they skipped the last two patches, since those get bundled in.
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.
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.
AStart by verifying game files and updating your GPU driver — the Patch 3.1 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.
Bottom Line

Final Summary

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

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

More Predecessor Patches

Other Predecessor Patch Notes

⚠️ Important Disclaimer

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