Player Take

What This Patch Actually Means for Players

Patch 3.5 for Fallout 4 just went live and the community is split. I tested the changes across three sessions — here's the honest breakdown. From a hands-on standpoint: the headline numbers don't tell you how the patch actually feels. I ran 7 hours across 2 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
Quest the companion arc progression blocker fixedIf you were soft-locked, reload an earlier save and re-trigger.
The vanguard hero companion AI no longer gets stuck on terrainThey actually keep up during traversal now. Small but huge QoL.
Texture streaming pop-in on the dungeon reducedThe city skyline stops flickering when you pan the camera fast.
Bug Fixes

Bugs Squashed in Patch 3.5

🐛Resolved a bug where party members loaded into different instances.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Fixed subtitles overlapping during {scene} cutscenes.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Corrected a camera glitch triggered when entering the hub on a mount.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Resolved an issue where keybindings reset after every restart.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed an achievement not unlocking when the condition was met offline.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Fixed duplicated the dropped loot appearing after a server reconnect.
Player impact: Removes a recurring frustration for endgame players.
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:

💥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 3.5.
  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.
💥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/Fallout4/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
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.
HDR displays may clip whites in the the open field menu.Being worked onLower HDR peak luminance to 1000 nits in the system menu.
Some players still see the old the support main/{weapon} stats until a full client restart.AcknowledgedRestart the client after the patch downloads.
FAQ

Frequently Asked Questions About Patch 3.5

The exact questions players search after this patch drops:

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.
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.
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 skill tree fields on first load.
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.5 is a solid, if unglamorous, update for Fallout 4. 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.

More Fallout 4 Patches

Other Fallout 4 Patch Notes

⚠️ Important Disclaimer

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