FNV General Mod Use Advice
- 1 Overview
- 2 Terminology
- 3 First Timer Advice
- 3.1 Bandwidth Considerations
- 3.2 Correcting broken mod links
- 3.3 Do NOT accept the default install location
- 3.4 Maximizing use of memory
- 3.5 Adding third-party tools to mod managers
- 3.6 First Rule - Install one mod at a time
- 3.7 Second Rule - Make it playable first
- 3.8 Third Rule - The Rule of One
- 3.9 Fourth Rule - Reloading save game files
- 3.10 Essentials for Getting Started
- 3.11 Should you Clean the game master files
- 3.12 Vanilla Load Order
- 3.13 Game INI files
- 3.14 Restoring to Vanilla
- 4 Mod Managers
- 5 Smaller Plugin Cap
- 6 DLC expansions
- 7 Script Extenders
- 8 Towards Game Stability
- 9 Body Replacement Basics
- 10 Mod recommendations
- 11 Factions and Reputation
- 12 Clean Saves
- 13 Merge Patch File
- 14 Improved Texture Considerations
- 15 LOD or VWD Texture Packs
- 16 Testing
- 17 Common Game Problems
- 18 Missing Masters
- 19 Mod Conflict Troubleshooting
- 20 Post processing shaders
- 21 HUD-UI-Menu Issues
- 22 How to ask for help in the forums
- 23 Want to create your own mod?
- 24 References
If you aren't aware as yet, it's pretty much universally recognized that the default install location used by Steam (to the "C:\Program Files" folder tree) is a problem area due to the anti-malware security measures taken with it since the release of Windows Vista. Many unexplained problems are directly related to this location. Save yourself a lot of potential frustration and grief in the future by taking the time to move your Steam game (and really all games that did not come already installed) to a different location. The wiki article Installing Games on Windows Vista+ covers the reasons and procedure for moving Steam games.
If you are new to using "mods" with games on the PC, or just want some tips on how to quickly get using mods with "Fallout New Vegas" (or FNV as it is known) with the least amount of hassle, this is the place to start. This article broadly covers things you should know, and points you to more in-depth articles on particular subjects.
Just to clarify: "Fallout New Vegas" (2010) still uses the same "Gamebryo Engine" as "The Elder Scrolls III: Morrowind" (2002), "The Elder Scrolls IV: Oblivion" (2006), and "Fallout 3" (2008).- Wikipedia.
It is important to keep the distinctions between engines in mind when attempting to transfer "lessons learned" or tools from one game to another. The games based upon the Gamebryo engine tended to build upon prior knowledge from the older games, while games built upon the "Creation" engine tended to "go their own way" in important aspects.
The game has 7 "official patches" from the game publisher which fix problems discovered or corrected since it's initial release. (Do not confuse these with "unofficial patches" released as "mods" by the game community.) Everyone assumes you have a full "officially patched" version by this date. (This is sometimes called your "patch level".) If you purchased any version of the game released after 2011 (e.g. "Ultimate", "Game of the Year", etc.), then you are fully patched to version 22.214.171.1245.
- Determining your Official Patch level: Start the game, then in the Main Menu, select "Settings | Display" and look in the lower left corner. You may need to place your cursor over the "Vault Boy/Girl" head icon (if any) before it will display the version information.
A "mod" is a package (archive) of related files that make some change to the vanilla game (including official "Down Loadable Content" (DLC) expansions as delivered by the publisher). The "file extension", the characters after the last period (".") reading left to right in the filename, indicate which program was used to create the archive package. (You can use the site File-Extensions.org to look up those you are not familiar with.) The ones most commonly used for mods on the "Nexus Mods" site are ".7z" (created by the 7Zip program), and ".rar" (created by the WinRAR program. There are a number of alternative tools which can unpack those types of archive files, but each archive tool has mutiple "formats" in which it can compress a file. Some of these may be "proprietary" and exclusive to a particular program, while most are common among many programs. 7Zip is the most commonly used program as it can unpack the most common, non-proprietary ".rar" formats as well as ".zip" files (a predecessor format, now natively supported by Windows).
Within a "mod" package are a number of "asset files" which add to or replace the existing vanilla assets (meshes, textures, sounds, animations, XML files, etc.), and one or more "plugin files" that tell the game about the existence and use of the new assets and where they are placed in the game. The "plugin" files are the only ones that appear in the "load order" (see below). "Plugin" files have one of two possible file extensions: ESM and ESP. There is generally only one ESM file, but there may be any number of ESP files (including none). The ESM files are loaded first, and are considered "masters" to the ESP files that depend upon them. You should find all of your ESM files (vanilla, DLC, and mod) at the top of your "load order".
The archive package may also include some documentation file(s). These could have any extension typical of a "word processing" or "text" program such as ".txt", ".doc", ".rtf" or ".pdf". Some mod creators have adopted the practice of placing such into a "docs" folder under the game "Data" folder (e.g. "Data\docs") when the archive is unpacked. Others just leave them in the same folder as their other "assets" when "installed", depending upon the folder structure of the archive. Sometimes that means they are just placed in the "Data" folder. Examining the folder structure of the package "contents" with the appropriate archive tool will tell you where they will be located.
"Modding" refers to both the process of playing the game with mods installed, and to creating such mods. More properly we should distinguish between "mod users" and "mod creators", but most people rely upon the context in which the term is used rather than explicitly stating which is meant.
There are two important "orders" to which you must learn and understand the distinction because they are going to come up over and over again: "install order" and "load order".
- "Install Order" refers to the sequence in which mods are "installed" into the game "Data" folder. Later installed mods that have a file with the same folder path and filename will need to overwrite previously installed files in the same location. So the last installed "wins", as there can only be one file with a given name in a given folder. With mod managers, this can become less obvious than it would appear at first glance. Some mod managers allow you to "move" around the sequence of installed mods, and then resolve the new "winners". This is possible only if they have a copy of the "vanilla" files to restore from when needed. Read the documentation of your chosen mod manager carefully to see how (if at all) this is implemented. The "vanilla" files are typically all stored in ".BSA" extension archive files, but some "loose" files (not in a ".BSA" file but visible as individual files) may exist in folders under the "Data" folder. Therefor, best practice is to make a backup copy of the entire "Data" folder somewhere outside of the game folder. Then you will always have the original files and can compare the contents to see what has changed.
- For a solid guide (regardless of which Bethesda game) to organizing the sequence of mod installation, see A General Order for Installing Mods (Oblivion).
- "Load Order" refers to the sequence in which the game loads ".ESM" and ".ESP" (collectively called "plugin" files) when the game is launched. These two files in turn take care of loading the "assets" (sound, meshes, textures, etc.) from the mod into the game. Most of your problems with running mods will come down to problems with your "load order" because two (or more) mods are trying to modify the same "data record" in the vanilla files (both the original game and the DLC expansions. Similarly to the situation with "install order", the last loaded plugin "wins" out over all previous plugins that conflict by default, in an all or nothing manner. IF the other plugins make changes to other records that the "winner" doesn't touch, they still lose out and those changes do not take effect. This is known as "the rule of one", and is why "proper sorting" of your "load order" is so important. Those files that are "lower" (relative to the "Fallout.ESM" files; higher numbered) in your "load order" will be the "winners" of conflicts.
- Fortunately there is a way to get around this "all or nothing" winner in "load order" by using a "merged patch" file that resolves conflicts on a "last modified record field" winner basis. This enables multiple mods to change a record as long as they are the only one changing a particular field within that record. In the case of record field conflicts, the same "rule of one" applies. More on this topic later in a linked article.
For the user, a mod package essentially has three "states": "downloaded", "installed", and "activated".
- Downloaded: the mod package has been copied from a server on the Internet (i.e. The Nexus Mods website) to a location on your computer.
- Installed: the "downloaded" mod archive package has been "unpacked" and the package/archive contents "installed" into the same or a different folder (i.e. a "Mods" or the game "Data" folder) on your computer.
- Activated (aka "Enabled"): The game has been instructed to load the plugin as part of it's "load order". For FNV, this means it has had the "checkbox" enabled in the "Data" option of the first game menu. Mod Managers take care of this for you when the plugin is enabled/activated in their interface.
- For some mod managers (i.e. "WB/WF" and "FOMM"; see under Mod Managers below), "installation" means the mod files have been copied into the game "Data" folder or sub-folders. This "install order" is independent of the "load order", and is considered the "traditional" form of installation. For others (i.e. "MO" and "NMM"), the "mod" or "install info" folder is separate from the game folders, and only "links" to the actual files are placed in the game "Data" folders, and that only when the mod plugins are "activated". In these mod managers, the "install order" initially equals the "load order", and changes when the "load order" of the plugins is re-sorted.
- However, mods often include the previously mentioned "asset files" that are placed in sub-folders under "Data", which are used instead of vanilla versions of those files. Merely "deactivating" a mod plugin does not remove such added or restore replaced files, so the mod must be either uninstalled or it's unused/unwanted "asset" files manually removed from the "Data" folder path so the vanilla versions will be used. The game engine still loads every file it finds in the "Data" folder into memory and checks it's references for "master files", regardless of it's "active" state. This is why they count against your "plugin cap" (described later). If it fails to find any of such referenced masters, it causes a "missing master" CTD without warning. This is the primary reason you can't use a patch file designed for mods you do not have installed, as they will always be missing the "master" plugin of the absent mod and "mysteriously" crash.
Most mod packages are "simple" in structure and can be installed with any mod manager. They just need to have all their contents installed into the correct folders under the game "Data" folder, which is what all mod managers assume. They normally have any sub-folders already included in the archive. You should always "overwrite" any existing files they encounter with the same name. (This is why "install order" is significant. Last installed is the last to overwrite, and the only version of that filename to exist.) Note that some mods, such as Script Extender plugins and tools like FNVEdit, need to be placed elsewhere than under the "Data" folder, which is why they should not be installed with a mod manager.
Some mod packages are more complex, with optional files that need to be copied when other specific mod files are also found to already have been installed. The mod may have specific instructions in the provided documentation (aka "ReadMe.txt" files), or on the download page, or under "optional files" on the mod's "Files" page. But some have "scripts" or "wizards" which the manager will automatically execute (if it recognizes them) that will detect the files of the other mods they are designed to work with, and automatically install the correct components or offer you options to choose among. (This is especially true of FOMM mods.) However, these "scripts" are not "universal" in that they do not work will all mod managers. Such scripted mods will normally specify on the download page which mod manager they require to process their "wizard" (i.e. "install with FOMM").
It is not absolutely required that you use the mod manager a script is designed for, if you don't care about actually executing the script and know how to interpret it. The script itself is a text file with basic "if ... then ... else" style instructions you can follow manually or rewrite into a different scripting language if you have the skill set. But most will find it easier to simply use the manager the script is written for. However, mod managers generally only can "manage" mods they themselves install. They won't "know" about mods installed by other managers unless they happen to place them where expected. ("Management" in this case typically refers to "installing", "uninstalling", and "restoring" the previously existing mod components cleanly, as opposed to "activation". Depending upon how your manager works, it may be relatively easy to get it to "activate/deactivate" plugins from sources it did not manage.) So it normally is beneficial to plan ahead and use the mod manager suited to the majority of mods you plan to install.
There is an important consideration with "complex" structured mod packages (i.e. "Fallout Character Overhaul (FCO)" being a popular example of this). YOU need to know which "optional" components or "compatibility patches" are needed. (Often others than the original mod author will produce "compatibility patches" for additional mods. Be sure to seek them out by searching on both the "full name" and "nickname" of the primary mod, such as "Fallout Character Overhaul" and "FCO", as well as under the "optional files" of the secondary mod, like one for "Hair styles".) Installing package component files that are not needed can prevent the game from starting. (See the entry on Missing Masters below.) Do not install every optional file without a reason: pick and choose only those you know are needed. It is much easier to add a missing optional file later than it is to figure out which are not needed and are preventing the game from loading. Seek assistance on the Forums when in doubt.
"Post Processing" is used in the video and film industry to improve the quality of images once they have been processed. In real-time 3D games, they are applied to the rendered effects to supplement the game engine.
According to Wikipedia:
Instead of rendering 3D objects directly to the display, the scene is first rendered to a buffer in the memory of the video card. Pixel shaders and optionally Vertex shaders are then used to apply post-processing filters to the image buffer before displaying it to the screen. Some post-processing effects also require multiple-passes, gamma inputs, vertex manipulation and depth buffer access. Post-processing allows effects to be used that require awareness of the entire image (since normally each 3D object is rendered in isolation).
There is a whole host of effects that can be produced. See the sub-topic Post processing shaders if this interests you.
First Timer Advice
Bandwidth refers to how much data (measured in bits) you can move between point A and point B in a given period of time. All Internet communications consume bandwidth. In the most general terms, the faster your connection speed ("bits per second" or "Mega bps" or "Giga bps"), the more bandwidth you have at any given moment. However, the amount of data you have to move has to be divided into "packets" that do not exceed your bandwidth. So, the more data you have to move over a given bandwidth, the longer it will take. This is called your "throughput data rate". For this reason you generally want to minimize the amount of data that has to use bandwidth to increase your "throughput data rate". Your "Internet Service Provider" (ISP) typically has a maximum amount of data transfer each month or given period called a "monthly data transfer cap", after which it charges you extra or "throttles down" your available bandwidth to a slower throughput rate.
The Steam Client has to be running in order to play a "Steam" game. As this (in "online mode") consumes bandwidth, if you have a slower connection speed or "low transfer cap" you will want to take steps to minimize how much throughput the Client requires. If this is a concern for you, please read one of the articles:
- Make Steam friendly to low bandwidth connections
- Make Steam friendly to low bandwidth connections/Pictorial
However, if you previously setup the "Steam Client" (under "Steam | Settings") by disabling (unchecking) the "Don't save account credentials on this computer" option at the bottom of the page so it will save your account data locally, then you can start the Client in "offline mode" and play the game even without an Internet connection after your very first session. You simply won't have any of the Client functionality like "Community" or tracking of the number of hours you have played or achievements reached until the next time you play in "online mode", whereupon it will update that information.
In either "offline" or "online" modes, you can close the Client interface window but must leave the Steam icon in the "system tray" on the end of the Windows taskbar (the one on the edge of your monitor with the "Start" button).
Link formats on web sites often change over time. Here's how to translate old ones into the current format (at least on the Nexus, though the general approach should work for other sites):
Suppose you have an old link to "Breezes New Vegas Males". (The old format doesn't actually matter; just the "mod id number".)
- Find any current active mod page on the site. Doesn't matter which game (with the appropriate adjustments), but simplest is a mod from the game you are playing. For example: FNV's mod "Type3 Body and Armor replacer" is currently found on Nexus at:
- Copy out everything up to but not including the "Mod ID number" (i.e. excluding "34825" in this example). That is the "new link prefix" currently in use (e.g. "https://www.nexusmods.com/newvegas/mods/").
- Now take the "Mod ID number" from the old, no longer functional link (which is the only part that uniquely IDs that mod within that game category) and add it to the end of the "new link prefix".
- That "rebuilt" link can now be pasted into your browser as a destination URL.
So, convert the broken "Breezes" link format (e.g. Mod ID "35451") to:
If the rebuilt link fails to work, it is possible the mod no longer exists; but try searching on the keyword parts of the mod name first. However, sometimes a mod has been renamed so then you have to resort to searching through the appropriate Nexus "Category" instead.
Now you can fix any broken link yourself.
Do NOT accept the default install location
If you have already installed Steam to "C:\Program Files" or "C:\Program Files(x86)", read the Installing Games on Windows Vista+ article which has a link to the official Steam guide to moving already installed Steam games. (Yes, you will need to "re-install" them so the Windows registry entries are correct, but you can still use your "saved game files".) As painful as this may sound, this one step will solve most "strange" problems not related to a mod conflict, and you will no longer need to run your games as an "administrator". It is never easier to do than now, and you don't need to move all your Steam games at once. DO NOT try to move or install to your "User\Documents" folder as that is also a "system protected" folder that does not allow "executables" to run (because it is a folder which every user is known to have "write" access to and "malware" liked to use).
Once you tell the "Steam Library" installer for the game where to start placing it's files, it (assuming Steam; GOG is very similar but uses it's own "GOG" names) will then create (or use if already existing) either a "Steam" or "SteamLibrary" "upper-level" folder under that location (only one location per "drive letter"), and then under that the ".\steamapps\common\Fallout New Vegas" folders. This "Fallout New Vegas" folder is referred to as "the game root folder" and is where you will find the EXEs to launch the game, and in it the "Data" folder which has all the plugins and sub-folders (such as "Meshes" and "Textures") used by the game.
So, the default location is "C:\Program Files(x86)\Steam\steamapps\common\Fallout New Vegas", but you don't want this because of the many headaches it causes. If you were install from Steam to "C:\", it would then create "C:\Steam\steamapps\common\Fallout New Vegas" instead. This is not recommended because a new folder inherits it's "permissions" from it's parent, which in this instance is the "C:\" drive root. (See the "Installing Games on Windows Vista+" article referenced earlier.) Instead, create a new "top level" folder such as "C:\Games", setup the permissions on that new folder as desired for all subsequent games, and install to that folder. If you installed this game to "D:\Games" after installing others to "C:" drive, it would probably become "D:\Games\SteamLibrary\steamapps\common\Fallout New Vegas" because "SteamLibrary" is used whenever a "Steam" folder previously exists.
Remember: "Steam" (or "GOG") is a separate set of programs from the game. Each has it's own Client programs for managing the distribution of various games, and the games have already made their accommodations to work within that framework, but otherwise are independent of "Steam/GOG".
Maximizing use of memory
You need to be aware that FNV is a 32-bit game. As such, it can only address up to 2GB of RAM by default, even on a 64-bit system. A detailed explanation of the reasons behind this and some solutions around it if you have more than 3GB of system RAM can be found in the wiki article 2-4GB game memory limits and solutions. But for FNV Steam users (and now for GOG users as well with v1.4 or later) there is a tool called FNV 4GB Patcher that easily solves the problem for both the game and GECK. (Older versions of the tool are deprecated. The latest version (v1.4+) now supports the GOG version for auto loading NVSE, and the "NVSE_CONFIG.INI" file does not work for the GOG version without RoyBatty's patch. Revert to the backup copy created if you did run an older version.) Run the patcher once (as "Local Administrator" if necessary) and thereafter just use the default game FalloutNV.EXE or FalloutNVLauncher.EXE as a normal user. The patched game automatically detects and launches NVSE.
How can you tell if the 4GB Patch is working?
- Look for the "Data\NVSE\NVSE_CONFIG.INI" file which for GOG users will otherwise will not get created without the "nvse_steam_loader". Check the "nvse_steam_loader.log" file (in the game root folder with the FalloutNV.EXE file) for errors.
- The JIP LN NVSE Plugin has a function which can be run from the console: "GetIsLAA" (not case sensitive).
- Possible return codes:
- 0=patch is not applied
- 1=patch was applied to the executable, but extra memory is not being allocated
- 2=successfully allocated extra memory from the patch and is fully working.
- If "GetIsLAA" is returning code "1", try running the game from a "Local Administrator" account. If that is succesfull, you need to move the game install location out of the "C:\Program Files" folder tree, or correct the "permissions" on it's folder if you have moved it, as you are going to have other problems down the road. Please see the wiki "[url=http://wiki.tesnexus.com/index.php/Installing_Games_on_Windows_Vista%2B]Installing Games on Windows Vista+[/url]" article for details.
- Alternatively: if the Windows "Task Manager" indicates the "FalloutNV.exe" program has more than 2GB (2,000,000KB) of "Memory (Private Working Set)", then the 4GB Patcher is in effect. However, to the contrary: less does not mean it is not working. The game simply hasn't needed that much memory as yet.
For those who still have problems trying to run the game directly from the "Steam Library", check out the mod SteamLauncher for NVSE and FNV4GB and ModOrganizer. Note that the "SteamLauncher" runs the "FalloutNVLauncher.exe" program and WILL replace your "Users" folder INI files from the "Fallout_default.INI" file in the "game root folder" each time. This mod also is designed to work with the original "Loader" version of FNV4GB (4GB Fallout New Vegas Updated) rather than the "Patcher" version. See the Game INI files section for more details.
Those anticipating or encountering problems with textures consuming too much video memory should read the S.T.E.P. ENBoost page. This a separate component of the ENB "post-processor" which increases available video memory by up to 4GB without the graphic effects of the main ENB tool.
Adding third-party tools to mod managers
Most mod managers have a method of adding "third-party" tools like NVSE, FNVEdit, and FNV4GB to their launch options. This is not required for FNV4GB, which normally is run from the desktop shortcut instead of inside a manager. However, as some NMM users have had trouble discovering about it, here are specific instructions on how to do so. Supposedly the equivalent will be added to the "launch list" in the top left corner where the FNV and NVSE launchers are currently located in the "next release" after April 2015. The instructions are presented here in a generalized form as a guide to adding other "third-party" tools to the NMM launcher:
- Install the tool according to instructions, paying particular note as to the correct location.
- In NMM open "Settings" (looks like a pair of gears):
- Open the "Fallout: New Vegas" tab.
- Locate "Custom Launch Command".
- Enter the explicit path to your tool "exe" file in the "Command:" field
- (Ex.: "C:\Games\SteamLibrary\steamapps\common\Fallout New Vegas\fnv4gb.exe" without the quotes.)
- Click the "OK" button.
- Open the "drop list" window for the "Launch" button in NMM.
- Choose "Launch Custom Fallout: New Vegas".
First Rule - Install one mod at a time
First rule of playing with mods is: install and TEST one mod at a time. This is the only way you are going to know if you have made a mistake in installation or if the mod is going to conflict with others before getting many hours into the game before a fatal problem shows itself and you have to start over.
In turn that means you need to prioritize what is most important to you. You don't want something that is "nice to have" dictating that you can't use something you consider essential. This takes time, but if you don't force this discipline upon yourself, you are going to spend a lot of frustration and even more time ripping your game apart trying to figure out why it crashes or won't work right. There are no shortcuts. A guide by somebody else is not guaranteed to work on your system because they don't have the exact same setup as you; nor do they necessarily consider the same things as "important".
Second Rule - Make it playable first
Second rule is: "pretty" does not beat out "playable". Improved graphics come at a cost, usually in terms of "frames per second" (FPS). Add your graphics overhauls after you have a stable game built that runs fast enough to keep you happy. Nobody has a system new enough or fast enough to play with every mod they might want. The game engine is too old to accommodate that. It was written for single processor 32-bit systems. All your multi-core processors are going to be ignored. So there WILL be limits.
Third Rule - The Rule of One
Third rule is called "The Rule of One". What this means is that when two plugins attempt to modify the same record in the vanilla game, only the last plugin loaded (determined by the "load order") "wins"; totally and completely. (This is described in the Terminology section, under "Load Order". This rule also applies to "Install Order".) The way around this is to use a "bashed" or "merged" patch file, which enables "record level" conflict resolution among all the plugins instead of the default "one plugin winner takes all" approach. The subject of how to create either a "bashed" or "merged" patch file is covered in the S.T.E.P. Project "Fear and Loathing" guide linked under the sub-topic Merge Patch File below. You don't really need either one until you have settled on your basic mod lineup, which should be before approaching the plugin limit described elsewhere in this document.
Fourth Rule - Reloading save game files
The rule is simple: ALWAYS "quit to the desktop" before reloading a "save game" file of any nature during a game session: quick, auto, checkpoint, manual, triggered, whatever. (This rule applies to all Bethesda games thru the latest. It is the only guaranteed way to avoid corrupting save games.)
By this is meant "closing the game session" (where starting the game and then exiting to the desktop is considered "one game session") between opening one save and then another (even the same save file). As in:
- Start the game up. (Start of session #1.)
- Load any save and play.
- Quit the game back to the desktop (not just the "main menu"). (End of session #1.)
- Start the game up again. (Start of session #2.)
- Load a save game (either the same one or a different one), and play.
While this practice is annoying, it is necessary because there is now a difference in the state of the game "in memory" and "as saved". At the beginning of a game session it loads a bunch of background material about your location's "worldspace" (or "interior cell") and "other stuff" about the state of the environment and current quest line(s). Then as you interact with the game, you can cause changes to that "environment" in memory that are not included in your subsequent "save game" file. Unless you quit to the desktop, the "in memory" state of the game persists with only portions getting overwritten from the save file.
As an example, say you've been blown up by a mine, reload from a quick/auto save ten yards away from where you were blown up, and then go in search of that mine ... only to find it is no longer there. That's because "in memory" that mine has already blown up and no longer exists. (You can easily test this for yourself.) It was not something that was included in the save. (Saves are primarily about your character and it's status, inventory, and certain "state" variables such as quests; not the entire rendered world. Things that are different than the default game state.) Quitting to the desktop will put the world state back in time to the way it was before you triggered the mine. Now imagine things like scripts and their flags being triggered, then "oops: not triggered", depending on states in memory. Complex corruption of the game thereafter if you don't quit to the desktop so the world "in memory" gets synced/reset to the state at the time of the save.
There's an even simpler way than the "mine trick" to prove that reloading a save from the menu doesn't revert the game back fully: save the game, play a facial expression on a character, reload the save game (without exiting to the desktop), and that expression is still there. Now "exit to the desktop" and start the game again with the same save file. The character's facial expression reverted to it's default.
For similar reasons, completely disable all manner of automatic saving in the game options. See the paragraph about "auto-saves" in the Essentials for Getting Started section.
Essentials for Getting Started
There is an excellent set of advice for those new to modding: see the "Fallout: New Vegas Mod Troubleshooting" sub-forum Fallout New Vegas Beginners Guide to modding thread ("sticky" at the top) which covers the essential tools you will need, such as LOOT for sorting your "load order" (LO). Consider this article a supplement to that thread.
Like most automated tools, LOOT is not 100% accurate; yet it is infinitely better at determining a correct load order for a large number of mods than anything other than manually examining each mod in an editor like FNVEdit (a generic tool called 'xEdit' which is renamed for working with specific games) and building such an order by hand (each time you add or remove a mod). (There is the Tome of xEdit current online manual for all games and the PDF FNVEdit Training Manual specific to both FO3 and FNV.) LOOT works by examining the file header of each plugin and working out all the records each modifies, and determines the relationships between those mods. LOOT's decisions are based in part upon user feedback about known conflicts (in it's "masterlist"). For the beginning mod user, it is essential to resolve most fatal mod conflict problems quickly and easily.
On the other hand, within certain limits as to dependency LOOT doesn't much care as to the order if it does not know about or detect a conflict. Consequently it has been found useful to rearrange some mods (especially recently added ones) by moving them to the top (low numbered position below the ESMs) and see which plugins it sorts them below. From there you can pretty much always move them to a lower (higher numbered) position in the LO without problems. This is helpful when attempting to arrange groups of "contiguously adjacent" plugins to be merged into "merge plugin files" in order to reduce your overall "active" plugin count. (See the Smaller Plugin Cap section.) This also gets you a reasonably stable "sort" sequence even when adding new mods later.
LOOT does provide the "metadata" mechanism that allows you to customize it's sorting to preserve such adjustments as you determine necessary. Read it's documentation to exploit all of it's capabilities.
The "Tale of Two Wastelands (TTW)" site (which has ported Fallout 3 to the FNV game engine enabling you to seamlessly move between both game worlds) has A Guide for NOT using LOOT for those interested in learning how to manually manage their "load order" for themselves; or see the wiki article "Load order and you" for another such approach to FNV.
Also recommended is the S.T.E.P. Project "Fear and Loathing" guide for FNV (linked below under the Mod Managers sub-topic). While oriented around using "Mod Organizer" (MO), it can be used with other mod managers as well, with appropriate changes for their peculiarities.
Your "save game" files are stored under the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV\Saves" folder. They have the extension ".fos", and if you have NVSE installed it also saves the same filename with the extension of ".nvse". You can have up to 999 saved game "*.fos" files displayed in the "load game" menu. (More may exist, but only the first 999, based on their date of creation, will be displayed.) They are named either "autosave <number>" by the game engine, or "<CharacterName> - Save <number>" for manual saves. Note however, that the number included in the filename is a simple increment to the name portion. If you are getting close to the 999 file display limit, you can delete older saves and the game will let you keep saving files with further incremental numbers beyond 999.
The Steam version of the game (GOG Galaxy v1.2 has a similar feature) automatically has "Cloud Sync" of save game files enabled.
You can check a specific game's sync status by seeing the Steam Library <game> "Properties" (right click), and then under the "Updates" tab there's a "Steam Cloud" section that indicates the bytes stored in Steam Cloud Sync. That is where you can disable it. See the Steam Support article Steam Cloud for more details. Note that the cloud is not automatically updated with your last "current save". It apparently only does so periodically. People have been caught with no saves in the cloud simply because they assumed the sync was working. Also note that if you delete a "local" save game file (to make room for newer ones) from your "Users" folder, "Cloud Sync" will automatically restore it if enabled and in "online mode", making your latest saves unavailable because you have exceeded the display limit of 999 files. (The files are still there; you just can't scroll to them in the game menu until you get under the limit. It counts from the oldest date.)
"Autosaves" are dangerous because they are seldom able to tell when the game is in the middle of doing something else critical. Also, they are by default limited to only so many (configurable up to 10) before they overwrite previous versions of the same filename. This may eventually lead to problems with corrupted files. (This has been demonstrated time and again with the game's builtin mechanism.)
There are mods designed to supplement or replace the builtin game save file mechanism. These follow the same principle but use slightly different conventions for the filename portion.
Most importantly, completely disable all manner of autosaves in the game options. The CASM with MCM (recommended) and CASM_NV mods attempt to provide more control over such situations. Simple Saves provides timed interval "full saves" without all the features of CASM, but only keeps 5 versions before it starts overwriting older files after the 5th save. They are all better than the built-in mechanism, but don't rely upon any auto-save exclusively. Manual "full saves" after waiting about four-five seconds with nothing happening are still safest. Also, you can use Clean Quick Saves to create a new "quick save" file every time, which is safer than overwriting an existing older version file. You will need to periodically clean old ones out (they count against the 999 save file limit). And always remember the Fourth Rule when loading any save.
Regardless of behavior experienced in other games, the mod author IStewieAI has examined the code and reports that all FNV "save game" files (Manual, Auto, and Quick) are created exactly the same way. The only difference is that saves with "autosave" at the start of their name can be created while in a (non-VATS) menu.
Should you Clean the game master files
The internet is full of mixed advice, and it varies over time. We know more now than back in 2010. The current argument is that it should be the responsibility of the mod author to "clean" a plugin, as they presumably know what needs to be there for their mod to work correctly. By the time of FO3 and FNV, the "dirty edits" and ITMs/UDRs in mods were well known to be an issue. Any present in the Fallout games and DLCs presumably are either necessary or harmless. So, as a general rule the advice is to leave the vanilla and DLC master files for both games alone unless you have very specific reasons for doing otherwise. BOSS and LOOT numbers are based on user reports of what they found. The mere fact that ITM/UDR records exist is no longer a reason to clean them out. Guidance varies by game and edition of the xEdit tool.
The "Tales of Two Wastelands" (TTW) team has had to look into the matter in order to get FO3 to run on the FNV game engine. Their FAQ page has the following:
» I read everywhere that we should clean Skyrim core files (.esm & .esp), so by association I decided to do the same to my Fallout games, did I do the right thing? «I am sorry, but you did the wrong thing. Fallout is not Skyrim, and so not everything that works for one also works for the other, they don't even use the same game engine. If you clean the Fallout 3 and/or Fallout New Vegas and/or their DLC's you will break your game since you are removing things that are necessary things that fix things in other things and make things run properly.
(See the TES5Edit Mod Cleaning Tutorial article for details about cleaning your own mods, and the associated terminology.)
Vanilla Load Order
In general, make sure all your ESM files are loaded first, with the game ESM (FalloutNV.ESM) as the very first file and those of the DLC next in the order they were released for the PC.
- FalloutNV.ESM - (Oct 2010)
- DeadMoney - (Feb 2011)
- HonestHearts - (May 2011)
- OldWorldBlues - (Jul 2011)
- LonesomeRoad - (Sep 2011)
- GunRunnersArsenal - (Sep 2011)
and then the "pre-order packs" of exclusive equipment to make the earlier stages of the game easier; later combined and released as the "Courier's Stash" pack (Sep 2011). As these "inject" records into the vanilla game, their load order is not important other than being up top with the other ESM files:
These are all included in the "Ultimate Edition" of FNV.
Mod EMS files should follow.
Note in particular the "First Rule" to install one mod at a time and test it thoroughly before the next mod. This, and that you install your Steam games to some folder OTHER than the default of "C:\Program Files", are pretty much universal for a solid, stable game.
Game INI files
The game has three INI files: the general "Fallout_default.INI" in the "game root folder" ("<steam install path>\steamapps\common\Fallout New Vegas") which only gets used to recreate the other two when they are not found; and the two specific to you in "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder ("Fallout.INI" and "FalloutPrefs.INI"). The two in the "Users" folder get created when you first run through the vanilla "FalloutNVLauncher.exe", which is necessary the first time in order for the engine to determine your hardware configuration. This information gets preserved in the "FalloutPrefs.INI" once you exit from the "Main Menu".
First make a backup of the original 'Fallout_default.INI' and 'FalloutPrefs.INI' files as a precaution. With these in a safe place as an appropriate backup, it is better to edit the "default" file as well the others with tweaks you know you intend to keep, so it will rebuild the "User" files as you expect when necessary. When experimenting with INI changes, only the "Users" files should be changed as they are what the game actually uses. Once happy with the chosen tweak, remember to change it in all three files: otherwise you tend to lose track of which you actually changed if you have to "verify files" or re-install later.
If you launch FNV from the Steam "Library" panel, it will replace your "Users" folder INI files with the "Fallout_default.INI" file from the "game root folder". It may also first set the "default" INI file to be "Read Only"; as might Windows if it is under the "C:\Program Files" folder tree. This replacement does not happen if you launch the game in "offline mode" (see the second paragraph under Bandwidth Considerations) from a desktop link and have moved the game out of the "Program Files" tree as described in the wiki Installing Games on Windows Vista+ article.
Where there are the same settings in more than one INI file, then you want each of them with those settings to be the same (after you have created a backup copy of the original "vanilla" version). It's not clear which INI file the game engine reads from in all instances, but there is evidence that when there are differences between the three ... "strange results occur"; enough to make it a standard practice (with the precautions indicated). This is usually expressed as "make the same change to all three INI files".
Restoring to Vanilla
It is often useful to have a copy of the original, unmodified game for testing purposes with a saved game just after you have created a basic character, or if a mod conflict forces you to "start over".
In addition, if something unexpected happens that forces you to reinstall the game, having a backup means you can reinstall (even to a "new" location) and then copy everything from the backup folder into the new game folder and pickup from where you left off.
Sometimes, if you didn't plan ahead for this, you want to restore the game to the original "vanilla" state, for instance to restore an original file. The following "verify files" procedure will NOT remove any mod plugins or asset files it finds in the game "Data" folder, nor any files in the "Users" folder, but will restore any files in the game root folder with the same name as vanilla ones that do not match the originals on the Steam server. This can break a mod that intentionally replaced a vanilla file, so it is best to re-install mods after you "verify" (or copy them from a backup).
- If you made any changes to any of the game INI files, remember to change it in all three files. (See the Game INI files section.) Otherwise you tend to lose track of which you actually changed if you have to "verify files" or re-install.
- For Steam versions, to see a visual "image guide" to the same "verify files" process presented below, click here.
- Start the "Steam Client",
- Navigate to the "Library" tab,
- Right-click on "Fallout: New Vegas" in your list of purchased games,
- Select "Properties",
- Then in the "Properties" window, Select the "Local Files" tab.
- Click on "Verify Integrity of Game Cache".
- For GOG versions installed from their Galaxy service, it's basically the same as with Steam. Look under "More | Manage Installation | Verify/Repair".
- If you installed manually from the GOG "Offline Backup Game Installer" location, then you can completely ignore everything that refers to the "verify local files" or "Steam Client" as you don't have anything equivalent. Just "reinstall" from the download files as normal.
- "Verifying" files will not affect your "saved game files".
- Rename both the INI files in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder, and let the game rebuild them by launching the "vanilla" launcher "FalloutNVLauncher.exe", configuring the hardware options and exiting when you get to the Main Menu of the game. Rename the INI files to anything you choose. I usually just add to the extension: from "<filename>.ini" to "<filename>.ini.old". The purpose is to be able to examine the old files for things you want to be able to replicate in the new versions of the same file.
- If you used the FNV 4GB Patcher to enable the use of more than 2GB of RAM, you will need to re-run it after verifying files.
To completely uninstall the game in order to get a "clean start" without any mods installed, you should click on "Delete Local Game Content" in the game "Properties" | "Local Files" tab. This will NOT always remove all game related files and folders added by mods. You need to also check for and delete loose files and any remaining folders to finish removing the last remnants. Then reboot the system to flush out any DLL or driver files still running in memory.
Uninstalling is the recommended way to remove the game related registry entries.
- If that doesn't seem to be working for you, you can manually delete the game with the following steps:
- Exit the Steam Client.
- Navigate to "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder.
- Backup any save games you wish to keep to another location. You might want to rename any INI files to something different (i.e. "<filename>.ini" to "<filename>.ini.old") before backing them up. It's better to make manual changes to new versions of the INI files instead of trying to use old ones that may have become corrupted.
- Delete the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder.
- Use Windows "Control Panel | Programs | Uninstall a program" control to uninstall the game.
- Navigate to the "<Steam install path>\steamapps\common" folder and check that the "Fallout New Vegas" folder is empty or deleted. If it isn't, manually delete the "Fallout New Vegas" folder and any contents remaining there.
- You may need to run a registry cleaner app to verify that all the game related registry entries have been removed. Be sure to backup the registry (such as running a Windows restore checkpoint) before letting such a tool remove anything, as a broken registry can turn your system into an inert brick.
- "Restart" your system. If you use the "hibernation" power option then you need to "power cycle" or "cold boot" your system (power off, wait 30 seconds, and then power on again) in order to ensure all DLLs and drivers are removed from memory and the hibernation file.
To reinstall the game once you have deleted the previous version:
- Prepare a "games" folder where you will install the game this time as described in Solution for Steam Games.
- Start the Steam Client.
- Navigate to the "Library" tab,
- Right-click on "Fallout: New Vegas" in your list of purchased games,
- Select "Play Game". Steam should now recognize the game does not exist on your computer and start downloading it again.
- Once the game has been reinstalled, run the "vanilla" launcher "FalloutNVLauncher.exe", configuring the hardware options and exiting when you get to the Main Menu of the game.
- If you used the FNV 4GB Patcher to enable the use of more than 2GB of RAM, you will need to re-run it after re-installing files.
- Now you can restore your backed up "save game" files to the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder.
- However, before loading any previously saved game, start a "new" test game to verify the vanilla game is working correctly. That way you will know that any subsequent problems that immediately show up are embedded in your old save files.
While a "mod manager" is not required it does make organizing your modded game much more manageable if you have more than a dozen files. This is especially true when trying to keep the "install order" (which deals with overwriting files of the same name) separate from the "load order" (which relates to the order in which the game reads in mod plugins). You should only need to learn and use one manager, but some mod archives are formatted for use with a particular manager. You can learn how to "repackage" them to work with your preferred choice, but sometimes it is easier to simply use the manager the mod is formatted to work with. Just remember that mods installed through a different mod manager will not be "known" by your preferred manager. The impact of this varies by the manager. But the "exceptions" are generally easier to keep track of.
There are several choices of mod managers such as:
- Nexus Mod Manager (NMM),
- NMM is still technically in "beta" status but is fully functional. Moreover the primary author of "Mod Organizer" (below) has now been hired full-time by the Nexus site management to redesign & rewrite "NMM" (called "Vortex", currently in available in "beta" release) from scratch. So the current "beta" will not be further improved and NMM is "end-of-line" without official support (community support is provided on GitHub Wiki and Issues page); and the future fate of MO is uncertain at the moment though support continues from the community.
- NMM Manual. Note that NMM MUST be installed to the same drive as the games it is managing.
- NMM Video tutorial by Gopher.
- NMM Video tutorial by GamerPoets.
- NMM Open Beta forum.
- Fallout Mod Manager (FOMM). There are reports this version no longer is compatible with 4GB loader or patch versions of FNV.
- Fallout Mod Manager - Forked a newer "variation" (different version) of FOMM,
- Neither version of FOMM seems to be updated any more but both are usable, stable, and functional, and the other managers are still actively supported. The "Forked" version is recommended between the two, and was created to fix problems in the original.
- Installing a Mod with FOMM
- FOMM and FOMODS for Dummies, Part 1
- FOMM Release Thread. Community support only.
- Mod Organizer (MO),
- MO is part of the S.T.E.P. project and they have their own install guide for FNV called Fear & Loathing in New Vegas (FalloutNV) which walks through the complete process very well. (It's the one I used quite successfully when I started FNV, even though I used WF as my manager instead of MO.)
- Offical Mod Organizer manual
- MO Video tutorial by Gopher.
- STEP Video Series by GamerPoets.
- MO Video tutorial: Mod Organizer #1 - Installation and Initial Setup
- Mod Organizer Support
- Mod Organizer 2 (MO2) 64 bit game compatible.
- The new "official" Nexus site mod manager.
- VORTEX - Beginner's Guide #1 (of 4) video tutorial series by Gopher.
- Install NVSE for use with Vortex forum thread.
- Nexus VORTEX Category Wiki articles on various aspects of the manager.
- Note that Vortex is now (30 Jul 2019) an official "production quality" Vortex 1.0 Release, meaning it's in a state where it is both stable, “feature complete”, and essentially "bug free" (as much as any released product ever is for the majority of users). That's not to say that they won't be adding plenty of new features and "bug fixes" to Vortex in the coming years, but the Vortex of today is one that will be a more than able mod management tool for the vast majority of mod users. Please see the link for more details, and report problems to the Vortex Forum.
- Wrye Flash (WF) is the FNV version of "Wrye Bash" (WB) and creates the "Bashed Patch" mentioned. It is most similar to the old (now considered obsolete) WB version 298.
- WF/WB is a "swiss army knife" sort of tool, but if you follow the Wrye Bash Pictorial Guide you can get functional with it quite quickly. The most essential parts are the "Mods" tab for your "load order" and "bash patch", and if you intend to use it as your mod manager: the "Installers" tab (known as BAIN) for managing your installed mod packages. Complete documentation is included as HTML files.
- Fallout New Vegas Beginners guide to modding Recommended thread on using Wrye Flash with FNV.
- Bash Tags and the Wrye Bash Patch Wiki article.
- Bashed Patch file with Marked Mergeables Wiki article for Wrye Flash.
- Wrye Flash NV Support Thread.
- Wrye Bash Support for all games Note that WB is currently on version 30x and doesn't yet have (but is working on) updated patching code for FO3 and FNV.
FOMOD organized packages need to be installed with FOMM. Mods installed by one manager are not "managed" by another, though the files so installed are still used by the game. The advantage of FOMM is that it has extensive scripting capability not present in the others. If a mod says "install with FOMM", then you should ... unless you are competent enough to read and interpret the script files (often called "wizards") in order to repackage them for your preferred manager. Most of the time this is easily accomplished, but some FOMOD scripts deal with edits to files other than those involved just in installing the package. Most other managers don't have any scripting capability, and none are as extensive as FOMM's. When in doubt, check the comments on the mod download page.
The subject of "ArchiveInvalidation" in mod managers always comes up when discussing "texture replacements". The topic is described in the TESTG Troubleshooting section. (When you have questions about "meshes" and "textures" and their replacements, this site is a good starting point to understanding the subject.) The basics of turning "ArchiveInvalidation" on and off are described in the the wiki article Fallout NV Mod Conflict Troubleshooting "Checklist" section.
Very briefly: "ArchiveInvalidation" (AI) tells the game engine to use the "loose files" it finds in the folders under "Data" instead of the ones it uses by preference in the BSA files. When you "toggle" that feature in your mod manager, it causes the game engine to determine just which files in the BSAs exist (or no longer do) as "loose files" in the folders in order to use them instead. The engine does not do so automatically unless it cannot find the specific file in question inside a BSA file (which is usually the case when a mod has added a new one). Most mod managers do not automatically "toggle" AI when adding or removing loose files. You only need to "toggle" once between game sessions no matter how many "loose files" are added or removed.
The current AI technique employed is called "BSA Redirection" and each mod manager uses it's own arbitrary "AI BSA" file name for this purpose, which is why using multiple different managers to handle AI doesn't work correctly. Choose only one manager to handle AI if you have multiple installed.
NOTE: For Vortex, this is initially a two-step process. It is outlined here due to the many reports of confusion about it (with thanks to browniefox).
- Download Vortex, choose options (ignore the "failure to validate" part at the start; just tick the box and choose your preferred skins) and enable.
- Go to Settings, click workarounds and click BSA Redirection to "On" (so it goes green).
( Now this is typically where people get to or already got to and are having issues. This adds a MOD. It doesn't do the "archive invalidation" check automatically.)
- Go back to your Mods tab. Find Vortex Archive Invalidation. Disable and then Enable it. (Or vice versa. Just make sure you toggle it "off and on again").
- You're done. You just did the "archive invalidation" step. In the top right a blue box should come up that whizzs through all your mods (this is the AI process).
- Hereafter, you should only need to toggle Vortex Archive Invalidation on the Mods tab whenever you add or remove mods that provide "art assets" (meshes, textures, animations, etc.) as "loose files" from a particular profile "load order".
About your choice of mod manager
Things change over time.
In the short term, FOMM is designed for FO3 and FNV, and works; but development has stopped. Wrye Flash works as well, and is an old fork of "Wrye Bash" (WB). However it is from before the current WB "300 series" version, which is just finishing a 5 year rewrite of the interface code (retaining essentially the same look and features) to become a more easily updated and general game manager compatible with Bethesda games (including Skyrim and FO4), but has not yet started work on retro-fitting/updating older Gamebryo engine game patching. Looking forward, "Wrye Flash/Bash" appears to have more potential in the long run. But it is currently limited in the games it works with, and is not where the team would like. It's "all active files in the Data folder all the time" approach is simple to understand, but more disk space intensive if you want to use multiple "profiles".
Now that "Vortex" is in full release people are finding it less intuitive than they would like, most especially if they are coming from NMM or MO/MO2. The similarity in "empty Data folder" design approach is not enough. There is no getting away from reading the documentation, but in fairness that IS said about any mod manager (old or new). Video tutorials cover the highlights but tend to miss the details that trip people up. However, once you have it up and working, it can deal with most mods for any game on the Nexus.
Much like with your favorite text/word editor: what you spend time and effort learning in the first place, tends to become your "favorite" as long as it still meets your needs. If you are choosing your first mod manager, expect to spend time learning about it and to have some problems initially. Locating good support will then become the key distinguishing feature.
Smaller Plugin Cap
Be aware that there is a limit to the number of mod plugins (ESM and ESP files) you can have active at the same time. ("Active" meaning the file is present in the game "Data" folder with an ESM/ESP file extension, and "activated" in the game for loading.) Merely being present in the "Data" folder, even if not "activated", plugins count against the effective limit the game can cope with. The game loads all that it sees in that folder before determining if they are part of the "load order". As a result, even "Inactive" plugins can cause a hidden "Missing Master" error. This is common for Gamebryo engine games, but the cap is much smaller for FNV than players of other Bethesda games are used to. The patched game has a cap anywhere between approximately 130-140 "active plugins" depending upon your system. "Strange things" happen when you exceed this cap, such as textures suddenly looking weird (missing, or solid or "wrong" surface colors) and the game crashes where previously things were fine.
Remove any unused plugins (ESM or ESP extensions) from the "Data" folder, especially "optional files" which shouldn't have been installed in the first place. Again, installing and testing one mod at a time, especially as you near or exceed 130-140 active mods, is the best way to tell where this limit is for your situation.
There are ways to get around this limitation: by "merging" plugins, and by placing only the "activated" plugin in the "Data" folder (which some Mod Managers do) for instance. See the wiki article Merged Plugin Guidelines for Personal Use for a description of the "merging" process.
There are two types of "downloadable content" (DLC) available for FNV: four expansion addons to the game world, and "item packs". There are four "pre-order item packs" originally only available through certain retailers for pre-ordering the game, which contain custom items available to the starting character. Later the "pre-order packs" were made available combined in the "Courier's Stash" package. The fifth expansion "Gun Runners Arsenal" (GRA) is also an "item pack" with primarily additional unique weapons, weapon mods, and new powerful ammunition types and ammo recipes; along with some additional Steam "Achievements and trophies". All five expansions and the "Courier's Stash" packs are bundled in the "Ultimate Edition" of the game.
The "pre-order packs" and GRA have no impact upon the main plot line. The other four expansions provide additional background motivational material on some of the characters in the main plot, as well as additional world spaces, unique weapons and chems, and new challenges to explore. You can safely ignore them without harming the main plot progression if you wish.
The community has generally recommended that you play the four world expansion DLCs in this order. Note that it is not strictly in release date order. Some feel strict release order sequence is the development team's design:
- Honest Hearts (Happy Trails Expedition - accessed via the Northern Passage). Target: level unspecified. (Suggested before Level 10, and after the "Volare!" quest from the Nellis Airbase "Boomers" faction, which is unrelated but does get you a "rebreather" and is a way of judging how ready you are).
- Old WorldBlues (Midnight Sci-Fi Feature! - accessed via the Mojave Drive-In). Target: level 15+. Recommended before level 20 and Dead Money. (Suggested before the "Brotherhood of Steel" (BoS) quests as well.)
- Dead Money (Sierra Madre Grand Opening! - accessed via the Abandoned BoS Bunker). Target: level 20+. (Suggested before level 20, just after BoS quests.)
- Lonesome Road (The Reunion - accessed via the Canyon Wreckage). Target: level 25+. (Suggested last, before the 2nd Battle of Hoover Dam climax of the main plot. Be prepared for lots of Deathclaws and SentryBots).
All the DLC worldspaces (except for Dead Money) can be returned to upon completion of their quest. In addition, only Lonesome Road can be left at any time before you complete it's main questline. Companions are not allowed to enter any of the DLC expansions. They must be dismissed ("part ways") or will be dismissed for you prior to the actual activation of the specific add-on quest. Some companions can be acquired during the DLC quests, but will not be able to leave that worldspace at the end of the questline.
If you don't want to play with some of the DLC, you may find that simply not activating them is not enough; they still load anyway. This is due to the presence of a "<DLCName>.nam" file for each. These force the game (and the Construction Set "G.E.C.K.") to load them automatically. You will need to move those ".nam" files out of the "Data" folder, or rename them with a different extension before you can successfully deactivate the DLC.
Mod creators are always wanting additional script capabilities the native game "construction set"/editor doesn't provide. These are generally provided by mods/tools called "Script Extenders" and are created by talented programming members of the community. In general, there is only one such tool that the community settles around and possibly additional supplemental extenders that "hook" into that primary one.
A "script extender" by itself does nothing. It is not an "executable" that you run. It is a "Dynamically Loaded Library" (DLL) file that is only used when a mod calls for a feature/function provided by that DLL. If you don't have any mods that make use of that "script extender" library, then it is never loaded. The most you might see in that case is a log entry that it has successfully "hooked" into the game executable.
FNV, at the time of this writing in 2016, has New Vegas Script Extender (NVSE) as it's primary extender, and the supplemental "script" extenders JIP NVSE Plugin and "Lutana NVSE Plugin". In addition to other functions, JIP is known for providing "companion" oriented functionality, and Lutana for "game controller" input emulation. However, both go well beyond those features. Mod creators should check their download pages and the GECK website on "NVSE", "JIP", and "Lutana" for documentation of their added functions. Various mods require one or the other or even both, in addition to NVSE. This is always documented in the requirements section of the mod's description. NVSE plugins other than supplemental "script extenders" also exist.
There has since (2020) been a community effort by a different team to fork and continue to extend the original NVSE tool with a compatible replacement called xNVSE. It is intended to be used "as-is" in place of the older NVSE plugin and is often referred to interchangeably by name with that plugin (i.e. both get referred to as "NVSE"). The xNVSE fork continues the version numbering from the last release of the original (e.g. "v5.1beta6").
NVSE incorporates all of the functions of the Fallout 3 (FO3) Script Extender FOSE. However, it is not "backwards compatible" in the sense that it can be used in FO3 instead of FOSE.
It is first necessary to get the vanilla game correctly installed and INI files created before installing NVSE. Be sure you go through the hardware setup screen, and then exit when you get to the "Main Menu" which has the options to create a new game or load a save game file. This is necessary to create the "FalloutPrefs.INI" and "Fallout.INI" files in your "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder.
The FNV game itself does not automatically create a log file. However, NVSE can be made to turn one on. See Checklist item #4 in the "Fallout NV Mod Conflict Troubleshooting" guide for instructions on how to enable this.
You must have NVSE installed correctly before it or any of the supplemental extenders will work correctly. All the script extenders create "log" files in the game "root" folder, automatically. If there isn't an NVSE log, then you either didn't set it up properly or failed to start it correctly. It always creates one with game initialization entries automatically. Once installed, always check the log files for errors after initially running the game with any mod that requires them. It's also a good practice after installing any mod.
NVSE will always create a log when the game starts. The others only do so when a mod calls for their services. Otherwise there is no visual indication that they are working or not.
Be sure to launch the game either with FNV4GB Loader (if you use it) or the FNV 4GB Patcher modified version of "FalloutNV.exe", both of which automatically recognize and launch NVSE; or the "nvse_loader.exe" instead of by the vanilla launcher or from the Steam Library, so NVSE gets loaded. If that still doesn't get you a log file, then you need to reinstall NVSE.
- This time, don't use a mod manager to install NVSE. They always assume everything goes under "Data" which is not the case with NVSE.
- Manually unpack the NVSE archive file somewhere outside of the game folders. The internal structure of the archive usually has a top level "version" folder like "nvse_5_0_beta3", which the game won't process correctly.
- Copy the contents under the "version" folder (excluding the "src" folder which is not needed) into the game "root" folder (i.e. "<Steam Install Path>\Fallout New Vegas").
When installed correctly you should see "<Steam Install Path>\Fallout New Vegas\Data\NVSE" folders. The game "root" folder should have four "nvse_*.dll" files, and "nvse_loader.exe", along with two "nvse_*.txt" files. You can compare the contents of the unpacked archive to the files you copied over to the game to check you have everything.
Other NVSE plugins like JIP and Lutana will go into the "Data\NVSE\Plugins" folder. You may initially create this "Plugins" folder yourself or let either JIP or Lutana plugins installation do so for you. Again, best to install them manually unless you know your mod manager can properly handle such plugins. You always have to watch out for "version" folders. When present they always require you either restructure the archive without them or install manually.
NVSE installation does not automatically create the "nvse_config.ini" file in the "Data\NVSE" folder. When you need one for the "Sheson" memory patch mentioned below under "game fixer mods", simply create a text file of that name and rename it with the ".ini" extension instead of a ".txt" one.
Towards Game Stability
- The foundation of game performance is to first optimize your system for gaming. Unfortunately the primary technical guide to this for FNV (TweakGuides.com) has closed. The following links are to those same or similar articles hosted on nVidia's GeForce.com site Guides page.
- The videographer GamePoets has recently (30 Oct 2018) released a definitive 12:11 minute Performance & Stability Guide YouTube video for "Tale of Two Wastelands (TTW)" covering many of the suggestions in this article. However, while it does not conflict with any advice here and generally works for FNV, it also does not cover quite as many options as detailed in the wiki Fallout NV Mod Conflict Troubleshooting article. It does make an excellent and recommended starting point for initially dealing with such issues up front.
- If you want a stable game, don't make any changes to your setup once you start playing and making "save game" files. Even updates to current mods run the risk of making things unstable after the point they are added. If you do update, ensure you know which save to revert to prior to that update if it goes wrong.
- Do not use the game's "auto-save" feature. See the sub-topic 'Issue: CTD on interior/exterior/"fast travel" cell change' in the wiki article Fallout NV Mod Conflict Troubleshooting for the explanation and alternatives.
- Removing a mod that has stored some elements in a "save file" will leave residue (even with a "clean save") that can cause problems down the road. In particular you have to watch out for mods that use scripts to permanently change form and leveled lists (such as, purely as an example, Millenia's Weapon mods). This is not, in and of itself, a bad thing as there are compatibility advantages to using this "script" technique. Such mods usually point this out in their description. But it is something to pay attention to when experimenting. It's better to find out what causes problems before you start to play in earnest.
- Use the Community "game fixer" mods. The following are commonly recommended, though their effectiveness varies by system. Install and test individually in the following order:
- (Note that NVSE is not listed as a "bug fix", though it may be required. Instead it extends the game functions that may be needed to produce a fix. See the Script Extenders section for details.)
- NVTF - New Vegas Tick Fix is a lighter, more compatible version of the 64hz stutter bug fix from NVSR and is now the recommended solution to stutter problems. Fully Windows 7 & 10 compatible, including Fast Exit. No more fiddling with INIs!
- Alternatively, the older New Vegas Stutter Remover (NVSR) (requires NVSE or xNVSE. The NVSR 5.0 beta versions are stable, but many people have problems getting a problem free INI configuration for Windows 10. The author and several users has provided configurations they find to work on the "comments" page, but "your mileage may vary". Check version requirements of other mods when choosing.)
- New Vegas AntiCrash (NVAC) (solves most common CTDs).
- FNV Mod Limit Fix (Requires NVSE). Works with latest Steam and GOG versions. Fixes the FNV mod limit bug, allowing a maximum of 255 plugins to be loaded. It can also cause an increase in "Frame Per Second (FPS)", remove game stutter and allow for faster loading times especially when using a large number of mods.
- "Sheson memory patch" for NVSE. (Increases "heap size". Use either the "heap replacement" feature of NVSR or this. Both together do not appear to conflict, but seem to be "overkill" at the cost of almost 1GB of game memory.) See the 'Issue: CTD without warning, "out of memory error", or stops responding' sub-topic in wiki article Fallout NV Mod Conflict Troubleshooting for simple but detailed instructions for enabling this patch or alternatives.
- Yukichigai Unofficial Patch (YUP) (and the various optional patches for it and other mods, There are other YUP patch files than on that page you may have to search out for other mods). Provides the most current and complete "bug fixes" for the vanilla game without requiring anything else.
- The following are complementary to YUP but by different teams, and extend NVSE functionality as well as fixing a number of game engine bugs using DLL files. Being a DLL means, unlike YUP, they do not take up a "mod plugin slot" in the "load order" as they are loaded (and unloaded) as needed by specific plugins from within the game rather than at "startup".
- The following are plugins loaded at game startup.
- Unofficial Patch Plus bug fixes that require NVSE, plus some "fixes" that are not technically "bugs", but believed by the author to be "as intended").
- The following MAY conflict with YUP. Read their descriptions and requirements carefully.
- Mission Mojave Ultimate Edition - FNV Community Patch (MMUE) (alternative to YUP, along with it's various optional mod compatibility patches). Note some who have looked at the internals of both YUP and MMUE feel they should not be used together and that YUP has all the "bug fixes" of MMUE (except for one related to a "Companion Perk"), and MMUE makes changes to "Hard Core" mod SleepDeprevation (SIC) in all three DLCs which add new "worldspaces" (Dead Money, Old World Blues, and Lonesome Road). MMUE is only partially a bug fix patch: it's mostly arbitrary edits that are not bug fixes. Some of the bug fixes are also incompatible with each other and are difficult to resolve. Be sure to check for the latest version (i.e. v12.1 of 27 Oct 2018 reverts some edits which introduced bugs).
- New Vegas Enhanced Content (NVEC) (notice it has "bugfix" modules if you don't want the "complete version" with enhancement mod inclusions. These "bugfixes" are likely to conflict with YUP, so only implement if you need them and manually resolve any conflicts. Note that it includes older versions of Someguy's "New Vegas Bounties I-II, which are incompatible with the latest release if you intend to play that excellent mod series.)
- Better Game Performance (NOT generally recommended by knowledgeable mod authors, test extensively first: some reports of minor slowdowns or worse, to include CTDs and corrupted saves. Best used with a "merge patch" or left out).
- Performance Of The Gods Disables the same things as "Better Game Performance", so use only one if you do. However, the same caution applies to both.
- Avoid these common OLD recommendations:
- Zan AutoPurge Crash Protector. It's often recommended, but it's only intended for "debugging" and will cause problems while playing. This advice comes from the authors of the "script extender" tools.
These "game fixer" mods often alter the same records, which means you should only use one (because the "Rule Of One" still applies, in which case YUP is the favorite recommendation) unless you also use a merge patch file to resolve the record level conflicts. As with other record level conflicts, the "load order" determines which mod's "fix" wins.
One of the problems with mods that are "collections of" or "include" other mods, is that they rather quickly get "out of date" when the other mods they include are updated. The other major problem is that it is difficult and time-consuming to properly merge all the various individual plugins to work together. Not all "collection" uploaders are equally skilled, but inevitably the problems are laid to the door of the included mod creators. For these reasons, many experienced mod users and most mod authors dislike "collections" despite their touted advantage of reducing the number of active plugins. Carefully check the "latest version" upload date and comments on the Nexus before choosing to implement one.
Be aware that even with an "Unlimited Companions" mod installed, the game will have circumstances where more than one humanoid and one "creature" (to include the "eyebot" ED-E) companion can cause problems simply because the designers limited the number to avoid overloading the processing of their AI packages. Even if not present in the same cell they will count as "companions" until you "part ways" by way of their dialog. (SOME modded companions have been designed to avoid being detected the same as the vanilla companions.) This addition to the AI package processing "overhead" can be a contributor to lag and reduced FPS.
Body Replacement Basics
Body replacement is generally considered a "beautification" process. As such, it has to be done before you start "playing" the game in earnest, but should be added after you have a basic stable game setup. Remember: 'Pretty' doesn't beat 'playable'!
Replacing the vanilla body of either the Player Character or an NPC involves two different sets of files: meshes and textures, which usually come as separate mods. Mods labelled "body type" are actually meshes that have a different shape in some regards to those used for the vanilla body. Both are generally going to be found in the Nexus site New Vegas Models and Textures category.
First of all you have to understand the difference between mesh and texture. Simplified, the mesh forms the 3D framework or shape of every item in the game. Texture covers the surface (provides a 2D "skin" if you will) to those frameworks. A UVmap (aka "texture coordinates") is part of the texture file and tells the rendering engine how to project the 2D texture onto the 3D mesh. While the mesh and texture are separate files, each mesh includes the relative path (starting below "Data"; from the "textures" folder) to it's respective texture. Changing the texture of a mesh requires either a direct replacement of the existing texture file by name, or changing the path to (and possibly the filename of) that replacement texture link within the mesh file. So the two files are intimately linked.
The vanilla body "texture" has underwear included, so it is not removable. Custom body replacement textures may have both a "nude" option and an "underwear" option texture as separate files. These tend to be "all-or-nothing" choices: everyone is nude underneath their garments, or everyone wears underwear; as long as that body replacement is used. Select a custom body texture mod that is designed to be compatible with your custom body type (i.e. the mesh) mod. Otherwise you may have apparent "black bands" around the groin area or huge scars on the breasts because the vanilla texture (used by default) doesn't fit correctly to the adjusted body mesh. Toggling "ArchiveInvalidation" off-and-then-on again as with other texture replacements may be necessary.
Body replacements are designed for two different purposes: to change the basic human body shape; and to play a "custom race": something other than a "vanilla human" (i.e. to role play what is normally only an NPC such as a ghoul, or an "anthro-pony", or "anime-style" character, or "creature" like a "Death Claw"). As a consequence of these custom meshes, vanilla garments may have "clipping" issues where adjacent body parts show through or don't seem to "fit" correctly leaving gaps or seams. Some "clipping" is minor, but often it is major enough that you have to also install mods for garments that are made specifically for that body type.
Both replacement purposes may involve using the "ShowRaceMenu", which has some peculiarities of which you need to be aware. (See the Issue: "ShowRaceMenu" / Changing Character / Uninstalling a "custom race" problems entry in the "Fallout NV Mod Conflict Troubleshooting" guide.)
Often these replacements will include female mesh paths to items for which the vanilla game did not provide a female version. (By default the game engine uses "male" versions instead in that circumstance.) However, these can cause conflicts with patches or an overhaul to the vanilla game, resulting in the loss of some fixes or changes. Such conflicts can usually be resolved with the use of a custom "Merge/Bash Patch" file or a distributed patch file for the specific mods involved.
"B-n-B" or "Bouncing Breasts and/or Butts" mods are meshes based upon a different "armature" or "skeleton" rigged with added "bones" (e.g. "breast bones") and weights to support the "bouncing" parts. They will either provide or tell you to use a specific "skeleton" in order to work correctly. Without that customized skeleton, the "bouncing" parts will not bounce and may appear "deformed" (i.e. stretching out to the horizon). There is only one skeleton used by each race in the game, so it will not adversely affect any "non-bouncing" meshes which will just ignore the added bones they don't know about. As a consequence, in order to see the "bouncing" effect in garments, you may need to install mods with those "bouncing" features enabled. Sometimes special animations for certain actions (i.e. walking, sneaking, jumping, swimming, dancing) are also available. Not all mods can use the same specialized skeleton, so check the description/documentation for each carefully. This "skeleton" choice can easily limit your options. In general, later skeleton versions have added "bones" not found in previous versions to accommodate features added in later mods.
Body replacement only affects the "unclothed" body. "Garments" (such as "clothing" and "armor") have their own "body shape", which is independent of that of the underlying body. They do not "warp around" or "conform to" the underlying body; they completely replace it. If you have body replacement type "A" and garments for body type "B", what you see is type "B". FO3/FNV mods usually use the "upper body" slot for armor and clothing. This includes both arms down to but excluding the hands (which have their own slots). There is no "lower body", "arms", or "legs" slot, and there does not appear to be any community agreed "standard" assignment for the three "body addon" slots. Consequently these might be used by other mods in a conflicting manner (e.g. for implants, holsters, other accessories, etc.).
Garments are kinda weird in games. A shirt isn't just a shirt. If you put on an outfit, that outfit typically replaces everything except your head and hands. If your character puts on a dress, the legs that are visible come from the dress model, and if your character is wearing an outfit with short sleeves, then their arms also come from that outfit, and not from the player's body model. It all depends upon which "body slot" the garment occupies, and whether or not the garment maker used a custom body mesh/texture as the basis of the garment. Typically adjustments have to be made. (See Type6MClipping Figure for an example of the problems "mashing up" a vanilla garment onto a Type6M "Athletic" body mesh. Click the link/thumbnail to see the enlarged image. Use your browser "<back page>" control to return to this page.) If you use a body replacement, for either male or female, you generally want to get garment replacements to match that body type, or weird things can happen; especially if the body replacement exaggerates certain aspects beyond that of vanilla. The body textures coloration might not be the same, which can lead to weird color marks all over body parts that are from a different body type. In other words, if your character puts on a bikini made for the vanilla body type and you have the Type 6M "Athletic" body replacement installed, it's going to use the vanilla body mesh with the bikini, so you won't get the bigger boobs, wider hips, etc., from the Type 6M body while wearing it, and the textures are going to be all screwy since the bikini model will be expecting the normal vanilla body texture and you've replaced it with a different and incompatible texture. This is not to say some vanilla garments won't work fine with some body replacements that are not too dissimilar to vanilla.
All of this applies to NPCs as well.
For some garments it doesn't matter. If you put on power armor, for example, there aren't any body parts visible, so it doesn't make any difference whether you are using a body replacer or not.
Cosmetic appearance mods (tattoos, piercings, hair styles, beards, etc.) are often included in this grouping, but really should be considered separately if they only involve the "head". Some features, such as scars and tattoos, are part of the texture and not a separate addition. Others have to use specific body part slots, which are broken down into "Body Data", "Face Data", and "FaceGen Race". Only one mesh can be assigned to each body part. For instance, "Face Data" has only "Eye colors" and "Hair styles". Which in turn means you can have "hair" or a "hat/helmet" but not both. If there is hair showing under a hat or helmet, it is part of that "hat" mesh. FNV does not have a separate slot for "facial hair" (i.e. beards, mustaches, "mutton chops", etc.). Mod authors have to cannibalize the use of a different slot for the purpose, or make the facial hair part of the texture itself.
Because they use a slot on the head, custom "Hair" and "Eye" mods can get complex to install. Sometimes they require using the GECK to add their mesh and textures to the "head" mod. Read their installation instructions carefully before choosing.
As the head is separate from the body, that means it too can have custom versions of it's mesh and textures (i.e. "head06" is a replacement head shape). In all other regards it is similar to but independent of the body. As the head (hair and face) is a separate component from the rest of the body, custom meshes often have a problem with a visible "seam" where the head mesh joins with the body mesh. It is just a fact of life you will have to live with; nothing the mod creators can completely eliminate. There are "seam concealer" mods that provide necklaces and similar to hide this seam. Not all such "head" mods are compatible with various other "body mods" or even "vanilla" heads. Read the documentation for each carefully.
The question of using body replacers from "Fallout 3" in "Fallout New Vegas" often comes up. As usual the answer is not simple.` If the "replacement" is purely "meshes" and "texures" (no ESM or ESP file required), then the answer is MAYBE. It is best to use "ported to FNV" versions of FO3 body replacements. However the texture files can usually be used without change so long as they share the same UV map. In fact the mod "Type 6 Modification Body NV by Izumiko" advises using the texture for the "DIMONIZED TYPE3 female body" from the FO3 section of the Nexus. However, this texture mod has since been uploaded to the "New Vegas" section of the site, apparently unchanged. As always, experiment with care.
In summary, you can expect to need "Body Type", "Body Texture", "Clothing and Armor", and possibly "Head", "Hair", and "Eyes" mods that are all compatible to work together. Hopefully by now you realize that using a "Body Replacement" mod is not something to take lightly. It is more complex than it appears on the surface. For a list of "Frequently Asked Questions" (FAQ), see the Issue: Custom "Body Type" Replacement section in the "Fallout NV Mod Conflict Troubleshooting" guide.
New players always want to know which mods are recommended for some style of play. The problem is every player's sense of what is most desirable is highly personal and varied. With the limited number of plugins this game permits, people have to pick and choose very carefully, and this limits the number of mods they can have experienced.
As has been mentioned before, the new player first needs to determine what is most important to their style of play. Then they have to prioritize those aspects and get a stable game setup with those mods installed. Only then are they ready to choose mods from Categories such as Quests and Adventures on the Nexus. The mods in a category can be sorted on several criteria, but the default is "endorsements" which is a reasonable indication of popularity. (Which in turn is why it is important for players to endorse mods they enjoy.)
Alternatively you can try using the "advanced search" capability in the Forums (the "gear" at the end of the "search" field at the top of the forum page) to look for key terms such as "best quests" in posts made on the specific game forum of interest. Unfortunately the list of forums and sub-forums in the "Find in forum" picklist is not organized alphabetically, so you have to scroll down looking at the entries carefully. Fortunately for FNV players, the FNV forum is listed (as of this writing) near the top just after "Skyrim", "Oblivion", "Morrowind", and "Fallout 3".
There is a "mod" called the Fallout New Vegas Ultimate Graphic Guide by Wuestenranger which provides that author's recommendations for a "graphics immersive" modded game using both FO3 and FNV texture mods on the description page. It does go into recommended install order and "adjustments" for the mods. At the very least it is useful for indicating the comparative impact upon FPS of an extensive linked list of various "improved texture" mods (by type) using a "green-yellow-red" color scheme based upon their experience. The author is not a native English speaker, yet the guide is quite understandable, so don't be put off by minor errors in grammar.
Factions and Reputation
Some people encounter problems with certain quest lines becoming blocked from them because they did not understand how the Faction and Reputation system applies and affects quests.
Factions are about "groups" of individuals (and creatures), and they have relationships with other groups. Reputations only affect the player and applies only to factions (not individuals); it never directly affects an NPC or Creature and only applies through their faction relationships. When the player "messes with" an individual actor or their "owned things" the game then checks the actor's primary faction and adjusts the player's reputation ("fame") and "crime" (or more accurately "infamy") against that faction (two different, independently tracked values). A faction can be "friendly", "allied", "neutral", or "enemies" with another faction. Your reputation with one faction can affect the reaction of other factions by association. These associated reactions are the most likely cause of unexpected reactions and quests becoming blocked.
The most non-obvious thing is that there are actually several "Legion" factions (and "Securitrons", and who knows how many others). This is only available when you start to look at the records of an individual actor in the GECK, which is why most people are unaware of it.
The "faction disguise" process is supposed to be your means around these negative effects. As I am sure you are aware, certain Actors (e.g. Legion Mongrols and Caesar's Guards) are not fooled by a disguise. Which means you need to use one of an acknowledge enemy (e.g. NCR) whenever you are "messing with" a faction member that is important to a quest (e.g. Legion) wherever you can avoid someone who can penetrate that disguise. That way you keep your "undisguised" reputation intact.
Remember only certain combinations of armor and helmet act as a "disguise". If you don't get the message that you now appear to be a member of that faction, you are not "disguised".
Ambushing someone will only preserve your reputation without a disguise if: 1) you are hidden and unobserved ("sneaking"), and 2) kill everyone in "line of sight" before someone spots you. Point 2 generally means you have to kill everyone within the time period of your initial attack: regular, or VATS/"Bullet time" action points. Anyone surviving that initial attack has a chance to ID you. Distance is not sufficient on it's own but combined with sneaking may buy you enough time to kill everyone before they get within range for an ID. But at melee distances you better get them all in the initial attack (or wear an enemy disguise).
For those who don't want to give up the use of their favorite armor combination regardless of faction association, recommend the mod Faction ID Cards by Morat48.
It will often be the case where you have to uninstall a quest mod once completed in order to make room for another. An uninstall of any mod always has the potential to cause corruption of subsequent save game files. (First, consider if creating some "merged plugin" files might not serve your purpose better. Please see the wiki Merged Plugin Guidelines for Personal Use article for details. Carefully note the difference between the "merge plugin" referred to here and the "merge patch" file referred to later in this article. They are different techniques serving different purposes.)
Your best chance to avoid this possibility of corruption requires you make a clean save first. (Even though the procedure is written for Oblivion, it applies to Fallout games as well as they use the same game engine. The FNV equivalent to the TestingHall location is the DevArmory. Use a map marker location such as Goodsprings or Jacobstown as your return destination.) Only then can you expect to be able to install another quest mod without problems but this is not guaranteed. Plan ahead. Remember, "unique items" specific to a removed mod will vanish from your game. If you want to keep them, then don't remove the mod. Otherwise, sell them before your "clean save".
Merge Patch File
The "Rule of One" means only the last loaded plugin that touches on a record, "wins". This is not usually a satisfactory solution as only one plugin is the winner. Even if other plugins affect different records but are dealing with the same sort of "thing" (i.e. perks, weapons, armor, ammo, etc.) they lose out completely if they touch the same record as the "winning plugin". So you might have several dozen plugins loaded, but only a few "winners" if the losers are all dealing with the same common item (even if they don't actually change it). The way to get all the plugins to use their records that are not in conflict, and still resolve all the conflicting records to a single "winner", is the use of a "merge patch file" that performs "record level" (instead of a broader file or type level) resolution.
[Note: Even with the release of the "FNV Mod Limit Fix" (see the Smaller Plugin Cap section), these techniques still fulfill their same useful roles.]
There are two primary methods of creating such a "merge patch" file: through the use of Wrye Bash "Bashed Patch", or a manually created file. (Wrye Flash NV is an older "flavor" of Wrye Bash specific to FNV.) See the S.T.E.P. Merging Plugins Guide which covers both approaches. (Use of "Mod Organizer" is not required.) While both WB/WF and xEdit (FNVEdit) are creating essentially the same thing, the big difference is that WB/WF automates the "record level conflict" resolution in load order sequence. This works fine for most such conflicts. But the xEdit process lends itself to deciding those exceptions where you want an earlier loading record to "win" the conflict instead. By running WB/WF first, and then creating an xEdit patch with just the different winners, you are reducing the number of manual changes needed. This becomes important if you tend to modify your load order with updates to plugins frequently, as you should rebuild your "merged patch(s)" whenever you do so.
Note that xEdit can "automate" the creation process in a similar manner to WB/WF, but it doesn't make use of "Bash Tags" and doesn't merge "leveled lists" either which WB/WF does. WB/WF also has built-in "tweaks" to game settings that it incorporates into the patch. You can also use xEdit to give "unique" results that none of the plugins provide (in effect creating a "new patch plugin" result within the overall patch.)
- See the wiki article Bashed Patch file with Marked Mergeables article for a step-by-step guide to building your first "Bashed Patch" file. It is a supplement to the Wrye Bash Pictorial Guide, which is designed to quickly get you functional with Wrye Bash, which is the easier approach for a novice mod user, especially when thousands of records are involved. "Marked Mergeables" are needed for the games using the older "Gamebryo" engine due to the "plugin cap", while the newer "Creation" engine games don't have that "less than 255 files" limitation and can ignore that step.
- The FNVEdit Training Manual and the video Making a Merge Patch by Roy Batty both use the "merge up" method of manually creating a merge patch with xEdit/FNVEdit.
- If you name your xEdit/FNVEdit manually created merge patch file: "TES5Merged.esp", then LOOT will automatically sort it correctly (even when you include it in a load order with a Wrye "bashed patch" file.)
Some suggestions for what and how to merge to reduce the number of active plugins can be found in Merged Plugin Guidelines for Personal Use.
Those taking the "manual" approach to creating a "merge patch", as well as mod users in general, need to understand about "Bethesda Software Archive" (BSA) files, which are very similar to (but not the same as) other archive format files such ZIP, 7Zip, and RAR, etc.. An archive is a way to package and compress various individual files together to both group related files and save physical disk space. Bethesda games can read the contents of their respective BSA formats, to include folder paths, without actually extracting the file contents to disk but into RAM memory instead as needed. BSAs are not loaded unless they have the same beginning to their file name as the ESP plugin (i.e. "Project Something.ESP" and "Project Something - Assets.BSA".) It isn't exactly clear just how much of the filename has to match, so common practice is "all that is significant enough to distinguish from others" (like other "Project" mods) up to a blank space. The BSA filename has to match an ESP, not an ESM file. The ESP does not have to contain any actual content, but a file with the correct name must exist. Without this, the BSA is ignored, and you get the "missing textures" red triangles, etc..
Mods that have their own BSA files but get included in a "merge patch" file won't have the necessary matching ESP filename to cause their BSA to get loaded. The solution is to extract the contents of their BSA files (using a tool like BSAOpt or the newer BSAExtractor (BSAE)) into the same folder (keeping their sub-folder structures intact), and then create a new BSA from the contents of that folder with the name of your "merge patch" file using an FNV format compatible tool like the command line BSArch (freeware) by zilav. (Other BSA tools may be able to extract files from a BSA, but may not be able to create a new, valid BSA due to subtle differences in format between games. Older tools that have not been kept up-to-date will not have all the correct BSA format changes discovered since. Always check compatibility first.)
The Wrye Bash "Bashed Patch" approach avoids this issue by leaving the ESP file associated with a BSA "active" (green "check" in the box icon). This is why you always need to run the "Mark Mergable" process before building the BP.
Mator Smash is an alternative to the Wrye Bash "Bashed Patch". While it's documentation is focused on Skyrim, it can be used with FNV. The results will needed to be checked. Please see the wiki article Mator Smash Quick Start.
Improved Texture Considerations
"Beautification", improving the visual experience, is an often desired goal. Most people think this means simply using a "higher resolution", large texture image size. "Texture packs" and individual model texture replacement files don't usually show up in the "load order", and thus don't count against the "plugin cap". (They are replacing vanilla assets; thus they overwrite existing files.) But this does not mean you can ignore their impact on your game and system. The situation is more complex than that. Please see the wiki Display resolution versus Image Size article for an explanation of the issues.
It is possible to "resize" texture images, but this is generally best done by reducing instead of increasing the image size. The tool developed for this purpose is Optimizer Textures. (If you have heard about "PyFFI", it is for reducing the vertices of meshes rather than textures.) Refer to the TESTG Utilities page for more on these tools.
Because "Texture/Mesh" replacement mods replace vanilla versions of those files, you absolutely have to toggle "ArchiveInvalidation" off-and-then-on again after installing or removing one of them so it recognizes that there are loose files (added by the mod) which have to be used in place of the vanilla files in the BSA files or are no longer there and the BSA files should be used instead. That failure to toggle is the most common reason behind most "not working problems". This is usually evidenced by the red triangle with "!" icon for missing meshes, and solid colors for missing textures. Please see the ArchiveInvalidation (by Manager) section and also the Checklist Item #15 & 16 entries in the wiki Fallout NV Mod Conflict Troubleshooting guide.
The only other reasons for mods to have these "missing element" error indications are that you failed to install all the necessary files (such as an ESM or BSA file), or they aren't in the correct location.
In the case of (for example) "Weapon Retexture Project" (WRP), the package has a "non-standard" folder structure. (Not an uncommon mistake by mod authors, so learn from this.) The game (to include most mod managers like NMM, MO, and FOMM) is expecting the top level folder of an archive package to be standardized folder names such as "Textures" or "Meshes", or ESM/ESP/BSA files. It assumes they are being placed under the game "Data" folder. This example package starts with a "RLS" folder, which the game does not recognize, and so it places that as the "top level" under "Data". (Sometimes this "non-standard folder" is the author's name or initials, other times it's the mod name and version, but anything unexpected is treated the same way: as a new folder or file.) Most likely when the files are "installed" but aren't found correctly, something similar to this is your problem. Unpack the mod archive (WRP in this instance) to some other location and then either rebuild the archive so the top level folders are "Textures" and "Meshes" (in other words, without the "RLS" folder from WRP at all), and then install with your mod manager, or manually drag those two folders into the game "Data" folder.
The text file under the WRP "RLS" folder is a documentation file. If you want to keep similar in the package, just place it in the top level along with the "Meshes" and "Textures" folders. Personally, I rename such to "<mod_name>_ReadMe.txt" so I know which package they came from. (Many author's act as if their mod's text file is the only one that might possibly exist in the same location or use the same common name (e.g. "Readme.txt").)
LOD or VWD Texture Packs
It's very common for people to want to add "improved" scenery texture pack mods that enhance the distant views of the world, such as mountains, trees, and cities on the horizon. These are known as "Level of Detail" (LOD) for landscapes and "View While Distant" (VWD) for objects. What most new to modding don't understand is that this is actually a complex subject. Your "load order" has an effect upon how these distant landscapes and objects are stitched together in "quadrants" or "quads" to form that view. The primary tool for this purpose in FNV is called FNVLODGen. However there are some other tools that can be used to benefit as well such as Landscape LOD generator tes4ll. For an in-depth explanation of what is involved, please see the LOD/VWD Overview page on the "TES Texture Guide" (TESTG) site.
The short guideline is: If you add or remove any VWD/LOD textures, please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding re-running FNVLODGen and TES4LL. There is nothing wrong with re-running them whenever you make any changes to your "load order", just to be sure. However, do remember that nothing is "free". High-resolution LOD/VWD textures add to the rendering burden of your video card. It's very easy for the LOD generator to overload on excess triangle/poly count (the engine has a cap), resulting in disappearing LOD in some world cells. This is another "beautification" aspect that can adversely impact your game performance; so it should be tested once you have a stable game with your essentials.
Suggested install order for VWD/LOD resources
Other than "FNVLODGen Resources", these are all optional to install:
- Install all texture packs for landscape (such as NMC and Ojo Bueno) first. (Their order is your preference for which wins conflicts.)
- Improved LOD Noise Texture (disable if using the GECK to generate terrain textures)
- FNVLODGen Resources
- LODadditions andImprovements
- Much Needed LOD
- Much Needed LOD - <specific texture pack patches>
Other optional mods (such as the "Limestone LOD" mod) load before or after those that conflict depending upon which you prefer to win.
- Run FNVLODGEN.exe. (If you have your game installed under the "C:\Program Files" tree, then you will need to have "Administrator" privileges.)
- UNCHECK "tree LOD" if you have Vurts floral overhaul installed. Otherwise, enable it.
- Select ALL Worldspaces.
- Generate LOD
It is necessary to leave any ESP files for these LOD resources "active" in your "load order" after re-running FNVLODGen to ensure that the LOD meshes unload when seen up close. However, they are usually "fully mergeable" into the "Merge Patch" file.
Placement of the VWD/LOD ESP files in the "load order"
"Art assets" are individual files, and only the last installed file will be used. As such, they are not involved in the "record level conflict" resolution process used by "Merge Patch" files. If you combine multiple VWD/LOD mods, they can co-exist where they have unique file names. Otherwise the last one installed (overwriting) gets used where the filenames are the same.
Consequently, the "FNVLODGen.ESP" and similar "art" ESP files can safely be loaded after (below, higher number sequenced) "Merge Patch" files in the "load order".
"Testing" is not about "playing". It's about pushing boundaries and isolating problems that tend to only show up in the "edge cases". There are so many possible permutations of mod combinations no one mod creator can test them all. You can't count on anyone else to have tested your particular combination of mods.
You want to keep your "test" save files and your "game" save files separate. The easy way is to simply rename the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV\Saves" folder to something like "Saves - Game"; and create a new, empty "Saves" folder to replace it.
In very general terms, you want to create a "test character" just for that purpose. Simply take the defaults, unless you are testing a "character overhaul" mod. But "quick and dirty" is all you need; don't waste time customizing it. Once you get past the character generation, make a "full save" using the Menu "Save Game" option (not a quick or auto- save). This will become your "baseline test" starting point; as close to "vanilla" as is practical. Make a backup copy of this save game somewhere else.
Now use the console (typically the "~" key) to toggle on "God Mode" ("tgm"). This is so you can go places a 1st level character normally can't with impunity.
GoodSprings is a good initial test cell because many mods initialize scripts there and you will be able to notice game lag as a result of scripts running pretty quickly. One known culprit in this regard is the "Cheat chest" from the "Weapons of the New Millenia" mod. If you initially don't see a problem, this is good. But if you do while in GoodSprings after installing a new mod, then you have an idea as to why.
Run around GoodSprings, into and out of buildings, interact with NPCs, etc. Then push outside of the GoodSprings cell (just ignore the opportunity to modify your character, which is how you know you're leaving that cell for the first time) into the wastelands. Be sure to test the Pipboy first (default: <Tab>) and equip both armor (even though you are invincible in "tgm" mode) and weapons. Go play with the Geckos to the NE and test both "First Person View" (FPV) and "Third Person View" (TPV) aiming to check for the differences and see if there are any animation or aiming point issues.
From this point you want to get to areas of the game that stress various aspects of it. Toggle on the console command "tmm 1" to show all map markers so you can "fast travel" to them. ("Fast travel" is one of the things you want to test anyway. But be sure to turn off the built-in game "AutoSave" feature first. You don't generally need save files while testing, and that will corrupt them.) Places with lots of NPCs, such as battlefields ("Camp Forlorn Hope", "Camp Searchlight", and "Cottonwood Cove"), rich textures (i.e. "Zion Canyon" of Honest Hearts and "Red Rock Canyon" where the Khans hang out), and cities which are their own cell "worldspaces" such as "Free Side" and "New Vegas". If you are testing a mod that adds new locations, be sure to test those locations. Whatever a mod is supposed to bring to the game is what you need to test as hard as possible to see if it "breaks". Don't forget to also work through changes to the HUD, UI, or Menus such as MCM if they are affected by a newly added mod.
Anywhere you see a "loading" screen is changing between exterior and interior cells, or loading a new "worldspace". Things operate differently between the two so be sure you include such cell changes in your tests. When running through the wastelands you will also trigger cell changes, but these will be less obvious. But they are where your character may seem to momentarily "pause" for no apparent reason. The longer pauses are called "stuttering", and mean you are pushing the limits of what your graphic system can handle. The pause is the result of it having to load graphics out of the video memory (VRAM) and then load in the graphics from disk. The more "high resolution" your graphics, the less room there is to "pre-load" adjacent cells into the same amount of VRAM, and the more likely you are to get stuttering. There are also INI file settings that affect this. (See the "TweakGuide's General Fallout Guide" link in the Towards Game Stability sub-topic.)
Once you feel you have tested a new mod addition sufficiently and haven't encountered any unresolved problems, make a new "full save" and leave the mod in your "load order". In future tests, you will probably want to start from this "cumulative modded test" save point, but may on occasion (depending upon the mod) want to start from the "baseline test" save. You should delete older test saves between those two just to keep the used disk space down.
Now repeat the same test cycle with the next mod you add to your "load order".
When you have tested all your mods and have eliminated conflicts, rename the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV\Saves" folder to something like "Saves - Test"; and rename your "Saves - Game" folder back to just "Saves" (or create a new, empty "Saves" folder). Whichever version of those two "Saves" folders ("Saves -Test" or "Saves - Game") is NOT present is the one which is the current "Saves" folder.Now build your "game character", this time with the full mod "load order" installed and functional, and again save after the character generation. Be sure to disable the game "Auto-Save" feature, and now you can play in earnest. But remember, if you want to add any mods once you start playing, restore the "Saves - Test" folder as the current "Saves", and test fully before adding it to your existing game.
Common Game Problems
These usually occur shortly after loading a "save game" in your first 50 or hours of play, or trying to get past the "loading screens" to the game's Main Menu, or after you made a change to your "install or load order".
In general, if you haven't changed anything about your game and it suddenly stops working correctly you need to look to other causes: such as software updates to Windows, programming libraries such as ".Net", or hardware drivers. Older games eventually get dropped from product testing. It is also possible you are having problems with your hard drive. It never hurts to run "chkdsk" and an anti-virus scan.
FYI: If you recently had a Windows 10 system update, you only have 10 days to revert to the previous version if you decide to choose that option.
If the vanilla game (no active mods) launched without problem, most likely you have a Missing Masters problem.
All of the following may not apply to your specific situation, but are worth repeating anyway. These are the most common solutions to problems.
- Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so.
- Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. With the game moved out of the default location you will not need to be running it as an "Administrator Account", which is safer. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.
- If you did move Steam out of the default location, then likely any access privilege problem is one of "File and Folder permissions" on the parent "root" folder under which you installed the games. If this is not set correctly to allow at least "System", "Administrators", and "Users" to have "Full Control" then you can't overwrite other files or make changes. You then need to enable the "Properties | Security | Advanced | Change Permissions" setting of the parent folder to enable the box: "Replace all child object permissions with inheritable permissions from this object", so those changes get applied to the existing files and sub-folders.
- Are you running Win10? Did you get or have the "Fall Creator's Update" of 2017 (FCU aka "RedStone 3") installed? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.
- As an alternative to NVSR, if you are running Win7 or Win10, try using the "New Vegas Tick Fix (NVTF)" mod instead.
- Related to the NVSR problem, for problems AFTER a save game is loaded see also 'Issue: Incomplete save game load' in the "Troubleshooting" guide.
- If you are suddenly having a "slowdown" or lag; or a lack of sound; or problems getting NVSE to load, or really anything new unexpectedly, please see the 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. This may be due to a Windows Update for the "Meltdown and Spectre Vulnerabilities".
- Are you using the 4GB Patcher with the Steam version? (DO NOT use it with the GOG version, which is already patched. Applying the patch will break it. Revert to the backup copy created if you did run it.) If not, please see the Maximizing use of memory section of this article. If you aren't sure if it was installed or working, just re-run the Patcher again. Make sure it's FNV 4GB Patcher. Won't hurt and it will tell you if it is already patched. (If the Windows ("Task Manager" | Processes) tab entry for the game process has more than 2GB (2,097,152KB) "Memory(Private Working Set)" used, then the 4GB patch is definitely in effect. But being below that threshold doesn't mean it isn't.)
- How can you tell if the 4GB Patch (for Steam) is working? The JIP LN NVSE Plugin has a function which can be run from the console: "GetIsLAA" (not case sensitive).
- Possible return codes:
- 0=patch is not applied
- 1=patch was applied to the executable, but extra memory is not being allocated
- 2=successfully allocated extra memory from the patch and is fully working.
- If "GetIsLAA" is returning code "1", try running the game from a "local administrator" account. If that is successfull, you need to move the game install location out of the "C:\Program Files" folder tree, or correct the "permissions" on the folder you moved it to, as you are going to have other problems down the road. Please see the wiki "Installing Games on Windows Vista+" article for details.
- Alternatively: if the Windows "Task Manager" indicates the "FalloutNV.exe" program has more than 2GB (2,000,000KB) of "Memory (Private Working Set)", then the 4GB Patcher is in effect. However, to the contrary: less does not mean it is not working. The game simply hasn't needed that much memory as yet.
- The game has "memory leaks", primarily linked to the audio system due to the version of the Ogg Vorbis Libraries used by Bethesda. Getting 2-3 hours before a CTD is pretty good. The audio problem is fixed by using the updated Ogg Vorbis Libraries posted by Kane Wright. You might also want to try using the tool "Memclean", which periodically (you can set the interval; default is every 15 minutes) tells the OS to perform it's built-in "clean up" of memory. It has a "mini-monitor" that displays memory usage. Doesn't seem to hurt and might help.
- If you are using the full 4GB of memory, most likely your CTD problem (now or in the future) is the default "heap size" is too small. It's so common you might as well deal with it now. Please see the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entry in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.
- You can also get "out of memory" errors from the graphics system (which is separate from exhausting system memory), even with the game 4GB enabled. The video pipeline is known to have "memory leaks", and these occur faster with "beautification mods". Here the cause is a combination of larger image sizes ("higher resolutions", aka "hi-rez"), hi-rez texture packs for skin, hair, clothes, weapons, and landscape; along with mods that increase the number of NPCS in a given cell. (All those hi-rez texture "personal accessories" get multiplied by the number of Actors.) Please see the wiki "Display resolution versus Image Size" article. While "ENBoost" can help, you may need to switch to lower resolution/ smaller sized images or even lower quality in your game graphics configuration.
- Move any "inactive" plugins out of the game "Data" folder. They count against the "plugin cap" (see Smaller Plugin Cap) because they get loaded by the game engine if found, and can cause "Missing Master" problems. Please see the wiki "Missing Masters" article if you get that error message.
- Don't install every optional file for a mod. Read the install instructions carefully. Optional files need to be selected on a "case by case" basis. For example: with any mod you usually only need one ESP (and possibly one ESM) "base" file depending upon whether you have all the DLCs active or not. Only if you don't have them all active do you need to install any specific DLC versions if there is an "Ultimate Edition/All/Merged DLC" version.
- "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than all of the plugins they are designed to make compatible. (This also applies to "fix" files for a plugin.) ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. LOOT does a good job of determining those basic orders. Getting the "load order" incorrect will cause Missing Master errors as well. You can make minor adjustments to the order and tell LOOT how to remember them. It's in the on-line documentation under "Metadata".
- FYI: The "pre-order packs" (aka "POPs": Caravan, Classic, Mercenary, and Tribal; available now in the "Courier's Stash" addon), are not considered "true DLC expansions" by most mods and "compatibility patches" because they just add certain unique items. So their absence should not deter you from using "All DLC Merged" plugins. Where they are included, they should come after "GunrunnersArsenal.ESM" which is a true DLC expansion. When in doubt, follow the process in the wiki Missing Masters" article to confirm they are not "master files" for that plugin.
- Don't install compatibility patches for mods you do not have installed/active (e.g. get rid of any "TTW" patches if you aren't running TTW).
- Do not use an "Auto-purge" mod for game play. (That was old advice from before we knew better.) They are designed for debugging by mod creator's only, according to the author of the JIP extensions to NVSE. See the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu', "Cause-2", "Solution-3" entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for the game settings that do the same job.
- Please see the paragraph about "auto-saves" under the Essentials for Getting Started section of this article. If you have been using the built-in "auto-save" feature and you get the endless "roulette wheel" when loading a save game, then your current save game file is corrupted and you will have to either go back to a save before the corruption occurred (hard to tell) or start over.
- If you have more than one mod that makes any change to the same record or set of records in the vanilla game, then you really need to use a "Merge Patch File" with that collection of mods. Please see the Third Rule: The Rule of One and Merge Patch File sections of this article.
See the wiki article "Fallout NV Troubleshooting Guide" for tips on getting the basic vanilla game to launch. If you can't manage that, you have a major problem and most likely need to re-install the game outside of the "C:\Program Files" tree as suggested in the First Timer Advice sub-topic in this article.
Once you have an error free setup, only then should you consider installing the mod FNV Mod Limit Fix to increase your plugin cap to 255. More plugins initially will only complicate tracking down the source of your problem.
The game engine still loads every file it finds in the "Data" folder into memory and checks it's references for "master files", regardless of it's "active" state while determining it's "load order". (The "master files" are listed in the "file header" of each plugin.) This is why they count against your "plugin cap". If it fails to find any of such referenced masters, it causes a "missing master" CTD without warning. Similarly, if you attempt to load a "dependency" plugin prior to loading a "master" file (which is usually, but not always, an ESM file) that it depends upon for certain assets (i.e. if you have not sorted your "load order" or have it wrong) it will also result in a "missing master" situation even though all the files are present. This is especially true of the vanilla game and official DLC plugins which are masters for many mods. The "pre-order packs" are dependencies of the vanilla game and expansion DLCs. (See the Vanilla "Load Order" section.)
Installing optional package component files that are not needed can prevent the game from starting. This is the primary reason you can't use a patch file designed for mods you do not have installed, as they will always be missing the "master" plugin of the absent mod and "mysteriously" crash.
Mods often include "asset files" that are placed in sub-folders under "Data", which are used instead of vanilla versions of those files. Merely "deactivating" a mod plugin does not remove such added (or restore replaced) files, so the mod must be either uninstalled or it's unused/unwanted "asset" files manually removed from the "Data" folder path so the vanilla versions will be used.
As the game engine fails to report WHY it crashed under these circumstances, we primarily determine it to be a "missing master" issue by the timing of the crash: when the game is loading files during the display of the "Main Title loading screens" (aka "Before the Main Menu") or upon loading a "save game file" (aka "After the Main Menu"). This is not to say it can't happen later, upon the first attempt to use an asset that relies upon a missing file, but at least 95% of the time it will show up as a hang or CTD either before or just after the "Main Menu".
See the Missing Masters wiki article for detailed instructions on identifying and resolving this issue.
Mod Conflict Troubleshooting
When you run into problems (which you will inevitably) there is the wiki article Fallout NV Mod Conflict Troubleshooting. It will help you narrow down the most commonly asked questions so you can get more directed help faster. It also contains links to all sorts of essential tools and stability mods, as well as some specific problems and solutions.
It's always useful to post your "Load Order" (LO) with your problem description. (Use the "Special BBCode" button in the Forum "Reply" menu bar as the third icon from the left in the top row, next to and left of the "Font" pick-list field to put the LO in "Spoiler" tags.) Screenshots are not the best way to convey your LO, because they usually can't include everything in one image. LOOT (mentioned above) can copy your LO into a list suitable for posting on forums. (It's under the ":" with three dots to the extreme right in it's menu bar.) Most "mod managers" have a similar "LO List" capability. But the total number of mods you have installed in the DATA folder is also important, because even inactive plugins are counted against the so-called "140 cap". LOOT provides both numbers: active and total installed.
For help interpreting an error log, please see the How to read most Bethesda game error logs wiki article.
Modding a game takes time if you want the mods to work well together and be stable. Rushing the process will invariably lead to problems. Take the time to read and learn about the many new things that are involved, and you will have a much more enjoyable game when you are finished with the preliminaries.
Post processing shaders
Within the Bethesda gaming community the primary two graphic enhancements other than texture replacements used are: the ENB Series and the SweetFX Suite of shaders (though others exist). They are "post processing" effects to enhance the graphic feel of the game as the cost of some processing power and "frames per second"(FPS). Their installation can make changes to the INI files in your "User" account folder.
I would suggest you skip them for the time being, until you get a stable game going. If your average FPS is below 30, any post process shader is going to be a massive hit according to this Steam Community thread. Only if you are then still interested, the following may be helpful.
They are two different approaches to the same issue and can be used together if your system can handle the load. (Though likely you will have to learn the meaning of the configuration settings to deal with potential conflicts between them, they are considered generally complementary. Those settings, however, are very specific for technical effects and will require educating yourself.)
The "ENB Series" is developed by Boris Vorontsov and consists of a version for a specific game, and is available in either a "wrapper" or "injector" format depending upon which your system and game needs to work. (Some people can get the preferred "wrapper" version to work with FNV, while others are forced to the "injector" version.) The site for downloading the driver series is ENBDEV.
The "SweetFX" is a "shader suite" that uses an "injector" called "ReShade". Reshade and SweetFX are described in the article How To: Anti-Aliasing/Shader Injection (SweetFX, GeDoSaTo, GEMFX, and ReShade) along with a couple of others. Download SweetFX Suite (including ReShade) here.
And then there are various "presets" for both available for download from the Nexus, which are specific configurations developed by the authors and users to produce specific graphic atmospheres. These are a matter of personal preference.
Refer to the wiki article Fallout NV Mod Conflict Troubleshooting sub-topic "Issue: ENB is not working" for general ENB installation instructions.
Most of us sooner or later end up installing a mod that makes some change to the "Heads Up Display" (HUD), "User Interface" (UI), or some of the game's Menus. See the HUD-UI-Menu Issues wiki article before you do so, and avoid potential problems.
How to ask for help in the forums
The How to ask for help wiki article applies to any game. Read it before posting any problem not found in the resources listed here in the forums to speed up getting to the correct solution. The time you are wasting otherwise is not just your own.
For help on how to use features of the Forum Software such as linking or embedding images, see the wiki How to markup images (etc) in forum posts and comments article
Want to create your own mod?
Please see the wiki Getting started creating mods using GECK article. It provides a learning roadmap, a starting point and guide to progression; not a tutorial. Consider it a collection of suggestions, tips, and links to more detailed tutorials, articles, videos, and tools. Be sure to look over the "Programs and Tools" section first to obtain those tools you will need to work with this older 32-bit game. The "latest and greatest" versions are not usually the correct, compatible choice. The GECK itself is a very buggy tool and this article includes setup solutions, warnings, and customization tips to help get you past those early frustrations.
- Installing Games on Windows Vista+
- A General Order for Installing Mods (Oblivion)
- Wikipedia 'Video_post-processing'
- FNV 4GB Patcher
- New Vegas Script Extender (NVSE)
- JIP LN NVSE Plugin
- 4GB Fallout New Vegas Updated.
- SteamLauncher for NVSE and FNV4GB and ModOrganizer
- S.T.E.P. ENBoost
- Fallout New Vegas Beginners Guide to modding
- LOOT online manual
- Tome of xEdit Current online manual for all games
- FNVEdit Training Manual (PDF)
- CASM with MCM
- Simple Saves
- Clean Quick Saves
- Essarrbee's FalloutNewVegas Fear and Loathing Guide
- Nexus Mod Manager (NMM),
- FNV Mod Limit Fix
- Making a Merge Patch by Roy Batty
- Performance & Stability Guide YouTube video for "Tale of Two Wastelands (TTW)".
- New Vegas Stutter Remover (NVSR)
- New Vegas AntiCrash (NVAC)
- Yukichigai Unofficial Patch (YUP)
- Unofficial Patch Plus
- Mission Mojave Ultimate Edition - FNV Community Patch (MMUE)
- New Vegas Enhanced Content (NVEC)
- Better Game Performance
- Performance Of The Gods
- Zan AutoPurge Crash Protector
- BSAExtractor (BSAE)
- Landscape LOD generator tes4ll
- Faction ID Cards by Morat48
- Steam Community thread
- How To: Anti-Aliasing/Shader Injection (SweetFX, GeDoSaTo, GEMFX, and ReShade)
- SweetFX Suite
Nexus wiki articles referred to by this article:
- Installing Games on Windows Vista+
- Bashed Patch file with Marked Mergeables
- Merged Plugin Guidelines for Personal Use
- Mator Smash Quick Start
- Fallout NV Troubleshooting Guide
- Missing Masters
- Fallout NV Mod Conflict Troubleshooting
- HUD-UI-Menu Issues
- How to ask for help
- How to markup images (etc) in forum posts and comments
- Getting started creating mods using GECK
Nexus wiki articles that refer to this article: