The hype around Fallout London has players hammering refresh like it’s a VATS crit, and that traffic spike is exactly where this error comes from. When you see an HTTPSConnectionPool 502 error tied to Gamerant while researching how to install the mod, it’s not your PC, your browser, or your Fallout 4 setup breaking. It’s the internet equivalent of a quest NPC getting stuck in a door because too many scripts fired at once.
This showed up because Fallout London isn’t a normal mod drop. It’s a full-scale total conversion that rewires Fallout 4’s assets, quests, and worldspace, and everyone wants a clean install guide across Steam, GOG, and Epic at the same time. When thousands of players and automated tools hit the same article endpoint, servers start rolling natural 1s.
What a 502 Error Really Is in Plain English
A 502 Bad Gateway error means one server asked another server for data and got garbage back. Gamerant’s front-facing server tried to fetch content from its backend, CDN, or cache layer and received an invalid or empty response. Think of it like Fallout 4 calling a texture that failed to load, resulting in a purple mess instead of a vault wall.
The HTTPSConnectionPool part tells us this wasn’t just a one-off hiccup. Multiple retry attempts were made, and every single one failed because the upstream server kept returning errors. That’s why the system eventually gave up and threw the message you saw.
Why Fallout London Guides Triggered It Specifically
Fallout London research is a perfect storm for server strain. Players need platform-specific instructions because Steam, GOG, and Epic handle Fallout 4’s file structure, DRM, and executable behavior differently. That means long, heavily trafficked articles with lots of embedded assets, outbound links, and update revisions.
When a guide like that goes semi-viral, Gamerant’s servers may start rate-limiting requests or failing to propagate cached versions fast enough. Automated scrapers, Discord bots, and even mod managers checking URLs can unintentionally DDoS a page without malicious intent.
Why This Has Nothing to Do With Your Fallout 4 Install
It’s easy to assume the error means Fallout London is unstable or that install instructions are broken. That’s not the case. This error happens before you ever touch Fallout4.exe, F4SE, or the London installer files.
Your load order, plugin limit, and archive invalidation have zero influence here. The failure happens entirely at the web server level, long before your GPU drivers, INI tweaks, or mod staging folders enter the picture.
What This Tells Us About Fallout London’s Launch Window
Errors like this are a dead giveaway that interest is peaking hard. Total conversions don’t generate this kind of traffic unless they’re hitting that sweet spot between hype and availability. Fallout London crossed that line, and the infrastructure around it briefly buckled.
For players, this is actually useful intel. It means guides may be temporarily unreachable, mirrors might differ slightly, and instructions can change fast as installers get patched. Understanding why the error appeared puts you ahead of the curve before you even start prepping Fallout 4 for London’s first boot.
Fallout London PC Requirements and Supported Fallout 4 Versions (Steam, GOG, Epic Games Store)
All that server chaos leads to the obvious next question: can your PC and your copy of Fallout 4 actually run Fallout London once you get the files? This is where a lot of first-time total conversion players stumble, because Fallout London is not a lightweight mod you can brute-force through bad specs or mismatched versions.
Fallout London replaces nearly everything except the Creation Engine itself. Think new worldspaces, bespoke assets, custom animations, fresh scripting, and an entirely different progression curve. If your system barely scraped by in vanilla Fallout 4, London will expose every weak link fast.
Minimum and Recommended PC Requirements
At a baseline, Fallout London expects the same hardware as a fully modded Fallout 4 setup, not a clean install. An SSD is effectively mandatory, not optional, due to the sheer volume of assets and streaming data during cell transitions.
Minimum specs line up around a quad-core CPU, 8GB of RAM, and a GPU in the GTX 970 or RX 480 tier. You might technically boot below that, but expect brutal load times, texture pop-in, and stutter whenever the engine has to stream London’s dense urban cells.
For a stable experience, 16GB of RAM and a modern mid-range GPU like a GTX 1660, RTX 2060, or RX 5600 XT is the real floor. Fallout London leans heavily on draw calls and scripting, so CPU single-core performance still matters more than raw GPU horsepower.
Which Fallout 4 Versions Are Actually Supported
This is where platform choice matters more than most guides make it sound. Fallout London requires Fallout 4 with all DLC installed, and that requirement is non-negotiable. Missing even one DLC will hard-stop the installer or crash the game at launch.
Steam, GOG, and Epic Games Store versions are all supported, but they are not equal in setup complexity. The mod is built around Fallout 4’s pre–Next-Gen update executable behavior, which means version control is critical.
Steam Version: Most Compatible, Most Common
Steam is the most straightforward platform for Fallout London, primarily because it plays nicely with F4SE and version rollback tools. If your Steam copy updated to the Next-Gen patch, you will need to downgrade to the last pre-update version before installing London.
This isn’t optional. Fallout London relies on script extenders and engine hooks that simply do not work on the Next-Gen executable. Once downgraded, Steam users get the smoothest path for mod managers, INI control, and troubleshooting.
GOG Version: DRM-Free and Surprisingly Clean
The GOG release of Fallout 4 is fully supported and, in some ways, ideal. It ships DRM-free and does not auto-update unless you tell it to, which means you can lock your version and avoid surprise patches breaking your setup.
However, GOG installs Fallout 4 in a slightly different directory structure. That means you must double-check paths when pointing the Fallout London installer or your mod manager to Fallout4.exe. Once configured correctly, stability is excellent and long-term maintenance is easier than Steam.
Epic Games Store Version: Supported, But Expect Extra Steps
Yes, the Epic Games Store version works, but it’s the least beginner-friendly option. Epic handles file verification and updates aggressively, which can overwrite downgraded executables if you’re not careful.
F4SE compatibility is more fragile here, and you’ll need to manually confirm that the executable version matches Fallout London’s requirements before launching. If Epic is your only option, it’s doable, but expect more hands-on troubleshooting during setup.
Critical Prerequisites Before You Install Anything
Regardless of platform, start with a clean Fallout 4 install. No leftover mods, no old INI tweaks, and no half-removed script extenders lurking in your Data folder. Fallout London is a total conversion, not a load-order-friendly add-on.
Disable cloud saves, especially on Steam and Epic. Cloud sync conflicts can corrupt London’s save structure on first boot, leading to crashes that look like installer failures but aren’t.
Most importantly, do not attempt to merge Fallout London with an existing mod list. Treat it like a separate game. If you approach it with that mindset, you avoid 90 percent of the errors that flood Discord and Reddit during launch week.
Pre-Installation Checklist: Clean Fallout 4 Setup, DLC Validation, and Modding Tool Prerequisites
This is the point where most installs either succeed cleanly or spiral into mystery crashes. Fallout London is not forgiving if your Fallout 4 foundation is messy, partially modded, or missing key components. Before you even think about running the installer, lock in the following checks.
Verify a Truly Clean Fallout 4 Install
A “clean” install means more than uninstalling mods from a manager. You need zero leftover files from previous setups, including loose scripts, textures, or old F4SE binaries hiding in the Data folder.
After uninstalling Fallout 4, manually delete the entire Fallout 4 directory. Then check Documents\My Games\Fallout4 and remove Fallout4.ini and Fallout4Custom.ini so the game can regenerate them fresh on first launch.
Once reinstalled, launch Fallout 4 once and reach the main menu. This step forces the engine to rebuild INIs and registry entries, which Fallout London relies on to hook correctly.
DLC Validation: Non-Negotiable Requirements
Fallout London requires every major Fallout 4 DLC. That includes Automatron, Wasteland Workshop, Far Harbor, Contraptions Workshop, Vault-Tec Workshop, and Nuka-World.
Open the in-game Add-Ons menu or your platform’s DLC manager and confirm every DLC is installed and enabled. Missing even one will result in silent crashes or infinite loading screens during London’s intro sequence.
If you’re on Steam or Epic, run a file verification after installing DLCs. On GOG, use Galaxy’s repair feature or manually confirm the DLC folders exist inside the Data directory.
Folder Structure and Install Location Checks
Avoid installing Fallout 4 inside Program Files. Windows permissions can block script injection and virtual file access, which breaks mod managers and F4SE behavior.
If possible, install Fallout 4 to a root-level directory like C:\Games\Fallout 4 or a separate SSD. Faster read speeds noticeably reduce stutter during London’s first boot and scripted sequences.
For GOG and Epic users especially, double-check that the Fallout London installer is pointed at the correct Fallout4.exe. Auto-detection fails more often on non-Steam versions.
Mod Manager Requirements: Pick One, Set It Up Properly
You need a modern mod manager, even if Fallout London handles most of the heavy lifting. Mod Organizer 2 is strongly recommended due to its virtual file system and profile support.
Vortex technically works, but troubleshooting is harder and load-order visibility is worse for total conversions. If you’re new to modding, MO2’s learning curve pays off fast here.
Install your mod manager before Fallout London and launch it once to confirm it detects Fallout 4 correctly. Do not import old mod lists or profiles.
F4SE and Runtime Compatibility
Fallout London depends on Fallout 4 Script Extender, but only specific runtime versions are supported. This is where Next-Gen updates cause the most damage.
Confirm your Fallout 4 executable version matches Fallout London’s documentation before installing F4SE. Installing the wrong F4SE build will prevent the game from launching at all.
Never overwrite F4SE files from an older setup. Extract fresh, version-matched files directly into the Fallout 4 root folder.
INI Settings, Cloud Saves, and Background Interference
Keep INI files vanilla at this stage. No custom memory tweaks, no old graphics presets, and no performance configs meant for heavily modded playthroughs.
Disable Steam Cloud or Epic Cloud saves for Fallout 4. London uses its own save structure, and cloud sync conflicts can corrupt saves on first launch.
Finally, whitelist your Fallout 4 folder in your antivirus. Script-heavy installers and executables get flagged surprisingly often, especially during London’s install process.
Free Space and Patience
Fallout London is massive. Make sure you have at least 50 GB of free space beyond your Fallout 4 install to account for extraction, patching, and future updates.
Rushing this checklist is how players end up reinstalling everything twice. Lock this foundation in now, and the actual Fallout London install becomes dramatically smoother.
Step-by-Step Installation: Fallout London on Steam Fallout 4
With your foundation locked in, this is where the actual install begins. Steam users have the smoothest path, but only if Fallout 4 is pinned to the correct runtime and kept there. Follow these steps in order, don’t skip ahead, and resist the urge to “optimize” anything until London boots successfully.
Step 1: Lock Fallout 4 to the Correct Steam Version
Before downloading anything London-related, open Steam and disable automatic updates for Fallout 4. Set updates to “Only update when I launch,” then never launch the vanilla game through Steam again.
If Fallout 4 has already received the Next-Gen update, you must downgrade to the supported runtime using a trusted downgrade patcher. Fallout London will not function correctly on unsupported executables, and no amount of load-order tweaking will fix that.
Once downgraded, back up Fallout4.exe and Fallout4Launcher.exe. This gives you a rollback point if Steam tries to get clever later.
Step 2: Verify a Clean Fallout 4 Install
Open Steam, right-click Fallout 4, and verify integrity of game files. This ensures your base game is unmodified and free of leftover scripts or loose files.
Do not install Creation Club content, texture packs, or “essential” mods. Fallout London is a full conversion and expects a vanilla baseline, not a Frankenstein build.
Launch Fallout 4 once from Steam to generate fresh INI files, then close it immediately after reaching the main menu. Do not start a new game.
Step 3: Download Fallout London from the Official Source
Download the Fallout London installer only from the official Fallout London site or their verified distribution links. Avoid mirrors, torrents, or repacks, as incomplete archives are a common source of crashes and missing assets.
The installer is large and script-heavy, so expect a long download and extraction time. If your antivirus is aggressive, temporarily disable real-time scanning during this step to prevent silent file quarantines.
Do not extract or run the installer inside the Fallout 4 directory yet.
Step 4: Configure Mod Organizer 2 for Fallout London
Launch Mod Organizer 2 and create a brand-new profile specifically for Fallout London. Disable profile sharing for INI files and saves to keep London isolated from vanilla Fallout 4.
Point MO2 to your Fallout 4 installation when prompted. Confirm that the game binary path and data directory are correct before proceeding.
Do not add any mods, plugins, or executables beyond Fallout 4 itself at this stage.
Step 5: Run the Fallout London Installer
Run the Fallout London installer as administrator. When prompted for an install location, select your Fallout 4 root folder, not the Data subfolder.
The installer will handle asset deployment, plugins, and London-specific scripts automatically. This process can take several minutes and may appear frozen during heavy file operations; let it finish.
If the installer throws errors about missing files or permissions, stop and fix those now. Re-running a failed install without correcting the cause usually compounds problems.
Step 6: Install and Verify F4SE for London
Extract the correct F4SE build for your Fallout 4 runtime directly into the Fallout 4 root directory. This includes the F4SE loader executable and associated DLLs.
Do not install F4SE through MO2 for Fallout London. The script extender must sit at the engine level to hook properly.
In MO2, add f4se_loader.exe as a new executable and set it as the default launch option for this profile.
Step 7: First Launch and Validation
Launch Fallout London using F4SE through Mod Organizer 2. The first boot is slow, with longer black screens and delayed audio initialization.
If the main menu shows Fallout London branding, the conversion is active. Start a new game only; loading old Fallout 4 saves will break progression scripts almost instantly.
Once in-game, wait until all background initialization finishes before moving or opening menus. This prevents early script desyncs that can haunt a save hours later.
Common Steam-Specific Errors and Fixes
If the game instantly closes on launch, your Fallout 4 runtime and F4SE versions do not match. Re-check executable versions before reinstalling anything.
Missing textures or invisible NPCs usually indicate an incomplete installer run or antivirus interference. Reinstall Fallout London after whitelisting the entire Fallout 4 folder.
If Steam tries to update Fallout 4, restore your backed-up executables immediately and re-lock updates. One accidental patch can invalidate the entire setup.
Playing London Safely After Install
Always launch through MO2 and F4SE, never directly from Steam. Treat Fallout London as its own game, not a modded Fallout 4 playthrough.
Avoid adding mods until you’ve completed at least the opening hours. London’s scripts are dense, and early instability is almost always user-inflicted.
This same disciplined approach applies to GOG and Epic versions of Fallout 4, but Steam users benefit most from strict version control. Get this right once, and Fallout London delivers one of the most ambitious total conversions Bethesda’s engine has ever seen.
Step-by-Step Installation: Fallout London on GOG and Epic Games Store Versions
If you’re coming from the Steam workflow, here’s the good news: Fallout London is fully playable on GOG and Epic Games Store builds of Fallout 4. The bad news is that both storefronts require extra attention to file paths, executable handling, and version parity.
The underlying rules don’t change. Fallout London is a total conversion that replaces Fallout 4 at runtime, and it demands a clean, controlled environment. What changes is how GOG and Epic handle updates, DRM, and executable structure.
Prerequisites: Fallout 4 Version and DLC Check
Before touching Mod Organizer 2 or the Fallout London installer, verify that your Fallout 4 installation includes all DLC. Fallout London hard-depends on every official expansion, including Automatron and Nuka-World.
On GOG, this is straightforward. Use GOG Galaxy to confirm all DLC is installed, then fully exit the launcher to prevent background file verification.
On Epic Games Store, open the Fallout 4 manage menu and confirm every add-on is enabled and downloaded. Epic sometimes silently skips DLC installs, which leads to missing world assets and broken quest triggers later.
Step 1: Disable Auto-Updates and File Verification
Unlike Steam, GOG and Epic don’t aggressively force updates, but both can still invalidate your setup if left unattended.
For GOG, disable auto-updates in Galaxy and avoid using the Verify/Repair option once Fallout London is installed. That process will overwrite modified executables without warning.
For Epic, go one step further. Set the game to offline mode after installation. Epic’s file verification is notorious for restoring vanilla files the moment it detects modified launch behavior.
Step 2: Install Mod Organizer 2 for a Non-Steam Build
Install Mod Organizer 2 outside of Program Files, ideally on the same drive as Fallout 4. This avoids Windows permission issues that can break virtual file system hooks.
When MO2 asks for a game association, manually point it to your Fallout 4 directory. GOG and Epic installs are not always auto-detected, so double-check the path before proceeding.
Create a dedicated profile named Fallout London. Disable profile-specific INI files unless you already know how to manage custom INI stacks.
Step 3: Installing Fallout London Files
Run the Fallout London installer and point it directly at the Fallout 4 root directory, not the Data folder. This step is identical across Steam, GOG, and Epic.
Allow the installer to complete without interruption. This process touches thousands of files, and interrupting it can cause missing meshes, audio stutter, or NPCs failing to spawn.
Once finished, do not launch the game yet. Fallout London is present, but it won’t function correctly without F4SE and MO2 integration.
Step 4: Installing F4SE for GOG and Epic
Download the correct F4SE build that matches your Fallout 4 runtime version. GOG and Epic often use different executable builds than Steam, so version matching is non-negotiable.
Extract F4SE directly into the Fallout 4 root directory. You should see f4se_loader.exe sitting alongside Fallout4.exe.
As with Steam, do not install F4SE through MO2. Script extenders must hook at the engine level, not the virtualized mod layer.
Step 5: Configuring MO2 Executables
Open MO2 and add a new executable. Point it to f4se_loader.exe in your Fallout 4 directory.
Set this as the default launch option for the Fallout London profile. From this point forward, this is the only way you should ever launch the game.
If you see Fallout4.exe listed as the active executable, stop and fix it. Launching the vanilla executable bypasses Fallout London’s scripting entirely.
Step 6: First Launch on GOG and Epic
Launch Fallout London through MO2 using F4SE. Expect a slow first boot, including long black screens and delayed audio.
If the main menu displays Fallout London branding, the conversion is active. Start a new game only; existing Fallout 4 saves are incompatible and will hard-lock progression scripts.
Once gameplay begins, do nothing for at least 30 seconds. Let scripts initialize, audio banks load, and NPC packages settle before moving or opening menus.
Common GOG and Epic Errors and Fixes
Instant crashes on launch almost always mean an F4SE mismatch. Re-check the runtime version of Fallout 4 and reinstall the correct script extender.
Missing voices or silent dialogue usually indicate incomplete DLC installs, especially Automatron. Re-verify DLC ownership and reinstall if needed.
If Epic restores vanilla files after a successful launch, you forgot to disable verification or went back online. Reinstall Fallout London and lock the setup down again.
Best Practices for Long-Term Stability
Treat Fallout London as its own standalone RPG. Never mix it with an existing Fallout 4 mod list, and avoid adding extra mods until you’re deep into the campaign.
Always launch through MO2 and F4SE, regardless of storefront. Direct launches from GOG Galaxy or Epic will bypass critical hooks.
Handled correctly, the GOG and Epic versions are just as stable as Steam, with fewer forced updates and more long-term control. That control is exactly what a mod of this scale demands.
Common Installation & Launch Errors (502 Errors, Script Extender Issues, Missing Masters) and How to Fix Them
Even with a clean setup, Fallout London is big enough to expose every weak link in your install chain. Most failures aren’t random crashes or bad luck with RNG; they’re predictable errors tied to downloads, script extenders, or missing dependencies. If your game won’t boot, freezes on a black screen, or dies before the main menu, start here.
502 Errors When Downloading Fallout London or Dependencies
A 502 error isn’t a problem with your PC or Fallout 4. It’s a server-side failure, usually caused by traffic spikes hammering sites like GameRant mirrors, Nexus Mods, or the Fallout London CDN.
If a download fails with repeated 502 responses, stop refreshing. Use a download manager, switch to a different mirror, or wait an hour and try again during off-peak times.
Corrupted downloads are a silent killer. If Fallout London installs but crashes instantly, delete the archive and re-download it completely rather than trying to repair the existing files.
F4SE Script Extender Mismatch and Launch Crashes
If the game crashes before the intro video or never reaches the main menu, this is almost always an F4SE issue. Fallout London relies heavily on script hooks, and even a minor runtime mismatch will hard-stop the engine.
Verify your Fallout 4 runtime version first. Steam, GOG, and Epic all ship slightly different executables, and auto-updates can desync F4SE without warning.
Download the exact F4SE build that matches your runtime and reinstall it manually. Replace all files, then relaunch exclusively through f4se_loader.exe inside MO2.
Missing Masters Errors in MO2
If MO2 throws a red warning about missing masters, don’t ignore it. Fallout London requires every Fallout 4 DLC, including Automatron, Wasteland Workshop, Far Harbor, Contraptions, Vault-Tec Workshop, and Nuka-World.
This error usually appears when a DLC failed to install, didn’t register correctly, or was disabled by the storefront. Epic and GOG are especially prone to partial DLC installs after verification.
Open your Fallout 4 Data folder and confirm each DLC plugin exists. If even one is missing, re-verify the game, reinstall the DLC, and relaunch MO2 so it can re-index the load order.
Black Screen on Launch or Infinite Loading
A long black screen on first launch is normal. An infinite one is not.
If the game sits black for more than five minutes with no audio, it usually means scripts failed to initialize. This points back to F4SE, a corrupted install, or launching the wrong executable.
Double-check that MO2 is set to launch F4SE and not Fallout4.exe. One wrong click here bypasses Fallout London entirely and soft-locks the engine.
Silent Dialogue, Missing Audio, or Broken Quests
Silent NPCs and broken quest triggers are almost never bugs in Fallout London itself. They’re symptoms of missing DLC assets or incomplete sound archives.
Automatron is the most common offender. If it’s missing or corrupted, dialogue systems break in ways that look like quest bugs.
Reinstall the affected DLC, then start a new game. Fallout London does not recover cleanly once scripting fails early, and continuing a broken save only compounds the damage.
Steam, GOG, and Epic-Specific Pitfalls
Steam users need to disable automatic updates after confirming the correct runtime. A surprise patch will instantly break F4SE and prevent launches.
GOG users should avoid Galaxy’s repair function once Fallout London is installed. It can restore vanilla files and overwrite custom scripts.
Epic users must stay offline after setup. Going back online can trigger file verification that strips Fallout London out without warning, forcing a full reinstall.
When to Reinstall Instead of Troubleshooting
If you’ve fixed F4SE, verified DLCs, and confirmed MO2 is launching correctly but crashes persist, stop digging deeper. Fallout London’s size means small errors snowball fast.
A clean reinstall of Fallout 4, followed by Fallout London, is often faster than chasing a corrupted file across multiple directories. Treat it like wiping a bad save after a failed boss run; painful, but efficient.
Once installed correctly, Fallout London is stable, consistent, and shockingly polished for a total conversion. Most launch issues happen before the first step into London, not after.
Load Order, Mod Manager Configuration, and Best Practices for a Stable First Launch
At this point, assume your install is clean and Fallout London is present. Stability now comes down to discipline: correct load order, a properly configured mod manager, and resisting the urge to tweak before the game proves it can boot cleanly.
This is where most first-time total conversion installs fail. Not because Fallout London is fragile, but because Fallout 4’s engine is unforgiving when mods step out of line.
Use Mod Organizer 2, Not Vortex
Fallout London is built with Mod Organizer 2 in mind, and that matters. MO2’s virtual file system ensures Fallout London never permanently overwrites vanilla files, which makes troubleshooting and reinstalls dramatically safer.
Vortex can work, but it introduces unnecessary risk with hard links and auto-sorting. For a total conversion this large, control beats convenience every time.
Create a fresh MO2 instance specifically for Fallout London. Do not reuse a heavily modded Fallout 4 profile unless you enjoy chasing invisible conflicts.
Correct Load Order: What Should and Shouldn’t Be There
Fallout London replaces Fallout 4’s worldspace, quests, NPCs, and progression systems. That means your load order should be brutally minimal.
Only these should be active:
Fallout4.esm
All official DLCs
FOLON’s master files and plugins
No texture packs. No gameplay tweaks. No UI mods. Even harmless-looking HUD mods can break early scripts or soft-lock the opening sequence.
If LOOT suggests changes, ignore it unless the Fallout London team explicitly recommends otherwise. Auto-sorting tools don’t understand total conversions and often make things worse.
Plugin Order and Archive Handling
In MO2’s right pane, Fallout London’s plugins should load after all official DLCs. Do not manually drag them above DLC masters, even if MO2 throws warnings.
Archive invalidation should remain enabled, but do not force loose file priority unless the installer explicitly instructs you to. Fallout London relies on packed archives for stability and performance.
If you see red missing master warnings, stop immediately. Launching with missing masters is how you corrupt saves before the main menu even appears.
INI Files, Profiles, and Engine Stability
Use profile-specific INI files in MO2. This isolates Fallout London from any old Fallout 4 tweaks you forgot existed.
Do not apply performance INI tweaks, ultra presets, or engine fixes before first launch. Fallout London already pushes the engine hard, and premature tweaks introduce variables you can’t diagnose later.
Let the game generate fresh INIs on first boot. You can optimize later, after you’ve confirmed the opening sequence runs without stutters, missing audio, or script delays.
Launching the Game the Right Way
Always launch through F4SE inside MO2. This is non-negotiable across Steam, GOG, and Epic.
Steam users should confirm the runtime version matches F4SE exactly before launching. GOG and Epic users must ensure MO2 points to the correct Fallout 4 install directory, not a duplicated or redirected one.
If the game boots but Fallout London branding doesn’t appear, you launched the wrong executable. Close it immediately and fix it before continuing.
First Launch Rules That Prevent 90 Percent of Crashes
On first boot, do nothing. Let the game sit at the main menu for a full minute to allow background scripts to initialize.
Start a new game and do not skip intro sequences unless the mod explicitly allows it. Skipping can desync scripts and cause missing NPCs or broken quests later.
Do not alt-tab, open overlays, or adjust graphics mid-intro. Treat the first launch like a scripted boss phase: hands off until control is clearly returned.
Resist Modding Until London Works
Once you step into London and complete the opening moments without errors, you’ve cleared the hardest part. Only then should you consider adding quality-of-life mods, and even then, one at a time.
Total conversions are ecosystems, not mod lists. Every added plugin changes aggro, RNG, and script timing in ways you won’t see until hours later.
Stability isn’t about how many mods you can stack. It’s about proving the foundation is solid before you build on it.
Performance Optimization, Known Compatibility Issues, and Recommended Post-Install Tweaks
Once Fallout London boots cleanly and you’ve confirmed quests, audio, and NPC behavior are functioning, it’s time to optimize. This is where you squeeze stability and framerate out of an engine that was already flirting with its limits in vanilla Fallout 4.
Treat optimization like tuning a build after the tutorial, not min-maxing before you know how the weapon handles. Every change here should be deliberate, tested, and reversible.
Fallout London Performance Reality Check
Fallout London is heavier than vanilla Fallout 4 in almost every way. Denser city spaces, higher NPC counts, longer draw distances, and aggressive scripting all stack CPU load before your GPU even enters the conversation.
If you’re CPU-bound, no amount of ultra textures will fix stutters. Players on older quad-core CPUs will feel this first, especially in outdoor hubs and transit-heavy areas.
Lock your expectations to stability first. A consistent 50–60 FPS with clean frame pacing beats an unstable 90 that collapses during combat or scripted events.
Recommended Graphics Settings That Actually Matter
Start with the in-game High preset, not Ultra. Ultra shadows and god rays are the single biggest FPS killers in Fallout London’s cityscapes.
Set Shadow Distance to Medium and Shadow Quality to High manually. This preserves visual depth without hammering draw calls during combat-heavy zones.
God Rays should be Low or Medium, and Weapon Debris must be Off unless you have an NVIDIA GPU. AMD users will crash here, full stop.
INI Tweaks You Should Apply After First Launch
Once the game has generated fresh INIs, minor adjustments can smooth performance without destabilizing scripts. Enable iPresentInterval=0 only if you plan to cap FPS externally through your GPU control panel or RTSS.
Increase uExterior Cell Buffer slightly if you have 16GB+ RAM. This reduces streaming stutter when moving between dense districts but should never be pushed aggressively.
Avoid outdated Fallout 4 tweak packs you find on forums. Fallout London’s worldspace and scripts are not vanilla, and copy-paste configs often cause long-term instability.
Engine Fixes and Plugins That Are Safe to Add
Buffout 4 is strongly recommended once stability is confirmed. It improves crash logging and memory handling without touching gameplay systems.
High FPS Physics Fix is safe if you plan to run above 60 FPS, but only after confirming the game behaves normally at stock settings. Physics desyncs in a total conversion can soft-lock quests hours later.
Do not install precombines or previs repair mods. Fallout London uses custom world optimization, and external fixes will break it.
Known Compatibility Issues Across Steam, GOG, and Epic
Steam users must disable automatic updates for Fallout 4. A runtime mismatch will instantly break F4SE and prevent Fallout London from launching.
GOG and Epic versions work fully, but the install path must be correctly detected by MO2. If MO2 points at a stub or redirected folder, the game may launch without London content loaded.
Cloud saves should be disabled across all platforms. Save corruption in a total conversion behaves like a delayed debuff, appearing hours after the initial mistake.
Common Errors and What They Actually Mean
Infinite loading screens usually indicate script overload, not a bad save. This often comes from enabling performance mods too early or skipping intro sequences.
Missing audio or ambient soundscapes point to archive invalidation issues or an incomplete install. Re-run the installer before troubleshooting anything else.
CTDs when entering new districts are almost always memory-related. Lower shadow settings and confirm Buffout logs before reinstalling.
Quality-of-Life Mods That Won’t Break the Game
After several stable hours, minimal QoL mods can be introduced. Interface mods like FallUI are generally safe and improve inventory management without touching scripts.
Quick Save hotkeys and map UI enhancements are fine if they don’t inject new quests or systems. Avoid survival overhauls, combat AI mods, or perk rewrites entirely.
Add one mod, test for 30 minutes, then proceed. Fallout London is less forgiving than vanilla Fallout 4 when it comes to hidden conflicts.
Post-Install Habits That Preserve Long-Term Stability
Create manual saves before major quest steps, not during them. Script-heavy moments are the worst time to rely on autosaves.
Avoid fast travel spam in dense areas. Let cells load fully to prevent NPC and quest desync.
If something feels off, stop playing and investigate immediately. Fallout London punishes “I’ll fix it later” more than any Bethesda release before it.
At this stage, you’re no longer just playing a mod. You’re maintaining a custom RPG build, and treating it with that respect is what turns a fragile install into a rock-solid London wasteland experience.
Verifying a Successful Installation and What to Do If Fallout London Still Won’t Launch
At this point, you’ve done the heavy lifting. Before diving into deeper troubleshooting, you need to confirm that Fallout London actually installed and is being called correctly by Fallout 4. Most launch failures happen because the game is still booting vanilla assets or the executable isn’t pointing at the London runtime.
How to Confirm Fallout London Is Actually Loaded
The fastest verification is the main menu. A successful install replaces the standard Fallout 4 background and branding with Fallout London-specific visuals and music. If you still see the vanilla menu, the mod is not being loaded, no matter what MO2 or Vortex claims.
Next, start a new game. Fallout London does not reuse the Fallout 4 intro. If you wake up in the pre-war bathroom or see the Vault-Tec opening, something is wrong with your load order or launch method.
Finally, check the Data folder Fallout London installs into. You should see large custom BA2 archives and London-specific folders. If those files aren’t there, the installer didn’t complete properly, even if it said it did.
Steam, GOG, and Epic-Specific Launch Checks
On Steam, Fallout 4 must be downgraded to the pre-next-gen version. If Steam auto-updated, Fallout London will silently fail or crash on launch. Set Fallout 4 to only update when launched, then always launch through MO2 or the Fallout London launcher.
GOG users have it easier, but still need to confirm the correct executable is selected. GOG installs don’t always default to the same folder structure MO2 expects, so manually verify the game path in your mod manager.
Epic Games Store is the most fragile setup. EGS overlays and cloud services can interfere with script initialization. Disable the Epic overlay, turn off cloud saves, and always run the game executable as administrator.
When the Game Crashes Immediately on Launch
Instant CTDs almost always mean a version mismatch. Double-check that Fallout 4 Script Extender matches your exact Fallout 4 build. Even being one version off will cause a hard crash before the menu appears.
Buffout 4 logs are your best diagnostic tool here. If the log points to memory allocation or renderer failures, lower graphics settings before reinstalling anything. Shadows and weapon debris are notorious crash triggers in total conversions.
If there’s no log at all, antivirus software may be blocking file access. Whitelist the entire Fallout 4 and Fallout London directories and try again.
Fixing Black Screens, Infinite Loads, and Soft Locks
A black screen with audio usually indicates archive loading failure. Re-run the Fallout London installer and make sure it finishes without interruption. Partial installs are more common than players realize.
Infinite loading screens after selecting New Game typically mean script overload. Disable any extra mods, even harmless-looking ones, and test with Fallout London alone. Performance tweaks belong after stability, not before it.
Soft locks during early gameplay often come from skipping dialogue or alt-tabbing during scripted sequences. Fallout London relies heavily on timed triggers, and breaking them can stall quests permanently.
If All Else Fails: The Clean Reset Method
Uninstall Fallout London, then verify Fallout 4’s base files through your platform. Manually delete any leftover folders before reinstalling. This prevents ghost files from poisoning a fresh setup.
Reinstall Fallout London with no additional mods and launch it once successfully before changing anything. Think of this like testing a clean build before min-maxing gear.
Yes, it’s time-consuming. But it’s still faster than chasing RNG-level bugs caused by a corrupted foundation.
Final Stability Check Before You Commit to a Full Playthrough
Play for at least 30 minutes without saving and loading repeatedly. Enter multiple interiors, trigger combat, and let ambient scripts run. If the game holds, your install is solid.
Once Fallout London is stable, treat it like a standalone RPG, not a modded sandbox. Respect its systems, pace your changes, and it will reward you with one of the most ambitious Fallout experiences ever released.
London isn’t forgiving, but when it works, it absolutely sings.