⚠️ Fallout 4 Mod Troubleshooting

Launch the game through f4se_loader.exe, never the vanilla launcher. In Vortex set F4SE as the primary tool; in MO2 run the game via the F4SE executable you added. If it still fails, your F4SE build is for a different game version.

Bethesda bumped the game to a new runtime and F4SE plus mods had to catch up. On Steam, select the Fallout 4 - Previous Generation beta branch (game version 1.10.163) to keep older mods working, or update F4SE to a build that matches the current runtime.

Boston is the most crash-prone region. Install Buffout 4 (with its Address Library dependency) — it fixes the most common crash causes and writes a crash log naming the culprit. The Previsibines Repair Pack mod also stabilizes the city, and disabling volumetric lighting (bVolumetricLightingEnable=0 under [Display] in Fallout4Prefs.ini) is a stopgap.

Usually a mod or F4SE loading incorrectly, or a display-mode problem. Rename Fallout4Prefs.ini and let the launcher regenerate it, or switch to borderless window (bBorderless=1 and bFull Screen=0 under [Display]). If it only happens with mods enabled, disable your newest mods to isolate it.

A plugin references a master you do not have installed. In Vortex check the Plugins tab dependencies; in MO2 the right pane flags it. Install the missing master (usually listed on the mod's Requirements page) or disable the plugin, then run LOOT.

Usually a script-hungry mod or too many heavy texture mods. Disable mods one at a time to isolate it, and check the f4se.log in Documents/My Games/Fallout4/F4SE for errors. Moving the game to an SSD also helps if load times are the real problem.

Open the save in FallrimTools ReSaver and run its clean function to remove unattached instances and undefined elements from the .f4se save. Back up the save first, and re-test after disabling any mods you added right before the corruption.

Conflicting face textures. In MO2 make the face-texture mod load above mods that alter NPCs (higher priority in the left pane) and put any NPC-overhaul plugin below it, or reinstall the face texture mod. Having two incompatible texture packs installed causes this too.

An animation mod whose files are not loading. Confirm F4SE is running, re-deploy the animation mod in Vortex or MO2 so its files actually land in the Data folder, and check you are not running two animation frameworks that overwrite each other.

The game cannot find texture files a mod references — usually a broken or partial install. Reinstall the mod, make sure the Meshes and Textures folders sit at the correct depth under Data, and check the mod page for a required separate texture pack you skipped.

You are launching the vanilla launcher instead of through F4SE, or the plugin is not in plugins.txt. Launch through f4se_loader.exe and make sure %LOCALAPPDATA%/Fallout4/plugins.txt is not read-only. Also avoid opening the game's in-game Mods menu once you are modding — it can disable all external mods.

Set F4SE as the primary tool in Vortex's Games page so every launch goes through f4se_loader.exe. If Vortex does not detect F4SE at all, its files are not inside the game folder.

Install Buffout 4 and its Address Library dependency. Buffout 4 writes detailed crash logs to Documents/My Games/Fallout4/F4SE that name the crashing plugin, which turns guesswork into a targeted fix.

The vanilla launcher rewrites Fallout4.ini every time it runs. Put custom settings in Fallout4Custom.ini instead — the launcher leaves it alone — using the same section names, e.g. bInvalidateOlderFiles=1 under [Archive].

The outfits were never built. Run BodySlide/Outfit Studio through your mod manager (as an MO2 executable or a Vortex tool) so it writes to the correct Data folder, then build the outfits and redo it after changing body mods.

Missing meshes — the mod's Mesh files did not deploy. Reinstall the mod, verify the archive's folder structure is correct, and confirm the mod does not depend on a separate mesh pack you skipped.