Player Take

What This Patch Actually Means for Players

Patch 2.0 for Smite just went live and the community is split. I tested the changes across three sessions — here's the honest breakdown. Here's the practical takeaway: 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.

Netcode feels more honest after Patch 2.0. 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 base armor nerfed by 30Early-game trades swing against them. Pick safer matchups in lane.
The support main spell damage scaling loweredMid-game burst drops off. Build paths leaning into penetration are back.
Tower plating gold reduced in the first 3 minutesTower-diving is riskier early; snowball lanes can't just cash out.
Jungle camp XP slightly increasedClear speeds recover faster after a invade. Gank timers shift by ~10s.
Bug Fixes

Bugs Squashed in Patch 2.0

🐛Resolved audio cutting out during the co-op raid on certain sound cards.
Player impact: Removes a recurring frustration for endgame players.
🐛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.
🐛Fixed a memory spike that could cause a disconnect after long sessions.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed an achievement not unlocking when the condition was met offline.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed subtitles overlapping during {scene} cutscenes.
Player impact: Quality-of-life win the community has wanted for weeks.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 2.0

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 ~400MB 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.
💥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 2.0.
  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.
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
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.
Some players still see the old the ranged carry/{weapon} stats until a full client restart.AcknowledgedRestart the client after the patch downloads.
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 2.0

The exact questions players search after this patch drops:

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 2.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.
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.
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.
Bottom Line

Final Summary

Patch 2.0 is a solid, if unglamorous, update for Smite. 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 Smite patch notes →

More Smite Patches

Other Smite Patch Notes

⚠️ Important Disclaimer

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