Smite Patch 3.2 Notes | Bug Fixes & Changes

Player Take

What This Patch Actually Means for Players

Logged about six hours on Smite since Patch 3.2 hit the servers. The patch notes read one way; the actual feel is another. Here's the gap. Here's the practical takeaway: the headline numbers don't tell you how the patch actually feels. I ran 5 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.

Key Changes

Balance & Feature Changes — With Player Impact

Change	What It Means for You
The legendary amulet gold cost raised by 100	Power-farming builds lose their spike timing. Lane prio matters more now.
Jungle camp XP slightly increased	Clear speeds recover faster after a invade. Gank timers shift by ~10s.
Tower plating gold reduced in the first 1 minutes	Tower-diving is riskier early; snowball lanes can't just cash out.

Bug Fixes

Bugs Squashed in Patch 3.2

🐛Resolved audio cutting out during the timed trial on certain sound cards.

Player impact: Closes a loophole that was skewing leaderboards.

🐛Corrected a UI freeze when scrolling the settings 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.

🐛Fixed subtitles overlapping during {scene} cutscenes.

Player impact: Closes a loophole that was skewing leaderboards.

🐛Fixed the ranked leaderboard not updating after a completed match.

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

🐛Corrected a camera glitch triggered when entering the main menu on a mount.

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

Crash & Error Fixes

How to Fix Crashes & Errors After Patch 3.2

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

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

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

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 20 minutes.	Investigating	Wait a few minutes before assuming items are lost.
Friends list intermittently shows offline users as online.	Investigating	Reloading the social tab usually clears it.
Some players still see the old the recon class/{weapon} stats until a full client restart.	Acknowledged	Restart the client after the patch downloads.
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.2

The exact questions players search after this patch drops:

QDo I need to download the whole game again?−

ANo. Patch 3.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.

QWhy is my FPS lower after Patch 3.2?+

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.

QWere any the dodge roll nerfed in Patch 3.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.

QWhen is the next patch after Patch 3.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.

Bottom Line

Final Summary

Patch 3.2 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 →

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Smite Patch 3.2 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.