Fallout: New Vegas runs on an older version of the Gamebryo engine, which was designed for dual-core processors and very limited RAM. By default, the game uses a small memory “bucket” for cell loading and face data. Modifying the FalloutNV.ini allows us to expand these buffers and enable “Multi-Threaded” AI and rendering, which significantly reduces the “Cell Loading Stutter” experienced when traveling between locations like Goodsprings and the New Vegas Strip.
Hardware Compatibility & Expectations
- Modern Systems: Even with 32GB of RAM, New Vegas can only “see” up to 4GB (with the patch). These tweaks ensure the game uses that 4GB as efficiently as possible.
- NVSE/New Vegas Heap Replacer: This guide assumes you are using these essential tools. The
.initweaks act as the final bridge to ensure the engine doesn’t fight against these mods. - Stutter Fix: These changes are specifically designed to fix the “Micro-stutter” caused by the engine’s internal frame-timing limits.
Backup and Preparation
Ensure the game launcher is closed before editing, as it can reset your .ini values to default.
- Exit Fallout: New Vegas.
- Navigate to your Documents folder.
- Right-click FalloutNV.ini, select Copy, and save a backup copy on your desktop.
- Open the original file with Notepad++.
File Location
The core configuration file is located in the user’s My Games directory: C:\Users\%USERNAME%\Documents\My Games\FalloutNV\FalloutNV.ini
Best Config Settings
Search for the following sections and update the values. These settings focus on “Threaded” operations and memory buffer expansion:
[General]
bUseThreadedAI=1
iNumINIThreads=2
biPreloadPackageLimit=134217728
bfStaticMenuBackground=1
[BackgroundLoad]
bBackgroundCellLoads=1
bBackgroundPathing=1
bUseMultiThreadedFaceGen=1
bUseMultiThreadedSceneGraph=1
[Display]
iPresentInterval=1
fLightLODDefaultStartFade=10240.0
Key Parameters Explained
| Parameter | Recommended Value | Impact |
| bUseThreadedAI | 1 | Enables the engine to process AI on a second CPU core; fixes the “Multi-core crash.” |
| iNumINIThreads | 2 | Forces the engine to use more than one thread to read configuration data. |
| iPreloadPackageLimit | 134217728 | Increases the “Preload” buffer to 128MB (from 25MB), reducing loading stutters. |
| bBackgroundCellLoads | 1 | Allows the game to load the next map area in the background while you are walking. |
In-Game Settings vs. Config
To maintain stability alongside these memory tweaks:
- Water Refractions/Reflections: Set to Off or Low. The engine’s water shaders are a major cause of memory-related crashes in areas like Lake Mead.
- Shadow Quality: Set to Medium. “High” shadows in FNV use an inefficient rendering pass that taxes the CPU’s main thread.
- V-Sync: It is recommended to keep
iPresentInterval=1in the config but use NVTf (New Vegas Tick Fix) to handle high refresh rates, rather than disabling V-Sync entirely.
Troubleshooting & Common Fixes
- The “3-Frame Stutter”: If the game feels “choppy” despite high FPS, ensure
bHookCriticalSections=1is set in your New Vegas Stutter Remover config (if using that older mod) or stick to New Vegas Tick Fix. - Crashing on Cell Travel: If the game crashes when moving between areas, your
iPreloadPackageLimitmight be too high for your specific mod list. Try reducing it to 67108864 (64MB). - Read-Only Mode: To prevent the launcher from resetting your
bUseThreadedAIfix, right-click FalloutNV.ini, select Properties, and check Read-only.
Frequently Asked Questions (FAQ)
Is the “4GB Patch” mandatory?
Yes. No amount of .ini editing can replace the 4GB Patch. Without it, the engine will crash as soon as it hits 2GB of usage, regardless of your config.
Why set iNumINIThreads to 2 and not higher?
The Gamebryo engine becomes increasingly unstable with more than 2 threads assigned to core tasks. Setting this to 4 or 8 will almost certainly cause immediate crashes.
Does this help with the “New Vegas Strip” lag?
Yes. By increasing the preload limits and enabling background cell loading, the game can handle the high density of NPCs and lights on the Strip more smoothly.
Conclusion and Expected Results
By manually refining your FalloutNV.ini, you are modernizing the way New Vegas interacts with your hardware. You can expect vastly reduced “Loading Screen” hangs, smoother transitions between wasteland cells, and fewer “Out of Memory” crashes during long play sessions.