Player Take

What This Patch Actually Means for Players

Logged about six hours on Gwent since Patch 1.2 hit the servers. The patch notes read one way; the actual feel is another. Here's the gap. Reading between the lines: the headline numbers don't tell you how the patch actually feels. I ran 8 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.

The balance lands in a weird spot for Gwent. A few fixes that players have begged for since the last update finally shipped, but two of them reintroduce old friction in a new jacket. Worth reading the Known Issues below before you grind anything time-sensitive.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
The draw engine mana cost raised by 12The ubiquitous auto-include loses a slot. Deck diversity should rise.
Daily quest reroll cost reducedF2P loops get slightly friendlier. Stack the dailies you want.
Bug where the finisher spell trigger order was wrong fixedCombo decks play as intended — no more mystery lethals.
The staple minion rarity drop rate bumped in the core setCompletionists breathe easier. The chase legendary isn't a myth.
Bug Fixes

Bugs Squashed in Patch 1.2

🐛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: Quality-of-life win the community has wanted for weeks.
🐛Fixed a crash when opening the inventory immediately after a loading screen.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Corrected wrong localized text in SA client for the store.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Resolved an issue where keybindings reset after every restart.
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 1.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 new zone 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 1.2
  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/Gwent/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.
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 30 minutes.InvestigatingWait a few minutes before assuming items are lost.
Controller rumble stays on after disconnecting a pad.KnownReconnect and disconnect the controller again to reset it.
HDR displays may clip whites in the {area} menu.Being worked onLower HDR peak luminance to 1000 nits in the system menu.
FAQ

Frequently Asked Questions About Patch 1.2

The exact questions players search after this patch drops:

ANo. Patch 1.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.
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 1.2 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.
AYes. Patch 1.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 crafting bench fields on first load.
Bottom Line

Final Summary

If you held off updating because of the early crash reports, Patch 1.2 is now safe to grab on most rigs. The fixes above cover the worst offenders. See you in the next patch notes — this page stays permanent.

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

More Gwent Patches

Other Gwent Patch Notes

⚠️ Important Disclaimer

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