Transitioning your setup from Fallout 4 version 1.10.163 to version 1.10.984 means moving from the long-standing pre-next-gen baseline to the major 2024 technical overhaul. This upgrade alters performance options, breaks legacy script extenders, and shifts how mods handle file structures. If you're returning to the wasteland or updating an existing installation, you need to understand what changed under the hood so you don't break your saves.
The core motivation behind moving past version 1.10.163 was the introduction of native current-gen console optimizations, widescreen display support, and official additions like the Enclave Remnants and Makeshift Weapon packs. However, these structural adjustments altered dynamic resolution settings, UI scaling, and common dynamic link libraries that thousands of community mods relied upon.
Understanding the Shift from 1.10.163 to 1.10.984
Version 1.10.163 served as the bedrock for PC modding for years. It was stable, predictable, and fully compatible with the Fallout 4 Script Extender (F4SE) in its mature state. When Bethesda pushed the code base to 1.10.984 (and subsequent hotfixes), the executable changed entirely. Memory addresses shifted, native UI scaling elements were rewritten to support ultra-widescreen monitors, and new Creation Club localization manifests were injected into the directory.
For players, this means your old plugin load orders and interface mods will likely throw errors or crash directly to the desktop upon launch. Knowing how to bridge the gap between these versions requires a careful audit of your data folder, your mod manager, and your graphics configuration profiles.
Key Technical Changes in the Update
The jump to version 1.10.984 introduced several display and system-level modifications that weren't present in 1.10.163.
- Frame Rate and Performance Settings: The update added native options to target frame rates of 30, 40, or 60 FPS, alongside toggles for Visuals versus Performance prioritization.
- Ultra-Widescreen Integration: Native support for 21:9 and 32:9 aspect ratios eliminated the need for third-party .ini tweaks or external patches for ultra-wide monitors, though it initially broke older custom HUD layouts.
- Creation Club Integration: A new "Installed Content" menu was bundled directly into the main menu, changing how internal archives (.bsa files) load alongside official DLCs.
Managing Mod Compatibility and F4SE
The single biggest hurdle when updating from 1.10.163 is script extension. F4SE relies on exact memory offsets within the game executable. Because version 1.10.984 changes those offsets, your old version of F4SE will fail instantly.
You must download the specific F4SE build designed for version 1.10.984 from the Silverlock Official Website. Furthermore, any mod that depends on native code DLL plugins—such as Address Library for F4SE Plugins or advanced physics tweaks—must be updated to their post-next-gen equivalents. Check the posts and files sections on the Nexus Mods Fallout 4 Page to ensure your utility mods match your current runtime version.
Step-by-Step Transition Strategy
If you are upgrading an active installation or setting up a clean directory, follow these steps to maintain stability:
- Back up your data directory: Make a complete copy of your Fallout 4 folder before letting your platform client apply the patch. This ensures you can revert if needed.
- Purge incompatible DLL mods: Open your mod manager (such as Mod Organizer 2 or Vortex) and temporarily disable all mods that rely on F4SE or UI frameworks like Fallout 4 Configuration Tool or older HUD replacements.
- Verify game files: Run a file integrity check through Steam Support to ensure your base game files match version 1.10.984 cleanly without lingering legacy loose files.
- Install updated core tools: Download the matching F4SE binaries and the updated Address Library plugin, dropping them directly into your main game directory alongside Fallout4.exe.
- Launch and test: Boot the game through your script extender loader, verify that the main menu loads without infinite loading screens, and load a throwaway save to test script functionality.
Common Pitfalls to Avoid
Many players run into trouble because they attempt to mix old UI frameworks with the new widescreen-native code. If your user interface text disappears or quest logs overlap, check for outdated Flash (.swf) interface replacer files. Another frequent issue involves shadow distance and graphics settings resetting automatically due to the restructuring of the default renderer preferences. Always re-apply your preferred tweaks via custom configuration files only after verifying the game boots successfully on vanilla settings.
Frequently Asked Questions
Can I downgrade from 1.10.984 back to 1.10.163?
Yes, many veteran modders prefer to downgrade to maintain compatibility with legacy adult or total-conversion mods. You can use specialized downgrade utilities found on community hubs like Nexus Mods that apply an older depot manifest to your executable.
Will my old save files work after updating?
Your save files will load, provided they do not rely on missing script-extended plugins. However, items added by new Creation Club content will inject themselves into your leveled lists immediately upon loading an existing save.
Why are my frame rates behaving strangely after the patch?
The update occasionally resets hardware thread settings in your configuration files. Ensure your renderer isn't defaulting to incorrect CPU thread counts, which can cause heavy stuttering during intense gunfights downtown.
Do I need to restart my playthrough?
A complete restart is rarely mandatory unless you are overhauling your entire mod list from scratch. However, starting fresh minimizes script lag and ensures quest triggers tied to updated cell edits execute cleanly.
