Player Take

What This Patch Actually Means for Players

Logged about six hours on Predecessor since Patch 3.5 hit the servers. The patch notes read one way; the actual feel is another. Here's the gap. The part most players miss: the headline numbers don't tell you how the patch actually feels. I ran 4 hours across 3 sessions on PC and a couple of these changes ripple further than the notes suggest.

Netcode feels more honest after Patch 3.5. 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
The assault operator spell damage scaling loweredMid-game burst drops off. Build paths leaning into penetration are back.
Jungle camp XP slightly increasedClear speeds recover faster after a invade. Gank timers shift by ~10s.
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.5

🐛Resolved a bug where party members loaded into different instances.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed duplicated the dropped loot appearing after a server reconnect.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Fixed a memory spike that could cause a disconnect after long sessions.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed a bug where the assault operator/the marksman rifle stats didn't apply after respec.
Player impact: Removes a recurring frustration for endgame players.
🐛Corrected a camera glitch triggered when entering the main menu on a mount.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed a bug where the quest item tooltips showed the wrong stat values.
Player impact: Closes a loophole that was skewing leaderboards.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 3.5

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 hub or fast-traveling
  1. Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~600MB 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.
💥Game closes to desktop right after the splash screen on Patch 3.5
  1. Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
  2. Update your GPU driver to the latest NVIDIA build — the May/June branches break on this patch.
  3. Delete the cache folder at Documents/Predecessor/cache, then relaunch.
  4. 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
  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
Cross-save may delay inventory sync by up to 20 minutes.InvestigatingWait a few minutes before assuming items are lost.
HDR displays may clip whites in the {area} menu.Being worked onLower HDR peak luminance to 1000 nits in the system menu.
Voice chat volume resets between matches.KnownRe-check your voice settings each session for now.
High refresh rate monitors may cap at 60fps in borderless mode.Pending fixUse exclusive fullscreen until the next hotfix.
FAQ

Frequently Asked Questions About Patch 3.5

The exact questions players search after this patch drops:

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