Summary of "SURPRISE Baldur's Gate 3 Hotfix Update! All Changes"

Baldur’s Gate 3 surprise hotfix (Feb 16)

Overview

A surprise hotfix was released for Baldur’s Gate 3 with almost no official patch notes. The only visible developer-side changes on SteamDB were primarily “virtual texture” depot updates. Community investigation and testing uncovered a mix of fixes and newly introduced issues, especially affecting modded installs and console players.

What the video covers

The creator’s long-broken save files (about 75% of saves stuck when loading between Act 2 → Act 3, Rivington/Moonrise areas) began loading again after the hotfix.
Many players report mixed results:
- Some previously broken saves are now fixed.
- Others experience new problems: crashes, corrupted saves, poor menu FPS, and co-op join failures.
- Consoles (Xbox/PS5) and some GOG installations appear particularly affected in some reports.
SteamDB showed depot updates related to virtual textures, but no formal, detailed patch notes were posted publicly. Community threads and SteamDB entries were the main information sources.

Key technical points explained

Virtual texture interactions
- The hotfix appears to target conflicts involving virtual textures.
- Older mods that use many virtual textures could push a game past a hidden limit, causing load/save failures around Act 2/3.
Virtual texture limit
- Anecdotal reports point to a per-game limit (example given around ~57 virtual textures). Exceeding that can cause loading issues.
- The effective limit likely depends on GPU, VRAM, and platform.
Common problem mods
- Outfit mods and some older mods (pre-patch 8) were implicated in causing virtual texture conflicts.
- Mods that don’t rely on virtual textures are less likely to trigger these problems.
Modded saves
- The uploader had saves with roughly 400 mods; outfits disappeared if mods were removed/updated.
- After the hotfix the saves became usable again, though mod-related visual elements might be missing until corresponding mods are restored.

Practical tips and troubleshooting

If you have corrupted or un-loadable saves:
- Disable suspect mods (especially recent or outfit/visual mods) and try loading again.
- Use non-virtual-texture versions of outfit or large visual mods when available.
- Verify game files on your platform (Steam/GOG/console equivalents).
- Check SteamDB for depot changes and approximate update size.
If you get new issues after the hotfix:
- Test with mods disabled to isolate whether the problem is mod-related or caused by the patch.
- Report the issue to Larian with full details: platform, exact reproduction steps, the save file, list of installed mods, and screenshots/logs. Detailed reports help both developers and mod authors.
Cross-platform play and saves:
- Be cautious transferring saves between PS5 and PC if you use mods — cross-platform transfers increase complexity and risk.
General best practice:
- Keep backups: use multiple save slots or manual copies to avoid single-save breakage.

Notes about the hotfix distribution

Download sizes varied by platform and launcher:
- Some users reported tiny downloads (~131 MB).
- Others saw very large downloads (reports up to ~60 GB), depending on platform and launcher (GOG, Steam).
No official, detailed patch notes were published for this hotfix; most information came from community reporting and SteamDB depot entries.