Difference between revisions of "Fallout NV Mod Conflict Troubleshooting"

From Nexus Mods Wiki
Jump to: navigation, search
m (Mod Conflict Isolation)
(Issue - MAIN - Nipton: Neither Vulpes Inculta nor Oliver Swanick appear: clarification)
 
Line 1: Line 1:
<div name="WIP Notice" class="boilerplate metadata" id="Missing Links"  
+
<div name="Development Box" class="boilerplate metadata" id="Development Box"  
style="color: red;background-color: #fdd; margin: 0 1em; padding: 0 10px;  
+
style="margin:0px 10px 10px 10px;border:1px solid #00C600;color: green;
border: 1px solid #aaa;
+
background-color:#fff5f5;padding:3px;white-space: pre-wrap;
/* Remove the next four 'white-space' lines to restore default white-space processing. */
+
white-space: -moz-pre-wrap;
 +
white-space: -pre-wrap;  
 +
white-space: -o-pre-wrap;  
 +
word-wrap: break-word;">
 +
'''This article is under development.'''
 +
It is essentially complete at this time, but new problems and solutions are discovered all the time and added.
 +
 
 +
If you have solutions, corrections, or suggestions for improvement, either make them directly, post to the [http://forums.nexusmods.com/index.php?/topic/5495032-fallout-nv-mod-conflict-troubleshooting-guide/ "Fallout NV Mod Conflict Troubleshooting" thread] in the "Fallout New Vegas Mod Troubleshooting" forum, or contact [http://wiki.nexusmods.com/index.php/User:Dubiousintent the current maintainer] by Private Message (PM).
 +
</div>
 +
<br>
 +
 
 +
== Overview ==
 +
This a collection of specific common problems and solutions, along with a general checklist of things known to contribute to problems, collected from around the web.  The [https://forums.nexusmods.com/index.php?/topic/5495032-fallout-nv-mod-conflict-troubleshooting-guide/ "Fallout NV Mod Conflict Troubleshooting" thread] in the "Fallout New Vegas Mod Troubleshooting" forum is for questions, suggestions, and discussion of this article's contents.
 +
 
 +
The article is organized around various generic topics, with specific mod conflicts or issues that don't fit into the other categories under "Solutions to Miscellaneous problems".
 +
 
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 0px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Don't overlook the power of a simple "cold restart" (aka "cold boot").  Before spending a lot of time chasing a problem, see if it's merely temporary by having Windows "Shut down" (power off) your computer, waiting 30 seconds (so RAM completely discharges it's contents), and powering on again.</div>
 +
 
 +
If you haven't already, it is suggested to read the wiki article [[FNV_General_Mod_Use_Advice|FNV General Mod Use Advice]] first to understand basic terminology as used here and differences in FNV from other games you may be used to modding.
 +
 
 +
Troubleshooting is a logical process of elimination.  If all logic fails, you have to revert back to a vanilla game and slowly re-install mods, testing each one thoroughly before adding the next.  It is a trade-off of "time" versus "effort".  Where that tipping point lies is up to you.  This is why you are always advised to follow a slow "install and test each mod one at a time" procedure when first setting up your game.  Then you know specifically which mod is causing your problem, which saves time.
 +
 
 +
The [[#How_to_ask_for_help|How to ask for help]] wiki article applies to any game.  Read it before posting your next problem in the forums to speed up getting to the correct solution.  The time you are wasting otherwise is not just your own.
 +
 
 +
== Checklist ==
 +
Standard list of things to ask yourself about your current FNV problem:<br>
 +
00. Did you install Steam under the default location of the "C:\Program Files" tree?  This causes many "strange" problems not otherwise explainable.  As painful as it may sound, read the wiki article [http://wiki.nexusmods.com/index.php/Installing_Games_on_Windows_Vista%2B  Installing Games on Windows Vista+] and move at least FNV.  That article has a link to the official Steam Procedure (a good indication that they now recognize the need to correct this).  This should be the first solution you try.  Otherwise you will spend a lot of time and effort trying other solutions, and still have to move the game files in the end anyway.<br>
 +
: Note that the GOG DRM-free version of FNV default install location is "C:\GOG Games\Fallout New Vegas".  It does not have this issue, in addition to already being 4GB memory enabled.  <span style="color: red;
 +
background-color:#fff5f5;">DO NOT run the 4GB Patcher against the GOG version.</span>  This situation has been known to prevent the ability to save any game files.  Other unpredictable problems may occur.<br>
 +
01. Are you getting an error message?  What is that pointing to as the source of the problem: the game, Steam, or Windows?<br>
 +
{{Nexus EU-GDPR Login}}
 +
02. What most recently changed (as far as what you have deliberately done to your game is concerned: New, updated, or removed mods or plugins)?<br>
 +
02b. Did any of the following which interact with the game get updated or changed recently.  They are prime suspects if nothing in the game itself changed:
 +
: a. Video driver.  (The latest is not always tested against an older game.)
 +
: b. Sound driver.
 +
: c. Mouse driver.  ("Advanced features" are not always compatible with the game.)
 +
: d. Power Outage?  Run a [http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/ chkdsk] on the drive to fix any errors that might have occurred.
 +
: e. Windows system update (consider rolling back to the previous [http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/ restore point]).
 +
03. If you have recently "verified local files" or "re-installed" the game, try renaming both the INI files in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder, and let the game rebuild them.  (There might have been some unexpected changes.)  Rename 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.<br>
 +
: Before you make any changes to the game INI files, please make backups and put them in a safe place.  See the [[FNV General Mod Use Advice#Game_INI_files|Game INI files]] section of the "FNV General Mod Use Advice" article for details.<span style="margin:0px 10px 10px 0px;border:1px solid #00C600;color: red;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">You have been warned!</span>
 +
: If you make any changes to any of the game INI files, remember to change it in all three files (after you have backups of the originals): the "Fallout_default.ini" in the game root folder (which only gets used to recreate the other two when they are not found), and the two in "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder ("FALLOUT.ini" and "FalloutPrefs.ini").  Otherwise you tend to lose track of which you actually changed if you have to "verify files".<br>
 +
:<span style="margin:0px 10px 10px 0px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 
word-wrap: break-word;      /* Internet Explorer 5.5+ */
">
+
">Note that if you are currently or have used "Mod Organizer", MO uses its own copies of "Fallout.ini" and "FalloutPrefs.ini" (from when the MO profile was created), located in the "<Steam install path>\steamapps\common\Fallout New Vegas\Mod Organizer\profiles\<Your Profile Name>" folder.  These files need to be changed as well.</span>
'''This is a Work In Progress (WIP), and not yet (and probably never will be) complete.'''
+
04. Does the most recent mod change use [http://nvse.silverlock.org/ New Vegas Script Extender] (NVSE) or supplemental plugins like [http://www.nexusmods.com/newvegas/mods/58277/ JIP NVSE Plugin] or "Lutana NVSE Plugin"?  Check that log (in the game's root folder: i.e. "<Steam install path>\steamapps\common\Fallout New Vegas").
 +
 
 +
: According to [http://forums.nexusmods.com/index.php?/topic/2619794-jip-nvse-plugin/?view=findpost&p=48608157 this post] in the JIP NVSE thread, mods are supposed to use and expect the following results when checking which version has been loaded, either in scripts or the game console ("<~>"); even from the Main Menu (without loading a "save game" file).
 +
: * GetNVSEVersion: returns integer (e.g. "5")
 +
: * GetJIPLNVersion / GetLNVersion: returns loaded JIP LN main version as float (xx.xxxx)
 +
: * GetPluginVersion "<string>": (quotes are required)
 +
::* "JIP NVSE Plugin": returns loaded JIP LN main version as float (xx.xxxx)
 +
::* "lutana_nvse": returns loaded JIP LN main version as float (xx.xxxx)
 +
:* IsPluginInstalled:
 +
::* "lutana_nvse" returns 1
  
Not all elements of the content have been posted as yetWhile the available elements should be functional, other elements are needed to achieve the end-result as described.
+
: If you previously had the "lutana nvse" plugin installed, make sure you have removed all "lutana*.*" files from both the game root and "Data\NVSE\Plugins" foldersOtherwise this can cause the "GetJIPLNVersion" command to fail with the error "command not found".
  
This message will be removed when the content is considered complete.
+
:<span style="margin:0px 10px 10px 0px;border:1px solid #00C600;color: green;
</div>
+
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">NVSE and related plugins must be manually installed because most mod managers assume everything in them needs to go into the "Data" folder instead of their respective specific locations.  Check their documentation carefully.</span>
 +
{{NVSE Configuration}}
 +
: See also entirety of the [[#Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu|Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu"]] in this guide.
 +
: For help interpreting an error log, please see the [http://wiki.nexusmods.com/index.php/How_to_read_most_Bethesda_game_error_logs How to read most Bethesda game error logs] wiki article.
 +
<br>
 +
: {{Lutana NVSE Plugin Status}}
 +
05. Did the mod need to be added to [http://www.nexusmods.com/newvegas/mods/42507/? Mod Configuration Menu (MCM)] / [http://www.nexusmods.com/newvegas/mods/44757/? One HUD (oHUD)] / [http://www.nexusmods.com/newvegas/mods/57174/? User Interface Organizer (UIO)]?  (Those mods need to see it when they are installed.  See the wiki article [http://wiki.nexusmods.com/index.php/HUD-UI-Menu_issues HUD-UI-Menu issues] and re-install them.)<br>
 +
06. Is your version of Windows 32 or 64-bit?  (32-bit may require BOOT.INI changes to use more than 2GB of memory.  See this [http://wiki.nexusmods.com/index.php/2-4GB_game_memory_limits_and_solutions 2-4GB game memory limits and solutions] article.)  FNV is a 32-bit game, so you need the 32-bit versions of any downloadable tools or libraries, like "C++ Runtimes" or "DirectX drivers" installed on your 64-bit system.  32-bit libraries are not interchangeable with 64-bit versions.  They install to different locations.  There is a reason MS makes both versions available.<br>
 +
07. Are you using a FNV4GB Loader such as [http://www.nexusmods.com/newvegas/mods/55061/? 4GB Fallout New Vegas Updated] or an LAA flag Patcher like [http://www.nexusmods.com/newvegas/mods/62552/? FNV 4GB Patcher]?  (Increases available memory.  But see the previous question about 32/64-bit Windows.  It's related.)  Did you turn off any "anti-virus" checking software before patching?  (They see any attempts to alter programs as "malware".)<br>
 +
: How can you tell if the 4GB Patch is working?
 +
: The [http://www.nexusmods.com/newvegas/mods/58277 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 the folder you moved it to, as you are going to have other problems down the road.  Please see the wiki "[http://wiki.tesnexus.com/index.php/Installing_Games_on_Windows_Vista%2B 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 Patch 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.<br>
 +
08. Are you using an [http://enbdev.com/index_en.html ENB] preset? (Alters the graphics environment, including INI changes.)  If you aren't sure, then probably not.  This is a "third party tool" you would have to manually add.  You should wait until you have a stable game before adding a "post-processor" like it to the mix.<br>
 +
09. Are you using [http://reshade.me/sweetfx Reshade/SweetFX]? (Alters the graphics environment, including INI changes.)  You should wait until you have a stable game before adding a "post-processor" like it to the mix.<br>
 +
10. Check the game graphic & ENB/SweetFX options do not conflict with video driver settings.  (Anti-aliasing, ambient occlusion, anisotropic sample size, v-sync, anything else that is mentioned.)  If you didn't install either of these then the question does do not apply.<br>
 +
11. Are you using [http://loot.github.io/ LOOT] to sort your mod "load order" (LO)?  (Reduces mod conflicts.)  If you don't like LOOT's results, or wish total control over your LO, see the wiki article [http://wiki.nexusmods.com/index.php/Load_order_and_you Load order and you] for an approach to organizing the LO and creating a "merge patch" file to manually resolve conflicts.<br>
 +
: 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 to put the LO in "Spoiler" tags. See the article [[#How_to_markup_images_(etc)_in_forum_posts_and_comments)|How to markup images (etc) in forum posts and comments]].)  Screenshots are not the best way to convey your LO, because they usually can't include everything in one image and (depending upon where you took the shot) may not show the actual "load order". [http://loot.github.io/ LOOT] 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.  Current [http://tes5edit.github.io/docs/index.html Tome of xEdit] online documentation here.) 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.
  
 +
12. Do you have more than 130 active plugins in your LO, or more than 140 plugins installed (active or not) in the game DATA folder? The game can have problems with anywhere from roughly 130-140 active, or too many installed, depending upon your system.  This may manifest in any number of strange ways to include apparent missing meshes and textures that were there before, along with CTDs.<br>
 +
13. If you are having a "red icon" problem, see the [[#ArchiveInvalidation (by Manager)|ArchiveInvalidation (by Manager)]] sub-topic.<br>
 +
:* When in doubt, it will never harm things to try toggling "ArchiveInvalidation" off and then on again.
 +
14. Are you missing any of the "game fixer" mods?  See the [[#Issue: Vanilla game bugs|Issue: Vanilla game bugs]] sub-topic for a list of specific recommendations.<br>
 +
15. If any LOD files (distant landscape terrain) have been added, re-run '''TES4LL''' (from [http://www.nexusmods.com/oblivion/mods/40549/? Nexus Oblivion] or [https://github.com/Gruftikus/tes4ll GitHub]).  ''''TES4LL''' is used to "fix up" LOD/VWD mesh files, and works along with [http://www.nexusmods.com/newvegas/mods/58562/? FNVLODGen].  The [http://web.archive.org/web/20170713081056/http://www.darkcreations.org/testg/wiki/Category:VWD-OB#TES4LL_process_sequence VWD/LOD Overview page] includes a basic batch file for assistance in automating the TES4LL process.  Edit in the following parameters in the "tes4ll_make_..." files for FNV: <div style="margin:0px 10px 10px 30px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;">... _gamemode=FalloutNV _worldspace=WastelandNV _worldspaceid=894758 _worldspaceidhex=000DA726 ...</div>
 +
:* A more recent alternative to '''TES4LL''' is [http://forum.step-project.com/topic/13451-xlodgen-terrain-lod-beta-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal/ xLODGen - Terrain LOD beta for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL] by '''sheson''', an updated version of the basic '''xLODGen''' tool (of which '''FNVLODGen''' is a game specific implementation) which now has the option to generate LOD meshes and textures "exactly" like the CK.  Read '''at least''' the first post instructions carefully.  Specifying an "output file" should be considered mandatory.<br>
 +
: See the [http://web.archive.org/web/20170713081056/http://www.darkcreations.org/testg/wiki/Main_Page TESTG] site for a glossary of terms and descriptions of/links to these and other utilities.
 +
16. If the LO has changed, re-run [http://www.nexusmods.com/newvegas/mods/58562/? FNVLODGen] after [https://loot.github.io/ LOOT].  (Rebuilds LOD quadrants (quads), which are "load order" dependent.)<br>
 +
17. Use [http://www.nexusmods.com/newvegas/mods/34703/? FNVEdit] (loading the entire LO) to check for Masters that are missing or loading after Dependencies.  See the wiki tutorial [http://wiki.nexusmods.com/index.php/Missing_Masters Missing Masters].  There is full documentation of FNVEdit (for both FO3 and FNV) in the online docs [http://tes5edit.github.io/docs/index.html Tome of xEdit] and the downloadable PDF [http://www.nexusmods.com/newvegas/mods/38413/? FNVEdit Training Manual].<br>
 +
18. Are you using a [http://www.nexusmods.com/newvegas/mods/35003/? Wrye Flash] Bashed Patch or a manually created "merge patch" file?  (Resolves record level conflicts.)  See [http://wiki.step-project.com/Guide:Merging_Plugins S.T.E.P. Merging Plugins Guide] which covers both approaches, or the video [https://www.youtube.com/watch?v=yq-fqpL5LqE Making a Merge Patch by Roy Batty] for the "merge up" approach.  (Use of "Mod Organizer" is not required.)  Use the [http://www.nexusmods.com/oblivion/mods/35230/? Wrye Bash Pictorial Guide] to quickly get functional with "Wrye Flash", which I think is the easier approach for a novice modder.<br>
 +
19. If you are using "Wrye Flash" to create a "Bashed Patch", have you gotten all "green" checkboxes for all your mods?  See the first post in the pinned thread [https://forums.nexusmods.com/index.php?/topic/2247404-fallout-new-vegas-beginners-guide-to-modding/ Fallout New Vegas Beginners guide to modding] by '''gromulos'''.<br>
 +
20. Was there an update to a mod that has been included in a "merged plugins" or "merge patch" file?  Rebuild the "merge" file.<br>
 +
21. Did any system or driver updates occur?  (Third party processes might be the cause if nothing else changed.)<br>
 +
22. Does your hardware meet the game's [http://www.systemrequirementslab.com/cyri/requirements/fallout-new-vegas/11035 minimum requirements]?<br>
 +
23. Have you tried running the game in "windowed mode"? This has been known to unexpectedly fix CTDs and "out of memory" errors on some older hardware.  If you prefer the "borderless" version of "windowed mode", install [http://nvse.silverlock.org/ New Vegas Script Extender (NVSE)] and use the [http://www.nexusmods.com/newvegas/mods/59266/? One Tweak for FNV] mod.<br>
 +
: Alternatively, there are free third-party tools that run games (not just FNV) in "borderless windowed mode", such as [https://github.com/Codeusa/Borderless-Gaming/releases Borderless Gaming].
 +
24. Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering.<br>
 +
25. Finally, the problem might be an overheating hardware component.  This usually shows up after a period of time which is typically fairly consistent but unpredictable as to when it manifests.  Try installing and keeping an eye on a temperature monitor, such as [http://www.almico.com/speedfan.php Speedfan] (freeware).  Your motherboard manufacturer probably has one available as well.  And it never hurts to clean out any dust collecting in the computer case.  Be sure to block any fans from rotating when you blow it out, so they don't send any unfiltered power surges through the system.
  
==Overview==
+
<span id="ArchiveInvalidation (by Manager)"></span>
Troubleshooting is a logical process of elimination.  If all logic fails, you have to revert back to a vanilla game and slowly re-install mods, testing each one thoroughly before adding the next.  It is a trade-off of "time" versus "effort".  Where that tipping point lies is up to you.  This is why you are always advised to follow a slow "install and test each mod one at a time" procedure when first setting up your game.  Then you know specifically which mod is causing your problem, which saves time.
 
  
==Checklist==
+
== ArchiveInvalidation ''by Manager'' ==
Standard list of things to ask yourself about your current FNV problem:
+
"ArchiveInvalidation" (AI) is a method by which the game is told to look for "loose files" in preference to those in the vanilla BSA files.  This is the reliable method to get a mod's own texture and mesh files utilized, assuming you have properly installed those "assets".  [https://forums.nexusmods.com/index.php?/topic/3538840-should-i-really-need-to-update-my-invalidation-file-by-hand/#entry31870835 This post on manual invalidation] explains the problem and history quite well.
  
# Are you getting an error message?  What is that pointing to as the source of the problem: the game, Steam, or Windows?
+
Check you have "ArchiveInvalidation" (AI) enabledYou may need to "toggle" it off and then on again.
# What most recently changed (as far as what you have deliberately done to your game is concerned: New, updated, or removed mods or plugins)?
 
# Try renaming both the INI files in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder, and let the game rebuild them.  (There might have been some unexpected changes.)
 
# Does the most recent mod change use [http://nvse.silverlock.org/ New Vegas Script Extender] (NVSE) or supplemental plugins like [http://www.nexusmods.com/newvegas/mods/58277/ JIP NVSE Plugin] or [http://www.nexusmods.com/newvegas/mods/55399/ Lutana NVSE Plugin]?  Check that log (in the game's root folder: i.e. "<Steam install path>\steamapps\common\FalloutNV").
 
#* In the folder "Data\NVSE" create a new text file and name it "nvse_config.ini".  (This is not created when you install NVSE.)
 
#* Make sure "hide known file types" is disabled in Windows Explorer's folder options, or it will have a hidden ".txt" extension which you don't want.
 
#* Copy and paste the following into it:
 
#:<pre>
 
#:: [Logging]
 
#:: EnableGameErrorLog=1
 
#:</pre>
 
#: This will enable the game's error log the next time you run it, which will then be found in your FNV root folder (where you put the NVSE executable files).  There will be two files: "falloutnv_error.log" and "falloutnv_havok.log".  The first one is very useful for finding broken stuff in mods or the cause of crashes.  Not everything in it is an error so keep that in mind; some are just warnings.
 
# Did the mod need to be added to MCM/oHUD/UIO?  (Those mods need to see it when they are installed.  See the wiki article [http://wiki.nexusmods.com/index.php/HUD-UI-Menu_issues HUD-UI-Menu issues] and re-install them.)
 
# Is your version of Windows 32 or 64-bit?  (32-bit may require BOOT.INI changes to use more than 2GB of memory.  See this [http://wiki.nexusmods.com/index.php/2-4GB_game_memory_limits_and_solutions 2-4GB game memory limits and solutions] article.)
 
# Are you using a [http://www.nexusmods.com/newvegas/mods/55061 FNV4GB Loader]?  (Increases available memory.  But see the question about 32/64-bit Windows.  It's related.)
 
# Are you using an [http://enbdev.com/index_en.html ENB] preset? (Alters the graphics environment, including INI changes.)
 
# Are you using [http://reshade.me/sweetfx Reshade/SweetFX]? (Alters the graphics environment, including INI changes.)
 
# Check the game graphic & ENB/SweetFX options do not conflict with video driver settings.  (Anti-aliasing, ambient occlusion, anisotropic sample size, v-sync, anything else that is mentioned.)
 
# Are you using [https://loot.github.io/ LOOT] to sort your mod "load order" (LO)?  (Reduces mod conflicts.)  If you don't like LOOT's results, or wish total control over your LO, see the wiki article [http://wiki.nexusmods.com/index.php/Load_order_and_you Load order and you] for an approach to organizing the LO and creating a "merge patch" file to manually resolve conflicts.
 
# Do you have more than 130 active plugins in your LO, or more than 140 plugins installed (active or not) in the game DATA folder? The game can have problems with anywhere between 130-140 active, or too many installed, depending upon your system.  This may manifest in any number of strange ways to include apparent missing meshes and textures that were there before, along with CTDs.
 
# If you are having a "texture" problem, see the [[#ArchiveInvalidation (by Manager)|ArchiveInvalidation (by Manager)]] sub-topic.
 
#* When in doubt, it will never harm things to try toggling "ArchiveInvalidation" off and then on again.
 
# Are you missing any of the "game fixer" mods?  See the [[#Issue: Vanilla game bugs|Issue: Vanilla game bugs]] sub-topic for a list of specific recommendations.
 
# If any LOD files (distant landscape terrain) have been added, re-run [https://github.com/Gruftikus/tes4ll TES4LL].  (See the [http://www.darkcreations.org/testg/wiki/Main_Page TESTG] site for a glossary of terms and descriptions of/links to utilities.)
 
# If the LO has changed, re-run [http://www.nexusmods.com/newvegas/mods/58562/? FNVLODGen] after LOOT.  (Rebuilds LOD quadrants (quads), which are "load order" dependent.)
 
# Use [http://www.nexusmods.com/newvegas/mods/34703/? FNVEdit] (loading the entire LO) to check for Masters that are missing or loading after Dependencies.  See wiki tutorial [http://wiki.nexusmods.com/index.php/Missing_Masters Missing Masters].
 
# Are you using a [http://www.nexusmods.com/newvegas/mods/35003/? Wrye Flash] Bashed Patch or a manually created "merge patch" file?  (Resolves record level conflicts.)  See [http://wiki.step-project.com/Guide:Merging_Plugins S.T.E.P. Merging Plugins Guide] which covers both approaches.  (Use of "Mod Organizer" is not required.)  Use the [http://www.nexusmods.com/oblivion/mods/35230/? Wrye Bash Pictorial Guide] to quickly get functional with "Wrye Flash", which I think is the easier approach for a novice modder.
 
# If you are using "Wrye Flash" to create a "Bashed Patch", have you gotten all "green" checkboxes for all your mods?  See the first post in the pinned thread [https://forums.nexusmods.com/index.php?/topic/2247404-fallout-new-vegas-beginners-guide-to-modding/ Fallout New Vegas Beginners guide to modding] by gromulos.
 
# Was there an update to a mod that has been included in a "merged plugins" or "merge patch" file?  Rebuild the "merge" file.
 
# Did any system or driver updates occur?  (Third party processes might be the cause if nothing else changed.)
 
# Does your hardware meet the game's [http://www.systemrequirementslab.com/cyri/requirements/fallout-new-vegas/11035 minimum requirements]?
 
# Did you install Steam under the default location of the "C:\Program Files" tree?  This causes many "strange" problems not otherwise explainable.  As painful as it may sound, read the wiki article [http://wiki.nexusmods.com/index.php/Installing_Games_on_Windows_Vista%2B  Installing Games on Windows Vista+] and move at least FNV.  That article has a link to the official Steam Procedure.
 
# Finally, the problem might be an overheating hardware component.  This usually shows up after a period of time which is typically fairly consistent but unpredictable as to when it manifests.  Try installing and keeping an eye on a temperature monitor, such as [http://www.almico.com/speedfan.php Speedfan] (freeware).  Your motherboard manufacturer probably has one available as well.
 
  
== ArchiveInvalidation (by Manager) ==
+
(For links to tutorials and documentation for the individual mod managers, please see the '[http://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice#Mod_Managers Mod Managers]' section of the wiki "[http://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice FNV General Mod Use Advice]" article.)
"ArchiveInvalidation" is a method by which the game is told to look for "loose files" in preference to those in the vanilla BSA files.  This is the reliable method to get a mod's own texture and mesh files utilized, assuming you have properly installed those "assets".  [https://forums.nexusmods.com/index.php?/topic/3538840-should-i-really-need-to-update-my-invalidation-file-by-hand/#entry31870835 This post] explains the problem and history quite well.
 
  
Check you have "ArchiveInvalidation" enabled.  You may need to "toggle" it off and then on again.
 
 
* Open your mod manager.
 
* Open your mod manager.
:* [http://www.nexusmods.com/newvegas/mods/42572/ Mod Organizer] (MO): Select your "Profile".  Turn on "Automatic Archive Invalidation" in the "Configure Profiles" dialog.  Close the mod manager.
+
:* [http://www.nexusmods.com/newvegas/mods/42572/ Mod Organizer (MO)]: Select your "Profile".  Turn on "Automatic Archive Invalidation" in the "Configure Profiles" dialog.  Close the mod manager.
:* [http://www.nexusmods.com/newvegas/mods/36901/ Fallout Mod Manager] (FOMM): Depending on the version you have, find "Archive Invalidation" either under the tools tab or find the button "Toggle Archive Invalidation".
+
:: Some have found "AI" more difficult to get working in MO.  In these cases the following steps are suggested:
:* [http://www.nexusmods.com/newvegas/mods/modmanager/ Nexus Mod Manager] (NMM) or the newer [http://www.nexusmods.com/newvegas/mods/54991/ Fallout Mod Manager - Forked] (FOMM): if there is a "check mark" shown next to "Archive Invalidation", remove it and close the mod manager.  Open the mod manager, open the "Tools" and place a "check mark" next to "Archive Invalidation".
+
::1. In MO Settings 'Workarounds': uncheck 'Force-enable game files'.
 +
::2. Get a copy of "Fallout - AI!.bsa" (From FOMM or NMM) and copy it to your "Data" directory.  (Basically this is an empty BSA file.)
 +
::3. Go to the 'Archives' tab in the right MO window. Make sure MO is managing BSA files. Move the "Fallout - AI!.bsa" to the top of the list.
 +
::4. Try "Automatic Archive Invalidation" in the Profile both OFF and ON.
 +
:* [http://forum.step-project.com/forum/102-mod-organizer-2-support/ MO2 Support] STEP Forum.  [http://forum.step-project.com/topic/13308-mo-or-mo2-for-fnv/ Recommendations] are mixed regarding it's use with FNV.
 +
::* [http://www.youtube.com/watch?v=DG3eqyNOByw Mod Organizer 2 Installation and Settings] Video 1 of 5 by '''GamerPoets'''.
 +
:* [http://www.nexusmods.com/newvegas/mods/36901/ Fallout Mod Manager (FOMM)]: Depending on the version you have, find "Archive Invalidation" either under the tools tab or find the button "Toggle Archive Invalidation".
 +
:* [http://www.nexusmods.com/newvegas/mods/modmanager/ Nexus Mod Manager (NMM)] or the newer [http://www.nexusmods.com/newvegas/mods/54991/ Fallout Mod Manager - Forked (FOMM-Forked)]: if there is a "check mark" shown next to "Archive Invalidation", remove it and close the mod manager.  Open the mod manager, open the "Tools" and place a "check mark" next to "Archive Invalidation".
 
:*: If there is not a "check mark" next to "Archive Invalidation", place one there and close the mod manager.
 
:*: If there is not a "check mark" next to "Archive Invalidation", place one there and close the mod manager.
:* [http://www.nexusmods.com/newvegas/mods/35003/ Wrye Flash] (WF): click on the "Installers" tab, then right-click on the "Package" column header (gray bar) and click to place a "check mark" on the "BSA Redirection" context menu entry.  Then right-click on the "Package" column header again and select "Anneal All".
+
:* [http://www.nexusmods.com/site/mods/1?tab=files Vortex]: the new "official" Nexus mod manager handles "Archive Invalidation" with an '''''extension''''' called "Gambryo Archive Invalidation".  It's enabled when '''Vortex''' is installed, and it works automatically for certain '''Bethesda''' games.
 +
:: It now has a dedicated button on the '''Vortex''' dashboard.
 +
 
 +
:: Per the author '''Tannin''' [http://forums.nexusmods.com/index.php?/topic/6685182-is-there-a-archive-invalidation-button-in-vortex/#entry62183357 here]:
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 50px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">For the newer games [Curator: Creation Engine based], "Archive Invalidation" is relatively simple, you just have to change the date of the original BSAs. '''Vortex''' will give you a notification when you have to do that and it may appear again if the game was updated or something else changed the date of the files again.
 +
 
 +
For the older games (prior to Skyrim) [Curator: Gamebryo Engine based] a BSA redirection plugin has to be installed. This can be done from '''settings->workarounds''' or from the dashboard (if you haven't removed the button already).
 +
 
 +
Please note that this will create a new mod called "Vortex Archive Invalidation". You can disable or remove that mod like any other but for invalidation to work you should keep it enabled on every profile.
 +
</div>
 +
:: Note that '''Vortex''' is now in "Production Release" state, meaning it is "stable", "feature complete", and "bug free" for the majority of users, but bugs may still be found and dealt with.  See the [http://www.nexusmods.com/news/14078 Nexus news article] for details.  Please report problems to the [http://forums.nexusmods.com/index.php?/forum/4301-vortex/ Vortex Forum].
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 50px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Thanks to user '''browniefox''' for the basis of the following.
 +
: Adding '''Vortex''' ''ArchiveInvalidation'' for older '''Gamebryo engine''' games:
 +
# Download your mod with replacement files, choose '''Options''' (ignore the "failure to validate" part at the start: just tick the box and choose your preferences) and '''Enable'''.  (This is an optional step, but without such a mod installed you won't see the effect of adding AI in the last step.)
 +
# Go to '''Settings''', click '''Workarounds''', and click the 'BSA Redirection' (the type of AI) option 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 (the "BSA redirection plugin" mentioned by '''Tannin''' above). It doesn't do the "Archive Invalidation" check automatically, and you do NOT need to repeat this step again when you add future mods.)
 +
# Go back to your '''Mods''' tab. Find '''Vortex Archive Invalidation''' on the dashboard. "Disable" and then "Enable" it (or vice versa. Just make sure you turn it "off" and then leave it "on" again).
 +
# You're done. You just did the "Archive Invalidation" toggle (in Step 3). In the top right a blue box should come up that whizzes through all your mods (this is the AI check).
 +
</div>
 +
:* [http://www.nexusmods.com/newvegas/mods/35003/ Wrye Flash (WF)]: click on the "Installers" tab, then right-click on the "Package" column header (gray bar) and click to place a "check mark" on the "BSA Redirection" context menu entry.  Then right-click on the "Package" column header again and select "Anneal All".
 
* If you don't use a "mod manager", you should.  But there are mods out there that provide the same "BSA Redirection" functionality (the currently more effective form of "ArchiveInvalidation") as an addon.
 
* If you don't use a "mod manager", you should.  But there are mods out there that provide the same "BSA Redirection" functionality (the currently more effective form of "ArchiveInvalidation") as an addon.
* For other texture problems, see the [http://www.darkcreations.org/testg/wiki/Troubleshooting TESTG Troubleshooting] section.
+
* If a mod manager's AI doesn't seem to be working, check the INI files under "[Archive]" for the "bInvalidateOlderFiles=" setting.  Try switching the value between "=0" and "=1".  (Some seem to need it one way, and others the opposite.)  See also the wiki article [[Archive_invalidation|Archive invalidation]] for details on where the "fake bsa" file needs to go in the "sArchiveList=" line.
 +
* Note that various mod managers can implement "BSA Redirection" in the same way, but be using different BSA filenames.  This filename gets inserted in the INI files (under the "[Archive]" section in the "sArchiveList=" setting string of files) using variation names such as "Fallout - AI!.bsa", "Fallout - ArchiveInvalidation.bsa", etc.  If you switch mod managers, make sure your INI files are using the correct filename as that manager is expecting.  In general this file is placed first or second in the "sArchiveList=" list.
 +
 
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 30px;border:1px dashed #DAA520;
 +
color: red; background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Do not attempt to use the ArchiveInvalidation mechanism from more than one mod manager at a time.  That will cause all kinds of confusion.</div>
 +
 
 +
: If you are using the [http://www.nexusmods.com/newvegas/mods/58277 JIP LN NVSE Plugin] optional "FalloutCustom.ini" file to override the standard INI file settings, make sure it has been changed as well.
 +
* For other texture problems, see the [http://web.archive.org/web/20170713081056/http://www.darkcreations.org/testg/wiki/Troubleshooting TESTG Troubleshooting] section.
  
 
== Mod Conflict Isolation ==
 
== Mod Conflict Isolation ==
If you have to isolate a mod conflict, try first "disabling" half your mods, and testing.  If the problem disappears, then you know the mod conflict lies in the "disabled" half of the mods.  Re-enable half of those "disabled" mods while disabling the other (previously enabled) half, and test.  Keep repeating this "halving" process until you have narrowed down the mod that causes the problem only when it is active.  This is the quickest way to isolate a problem mod.
+
If you have to isolate a mod conflict, try first "disabling" half your mods, and testing.  If the problem disappears, then you know the mod conflict lies in the "disabled" half of the mods.  Re-enable half of the "disabled" half of the mods (i.e. now down to 1/4 of the total) while disabling the entirety of the other (previously enabled) half, and test.  Keep repeating this "halving the remainder" process until you have narrowed it down to the mod that causes the problem only when it is active.  This is the quickest way to isolate a problem mod.
 +
 
 +
Whenever you "disable/deactivate/uninstall" a mod, make a "clean save" file before testing the result.  For FNV a "clean save" from an existing game save seems to be just a "full save" file (not a "quick save") that has been loaded, displayed the "missing content" message for the disabled plugin(s), and you continued on into the game; and then waiting about 10 seconds for scripts to initialize before saving again.  This is a minimal clean save procedure.  (If you appear to still have "residue" remaining after trying this procedure, try the more complete process laid out in the [http://www.uesp.net/wiki/Tes4Mod:Clean_Save Tes4Mod:Clean_Save procedure] for '''Oblivion'''.)  However, it is usually preferable to test using a "new" game "full save" file from just after you create a "new" character with a different name.  This avoids the possible issue of any corruption or problems "burned into" the save file.
 +
: Please see also the 'Fourth Rule: Reloading "save game" files' section of the wiki [[#FNV_General_Mod_Use_Advice | FNV General Mod Use Advice]] article.
  
 
If disabling mods does not pin down the culprit, then you have to uninstall them to completely remove their influence, because they overwrote something which is causing the problem.  You can use the same "halving" technique but often it will be quicker to just uninstall everything and start over from a "vanilla" game that you have tested has no problems.
 
If disabling mods does not pin down the culprit, then you have to uninstall them to completely remove their influence, because they overwrote something which is causing the problem.  You can use the same "halving" technique but often it will be quicker to just uninstall everything and start over from a "vanilla" game that you have tested has no problems.
  
If you un-installed and re-installed the game but even without mods it crashes on startup, likely you forgot to clear out your "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder.  The game places your specific versions of the Fallout and Fallout_prefs INI files there, along with your "save games".  Try renaming the "Users" folder INI files first.  Then if that fails move the "saves" elsewhere, delete that FalloutNV folder's content, and re-install again.  If you have to re-install again anyway, be sure to install to a folder that is not under the default "C:\Program Files" folder tree.  See [http://wiki.nexusmods.com/index.php/Installing_Games_on_Windows_Vista%2B Installing Games on Windows Vista+] for the rationale and guidance.
+
If you uninstalled and re-installed the game but even without mods it crashes on startup, likely you forgot to clear out your "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder.  The game places your specific versions of the '''Fallout''' and '''FalloutPrefs''' INI files there, along with your "save games".  Try renaming the "Users" folder INI files first.  I usually just add to the extension: from "<filename>.ini" to "<filename>.ini.old", but it can be anything.  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.  Then if that fails: move the "saves" elsewhere, delete that FalloutNV folder's content, and re-install again.  If you have to re-install again anyway, be sure to install to a folder that is not under the default "C:\Program Files" folder tree.  See [http://wiki.nexusmods.com/index.php/Installing_Games_on_Windows_Vista%2B Installing Games on Windows Vista+] for the rationale and guidance. (Actually, you should move your game from the default location regardless, but I realize this is unwelcome advice to most people.  It is still the single best "fix" you can do for yourself.  Read that article.)
  
 
When the above is not sufficient to resolve your problem, please report what steps you have tried so we don't waste time suggesting you repeat something.  In such cases, report the actual steps: not just "I followed the guide".  We need to know you didn't miss or misinterpret something.
 
When the above is not sufficient to resolve your problem, please report what steps you have tried so we don't waste time suggesting you repeat something.  In such cases, report the actual steps: not just "I followed the guide".  We need to know you didn't miss or misinterpret something.
  
It's always useful to post your Load Order (in "Spoiler" tags.  Use the "Special BBCode" button in the Forum "Reply" menu bar).  Screenshots are not the best way to convey your LO, because they usually can't include everything in one image.  [https://loot.github.io/ LOOT] 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.
+
It's always useful to post your Load Order (in "Spoiler" tags.  Use the "Special BBCode" button in the Forum "Reply" menu bar, just to the left of the "Fonts" pick-list).  Screenshots are not the best way to convey your LO, because they usually can't include everything in one image and make it difficult to determine if you have too many plugins.  [https://loot.github.io/ LOOT] 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".
  
==Towards Game Stability==
+
== Towards Game Stability ==
 +
* The videographer '''GamePoets''' has recently (30 Oct 2018) released a definitive 12:11 minute [http://www.youtube.com/watch?v=KkVWoccWoXY 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 works just as well for FNV, it also does not cover quite as many options.  It does make an excellent and recommended starting point for initially dealing with such issues.
  
* 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.
+
* 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, and test it thoroughly immediately.
 +
 
 +
* 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, the popular 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.  The general rule is: NEVER remove a mod from your load order once you have it in a "save game" file unless you are prepared to start over at some (possibly considerably) later point.
  
 
* Do not use the game's "auto-save" feature.  See the sub-topic [[#Issue: CTD on interior/exterior/"fast travel" cell change|Issue: CTD on interior/exterior/"fast travel" cell change]] for the explanation and alternatives.
 
* Do not use the game's "auto-save" feature.  See the sub-topic [[#Issue: CTD on interior/exterior/"fast travel" cell change|Issue: CTD on interior/exterior/"fast travel" cell change]] 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" techniqueSuch mods usually point this out in their descriptionBut it is something to pay attention to when experimentingIt's better to find out what causes problems before you start to play in earnest.
+
=== NVSE Installation issues ===
 +
If you are having a problem installing '''NVSE''' with your mod manager, first of all: DON'T!  Install it manually to the "game root" folder.  (This point is where mod managers get it wrong.)  But if you installed it manually and still wonder if you did it correctly, here is where the various (original "[http://nvse.silverlock.org/ Silverlock]") files belong.  The later, forked "[https://github.com/xNVSE/NVSE xNVSE]" version (v6.x.x and later) may include or move other files, but for "backwards compatibility" should keep these files in the same location.
 +
 
 +
:* In the "game root" folder (where '''FalloutNV.exe''' resides):
 +
::* ''nvse.log'' (only once NVSE is successfully used.)
 +
::* ''nvse_1_4.dll''
 +
::* ''nvse_1_4ng.dll'' (when installed after the [https://geckwiki.com/index.php?title=Garden_of_Eden_Creation_Kit GECK].)
 +
::* ''nvse_editor.log'' (only once NVSE is successfully used with the '''GECK'''.)
 +
::* ''nvse_editor_1_4.dll'' (when installed after the '''GECK'''.)
 +
::* ''nvse_extender.log'' (only once NVSE is successfully used with the [https://www.nexusmods.com/newvegas/mods/64888 GECK Extender] mod.)
 +
::* ''nvse_extender_ng.log'' (only once NVSE is successfully used with the '''GECK Extender'''.)
 +
::* ''nvse_loader.exe'' (use instead of '''FalloutNV.exe''' to launch the game if you haven't run [http://www.nexusmods.com/newvegas/mods/62552 FNV 4GB Patcher].  Once patched, use '''FalloutNV.exe''' as usual.)
 +
::* ''nvse_loader.log'' (only once NVSE is successfully launched.)
 +
::* ''nvse_readme.txt''
 +
::* ''nvse_steam_loader.dll'' (only needed by the Steam version of FNV.)
 +
::* ''nvse_whatsnew.txt''
 +
 
 +
:* In the "Data\NVSE" folder (various files other than '''nvse_config.ini''' are optional; some may not be present by default):
 +
::* ''nvse_config.ini''
 +
::* ''nvse_config.testAnim''
 +
::* ''nvse_plugin_geckpu_ew.ini'' (from the older [https://www.nexusmods.com/newvegas/mods/41642 Geck 1.4 PowerUp] mod.  Not used with '''GECK Extender'''.)
 +
::* ''TestAnim.txt''
 +
 
 +
:* Everything else belongs under "Data\NVSE\Plugins" and it's sub-folders.  When in doubt, just use the folder structure and files under each folder you find in the archive file.
 +
:* If you ran the '''FNV 4GB Patcher''' before installing '''NVSE''', you may need to re-run the '''patcher''' so it will detect that '''NVSE''' has now been installed.
 +
 
 +
== Solutions to Starting the game problems ==
 +
 
 +
<span id="Issue: After moving game from the default install location, FNV4GB fails to launch"></span>
 +
=== Issue - After moving game from the default install location FNV4GB fails to launch ===
 +
The '''FNV4GB.log''' looks similar to the following when trying to launch it:
 +
<div name="Simulated code box" class="boilerplate metadata" id="Warning Notice"
 +
style="margin:0px 10px 10px 30px; border:1px dashed #DAA520; color: lightgray; background-color:#333333; padding:3px;
 +
/* Remove the next four 'white-space' lines to restore default white-space processing. */
 +
white-space: pre-wrap;      /* css-3 */
 +
white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
 +
white-space: -pre-wrap;      /* Opera 4-6 */
 +
white-space: -o-pre-wrap;    /* Opera 7+ */
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">
 +
# Loader: Getting windows version - 6.2.9200
 +
# Loader: Address Space Size = 0xFA5D1000
 +
# Loader: Getting executable name - D:\Games\Steam Library\steamapps\common\Fallout New Vegas\fnv4gb.exe
 +
# Loader: Parsing Command Line...
 +
# Loader: Trying to get game path from Bethesda Softworks registry key
 +
# Loader: Attempting to open HKLM\SOFTWARE\Bethesda Softworks\FalloutNV - Failed
 +
# Loader: Trying to get game path from Steam registry key
 +
# Loader: Attempting to open HKLM\SOFTWARE\Valve\Steam - Succeeded
 +
# Loader: Attempting to query size of "InstallPath" value - Succeeded
 +
# Loader: Attempting to query "InstallPath" value - Succeeded
 +
# Loader: Changing directory to C:\Program Files (x86)\Steam\steamapps\common\fallout new vegas
 +
# Loader: Unable set current dir to game dir. - The system cannot find the file specified.</div>
 +
: The "Executable name" (3rd line) points to the correct location. The registry key "HKLM\SOFTWARE\Valve\Steam" value "InstallPath" (9th line; value content shown in 11th line) does not.
 +
 
 +
* Cause: The registry has not been properly updated.
 +
:* Solution: Running the vanilla EXE launcher (from the Steam Client or 'FalloutNVLauncher.exe') first after moving (at least once) updates the registry addresses.  After that FNV4GB will work correctly.
 +
 
 +
<span id="Issue: Application load Windows error(s)"></span>
 +
=== Issue - Application load Windows errors ===
 +
*Cause-1: Specifically error codes: "P:0000065432" or "5:0000065434" indicatea problem with the '''Steam Client'''.
 +
 
 +
:The "P:" prefix seems to show up when the '''Steam Client''' is not running.
 +
:The "5:" prefix appears to occur when starting the game from it's EXE (such as the Launcher or the "FalloutNV.EXE"), but then it fails to locate the '''Steam Client''' executable on local disk even though it is already running and loaded into memory. Which seems to be confirmed as it disappears when the '''SteamClient.exe''' (and only that one file) is placed in the game root folder.
 +
:Both instances produce the same "error code" message with only the prefix different.
 +
 
 +
:
 +
:*Solution-1a: The '''Steam Client''' may be in "Offline" mode and minimized to the system tray, but must remain running while launching the game, even with "nvse_launcher" or "fnv4gb". 
 +
::Note that the '''Steam Client''' is what displays the "Library", "Store", etc. It is a separate piece of software from "the game" and performs the authentication that your copy of the game is legitimate. 
 +
 
 +
:
 +
:*Solution-1b: Sometimes all that is needed is to open the "Task Manager" (<Ctrl+Alt+Del> or right-click on the "Task Bar" | "Start Task Manager"), switch to the "Processes" tab, and right-click the "image name" '''Steam.exe''' task and select "End Process Tree". Then restart the game again. 
 +
 
 +
:
 +
:*Solution-1c: When this occurs with the "FalloutNVLauncher.exe" file (whether or not after installing NVSE), some people have found that '''COPYing''' the '''Steam.EXE''' file (usually located in the "<install path>\Steam\" folder), into the game root folder (i.e. along with the game and NVSE EXE files in "<install path>\SteamLibrary\steamapps\common\Fallout New Vegas"), resolves the problem.&nbsp; This copy of '''Steam.EXE''' may need to be updated as well after the '''Steam Client''' has updated. 
 +
 
 +
*Cause-2: For some people, the game will not run without "Multi-threaded AI" enabled.  
 +
 
 +
:
 +
:*Solution-2: In all three INI files, under the "[General]" section set the following values:  
 +
::<pre>bUseThreadedAI=1</pre>
 +
 
 +
 
 +
&nbsp;
 +
 
 +
:
 +
::and add the line:
 +
::<pre>iNumHWThreads=</pre>
 +
 
 +
 
 +
and set that to however many cores your processor has. Note this added line is not a "performance" tweak (the game does multi-threading by default and the "iNumHWThreads=" setting may restrict it) and is not recommended for everyone in general. Some people have experienced adverse effects. Use with caution and test the result. When in doubt, start with "2".
 +
 
 +
*Cause-3: Error message "Application was unable to start correctly", and Windows "Event Viewer" '''Application''' Error: "Exception code: 0xc0000005".
 +
 
 +
:Generally this error code means the program is trying to access protected memory or outside of the space allocated to it. It's one of the most common OS errors seen. In this case the game is failing to start as a result.
 +
:*Solution-3a: The Nov 2016 Win10 updates should fix any WDDK based issues with video drivers or previous updates. Try applying system updates first.
 +
:*Solution-3b: See the article [http://www.errorlive.com/exception-code-0xc0000005 Exception Error Code 0xc0000005 Fixed on Windows 7 & 10].
 +
:*Solution-3c: See the article [http://www.eassos.com/how-to/fix-error-code-0xc0000005.php How to fix error code 0xc0000005] under "application was unable to start correctly" for other things to do to fix it. 
 +
:*Solution-3d: The mod [http://www.nexusmods.com/newvegas/mods/66537 New Vegas Tick Fix (NVTF)] was developed to correct specific problems encountered with Windows 10 as an alternative to the older "New Vegas Stutter Remover (NVSR)".  Among it's NVTF.INI file settings is the entry "bInlineCommonFunctions=".  Some have reported that disabling this entry ("=0") corrects this specific error, particularly if it occurs after the game has started.
 +
 
 +
*Cause-4: Error message "The application was unable to start correctly (0xc000007b)" has several possible causes. The [http://www.tomshardware.com/faq/id-3114816/solve-windows-error-0xc000007b.html TomsHardWare] site has a good list of these. But when the problem only occurs with FNV on a Windows 10 or later system, the most likely reason is due to the age of the game. At the time it was released, the game was designed to look for DirectX9 files with specific versions in the file names. Later versions of DirectX might be "backwards compatible", but the file names are not the same and the game does not recognize them as being equivalent.
 +
 
 +
:
 +
:*Solution-4a: Please see "Cause-1" in the [[#Issue:_Vanilla_game_Hangs_on_startup|Issue: Vanilla game Hangs on startup]] section. 
 +
 
 +
*Cause-5: Generally this only applies if you are unable to get the game to start at all, ever. If it had been running but suddenly starts failing for no apparent reason, most likely it is due to something on the OS side that recently changed: a Windows Update, or a new video/ mouse/ sound/ keyboard driver. See also: [[#Issue:_CTD_after_10-20_minutes_of_play_.28post-Win10_2017_FCU.29|Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)]].
 +
 
 +
:It is common advice to update video drivers, but manufacturers often stop testing for older game compatibility. Experience suggests you only update drivers when necessary to resolve a specific problem, and be prepared to "rollback" to an older driver version. Keep at least one version that is known to work "in reserve".
 +
:*Solution-5a: If running the game in '''online mode''' through '''Steam''', Set/Change Steam Compatibliity: 
 +
::
 +
::#Run the '''Steam Client''' and login '''online'''.
 +
::#Right-click on the '''Steam Icon''', choose '''Properties''', and if it is on, turn '''Compatibility off'''.
 +
::#Close out '''Steam Client''' entirely.
 +
::#Open '''Steam''' again it and attempt to load the game.   
 +
 
 +
:
 +
:*Solution-5b: If running the game in '''offline mode''' by launching from your computer desktop, or if setting "Steam Compatibliity" is not sufficient, Set/Change Windows Compatibility: 
 +
::
 +
::*Note that the Windows 10 "Fall Creator's Update" (FCU, v1709; aka "RedStone 3") reportedly no longer requires this compatibility setting.   
 +
::#Right-click on the ''Fallout: New Vegas'' launcher application (FalloutNVLauncher.exe) in the game root folder. (This is ''C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas'' (by default), but that location is not recommended. Please see the wiki [[Installing_Games_on_Windows_Vista+|Installing Games on Windows Vista+]] article for why not and help on moving it.)
 +
::#Select '''Troubleshoot Compatibility'''.
 +
::#Choose the '''Troubleshoot Compatibility''' option.
 +
::#Check the box that says '''The Program requires additional permissions'''.
 +
::#Select '''Yes''' for the next window and then '''Test the Program'''.
 +
::#Choose '''Save these settings'''.
 +
::#Try to launch the game from your desktop again.
 +
 
 +
<span id="Issue: Black Screen on startup"></span>
 +
 
 +
=== Issue - Black Screen on startup ===
 +
* Cause-1: Usually if the game "freezes" but doesn't CTD during the loading screens, it's due to a missing or incorrectly referenced "master file".  Usually this is a file with an ESM extension, but less commonly might be one with an ESP extension.  (It is a "flag" internally in the file header that makes a file a "master"; not the extension.)
 +
:: A "missing master" problem can result just from a plugin being in the wrong sequence in the "load order".
 +
 
 +
:* Solution-1: Use [http://www.nexusmods.com/newvegas/mods/34703/? FNVEdit] (loading the entire LO) to check for Masters that are missing or loading after Dependencies.  See the wiki article [http://wiki.nexusmods.com/index.php/Missing_Masters Missing Masters] for more detailed instructions.
 +
 
 +
:: 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:
 +
::* FalloutNV.ESM
 +
::* DeadMoney
 +
::* HonestHearts
 +
::* OldWorldBlues
 +
::* LonesomeRoad
 +
::* GunRunnersArsenal
 +
::*: and then the "pre-order packs":
 +
::* ClassicPack
 +
::* MercenaryPack
 +
::* TribalPack
 +
::* CaravanPack
 +
 
 +
:: Mod EMS files should follow.
 +
 
 +
:: Use [https://loot.github.io/ LOOT] to get a basic sorted mod order.  Note that some mods have ESMs that use the ESP extension, so if LOOT sorts them into the ESM group, leave them as it is determining that from the file headers and they really are flagged as ESMs.
 +
 
 +
* Cause-2: A Black screen but you can hear sounds and the game seems to be running usually means you have too many plugins active.  You can start to have problems anywhere with between 130-140 active plugins depending upon your system.  Here "plugins" refers to both ESM and ESP files that are active in your "load order", ''or present in the game "Data" folder even if not active''.
 +
 
 +
:* Solution-2: Try temporarily disabling enough plugins to get under the cap and see if that gets your screen back.  If so, then you need to look into permanently reducing the active plugin count by means of a "bashed" or "merged" patch file, and "merged plugin" files.  See the wiki article [http://wiki.nexusmods.com/index.php/Merged_Plugin_Guidelines_for_Personal_Use Merged Plugin Guidelines for Personal Use] where the subject is discussed.
 +
 
 +
* Cause-3: A Black screen but you can hear sounds and the game seems to be running could mean you have corrupted a HUD-UI-Menu XML file, or have installed a mod that overwrites oneThis can usually be confirmed by loading the game without any active mods or "save game" (i.e start a new game).  If the screen remains black, you have an XML file issue.
 +
 
 +
:* Solution-3: See the wiki article [http://wiki.nexusmods.com/index.php/HUD-UI-Menu_issues HUD-UI-Menu issues].
 +
 
 +
* Cause-4: A Black screen with CTD (or hang) during the loading screens is usually an indication of a mod conflict or a dependent plugin (i.e. an ESP) loaded before a master plugin (i.e. ESM for the same mod).    See the wiki article [http://wiki.nexusmods.com/index.php/Missing_Masters Missing Masters] for more detailed instructions to check for these problems.
 +
 
 +
:* Solution-4a: Check the date/timestamp on the files in question.  Even [https://loot.github.io/ LOOT] can occasionally set the times too close to each other when sorting.  They need to have at least a full minute difference to not be considered "the same time" by the game.  The ESP must have a later time than it's related ESM.  You can use a "file properties" tool like [https://www.petges.lu/home/ Attribute Changer] (freeware) to manually adjust any or all three timestamps (created, modified, accessed) on the files, or try manually moving files around in your mod manager.  Note that no two files should have the same "modified" date/timestamp in your "load order" or other problems will arise.
 +
 
 +
:* Solution-4b: To isolate a mod conflict, see the [[#Mod Conflict Isolation|Mod Conflict Isolation]] sub-topic.
 +
 
 +
:* Solution-4c: Installing HUD-UI-Menu mods in the wrong order can cause corruption of an XML file in a form of "mod conflict".  Please see the wiki "[http://wiki.nexusmods.com/index.php/HUD-UI-Menu_issues HUD-UI-Menu issues]" article.
 +
 
 +
* Cause-5: A Black screen during the game loading screen with the rotating roulette wheel, and no sound might be a problem with the audio driver.
 +
 
 +
:* Solution-5: Locate the sound card or integrated audio device driver for your version of Windows on the vendor site and re-install.  (These are often different from those available from "Microsoft Updates".)
 +
 
 +
<span id="Issue - ReinstallFreeze"></span>
 +
=== Issue - Game freezing on launch after re-install ===
 +
: Thanks to Kitty Black (Purr4me) for the basis of the following in a reply to the Nexus Fallout New Vegas Technical Support thread "[http://forums.nexusmods.com/index.php?/topic/7940008-game-freezing-at-launch-im-stumped/ Game freezing at launch - I'm stumped]":
 +
Upon launching the game after re-installing, it freezes upon getting to the Main Menu screen (where you choose to either "start a new game" or "continue to play").
 +
 
 +
* Cause: When you "change" the game executable to be "4GB/LAA aware", you are using an '''external''' program.
 +
:: That external program is NOT part of the game's structure.
 +
:: The registry values of the external program are hidden from the Steam and GOG game systems.
 +
:: The registry retains the updated information BY that "third party" program (e.g. 4GB Patcher, NTCore, etc.); not by the game publisher entry.
 +
:: Windows uses a "Prefetch", a hyperlink to that executable namesake.  ("Prefetch" is an algorithm introduced in '''WinXP''' that helps anticipate cache misses (times when Windows requests data that isn’t stored in the disk cache), and stores that data on the hard disk for easy retrieval.  See [http://windowsground.com/what-is-windows-prefetch-in-windows-10/ What is windows prefetch in windows 10? super-simplified] for a basic explanation, or [http://helpdeskgeek.com/help-desk/delete-disable-windows-prefetch/ What is Windows Prefetch and Superfetch?] for more details and tuning.)
 +
:: Software cleaners, & uninstaller programs will not touch "Prefetch" files.  (They saved in the "C:\Windows\Prefetch" folder with a ".PF" extension if you want to try deleting them.)
 +
:: The "Prefetch" files do not belong to the games software nor installers programing.
 +
:: Windows uses those hyperlinks on launch OR verifying valid updates to the executable.
 +
:: The 4GB/LAA enabler is not part of the game so it's changes will override Steam and GOG systems "validation certificate", making them "invalid".
 +
:: To bypass the system you need to update the certificate that is downloaded and currently being blocked from installing.
 +
:: The Steam verifier will show at least 1 invalid or 1 file is in error.  (That's the executable it downloaded.)
 +
 
 +
:* Solution-1:  <span style="color: red; background-color:#fff5f5;">Do not tamper with the properties of the executable unless you know what you are doing.</span>
 +
::* If you just installed the game and the "Steam Client" Interface is running in "online mode", you will get access to the systems utility for certification.  If a program refused to run, the utilities will be there in the file's '''properties''' menu to install certificatesOtherwise leave the software alone.
 +
:::* <Right-click> on the game executable file (FalloutNV.EXE), and bring up it's '''properties'''.  Follow the instructions given.
 +
::* If the "Steam Client" Interface is NOT running in "online mode" and the game is operational, you will NOT be given access to these utilities.
 +
 
 +
:* Solution-2:  Delete the existing "Pre-fetch" files.
 +
::* Run the "Steam Client" in "online mode".
 +
::* Open the "Library" tab, and select "Properties | Local Files | Verify Integrity of Game Cache".
 +
::* Once the files have been "verified" and updated, run the "FalloutLauncher.exe" BEFORE you patch the game for 4GB.
 +
 
 +
:* Solution-3: Corrupted Steam "ClientRegistry.blob" file.
 +
::* Use the Windows "Task Manager". End all the Steam related tasks starting from “Steam Client Bootstrapper”.
 +
::* Navigate to the location of your "Steam" folder (default is "C:\Program Files (x86)\Steam").
 +
::* Locate and rename the "ClientRegistry.blob" file to another name such as "ClientRegistry.blob.old".
 +
::* When you next restart Steam this file will be recreated.
 +
::* If that still doesn't resolve the problem, return to that same directory, locate and run "Steamerrorreporter.exe", and relaunch Steam again.
 +
 
 +
:* Solution-4: Make a backup copy elsewhere first, and then delete the "Steam\AppCache" folder contents.  It will be recreated when Steam next launches.
 +
 
 +
:* Solution-5: Ensure your "Time Zone" is set correctlyThis can affect Steam's attempts to collect "real time" data.
 +
::* Open the Windows "Control Panel | Date and time".
 +
::* From the three tabs, choose “Internet Time” and click on “Change Settings”.
 +
::* Check the dialogue box which says “Synchronize with Internet time server”. Click on "Update now". Click on "OK" after the time is updated successfully, and restart Steam.
 +
 
 +
:* Solution-6: Opening Steam in "Big Picture Mode" ('''Win10''').
 +
::* Right–click on the “Steam.exe” icon on the desktop.
 +
::: Note: If you don’t have a "Steam" shortcut on the desktop, you can find the “Steam.exe” in the installation directory.
 +
::* Select the “Pin to Taskbar” option from the "context menu" list.
 +
::* <Right–click> on the “Steam” icon ''in the taskbar'' and select “Open in Big Picture Mode“.
 +
::* Sign in to your account and press <Alt+Enter> to access Steam in Big Picture mode.
 +
::* Open the Game and check to see if the issue persists.
 +
 
 +
:* Solution-7: Unplug any JoyStick.  (The presence of one sometimes prevents a game from starting until it has been properly configured.)
 +
 
 +
<span id="Issue: ExploitProtection"></span>
 +
=== Issue - Game will not launch on Win10 for security reasons ===
 +
: Thanks to '''rubjonny''' of the Nexus "New Vegas Technical Support" forum for investigating and reporting [https://forums.nexusmods.com/index.php?/topic/9869713-fix-found-for-fose-and-new-vegas-not-working-on-windows-10-20h2/ this issue] and it's solution.
 +
Symptoms: The game won't start despite all the usual resolution attempts (installed outside of the default "C:\Program Files(x86)" location, "verified local files", running as "System Admin", different methods of launching, etc.).
 +
 
 +
* Cause: More recent System defaults in "Windows Exploit Protection" security settings which are causing portions of the game code to be placed randomly in memory.
 +
:* Solution:  Set a "Program" specific exemption for "FalloutNV.exe" as follows.
 +
[[File:WinExploitPreventionSetting.PNG|thumbnail|x400px|Exploit Prevention Setting]]
 +
::* Login as a "System Admin" account.
 +
::* <Right click> the '''Start Menu''' icon & select '''settings'''; or navigate to '''Settings''' (the "gear icon" in the left-hand navigation pane) from the '''Start Menu''' as usual.
 +
::* Select '''Update & Security''' in the left-hand navigation pane.
 +
::* Select '''Windows Security''' in the left-hand navigation pane.
 +
::* Select '''Virus & Threat detection''' in the right-hand main window under "Protections Areas".  (A new window will open.)
 +
::* Select '''App & browser control''' in the left-hand navigation pane.
 +
::* Select '''Exploit protection settings''' in the right-hand main window under "Exploit protection".  (The right-hand main window will change to show the list of "System settings".
 +
::* Select '''Program settings''' in the right-hand main window.
 +
::* Select the "'''+'''" icon to the left of '''Add program to customize''' in the right-hand main window.
 +
::* Select '''Choose exact file path''' from the "drop down list" that appears.
 +
::* Browse to and select '''FalloutNV.exe''' (or whichever executable is appropriate) as the file to Open.  (A list of the current "Program settings: FalloutNV.exe" will now appear.)
 +
::* Move your cursor into that list and a scroll bar will appear on the right edge of the window.  Scroll down to and select '''Force randomization for images (Mandatory ASLR)''' and make sure its set to '''Override system settings''' and '''Off'''.
 +
::: (See figure [[:File:WinExploitPreventionSetting.PNG|Exploit Prevention Setting]].  {{Thumbnail_enlargement_message}})
 +
::* Select '''Apply'''.  (The '''Program settings''' screen should be redisplayed.)
 +
::* Check that fully qualified path to the game executable is now listed with one more "system override" than previously indicated (e.g. "1 system override" for a newly added entry).
 +
:: Close the various windows.
 +
 
 +
:: This procedure will also work for '''Fallout 3'''; and may for other programs which seem to have a similar problem.
 +
 
 +
<span id="Issue: GOG DRM-free, non-steam version of FNV compatibility"></span>
 +
 
 +
=== Issue - GOG DRM-free non-Steam version of FNV compatibility ===
 +
On 01 Jun 2017, GOG.COM, the on-line game store that licenses DRM-free versions of games released their versions of "Oblivion", "Fallout 3", and "Fallout New Vegas".  As "DRM-free", they do not communicate with Steam.  They have been modified to work with the [https://www.gog.com/galaxy GOG Galaxy] client, which is similar to Steam's Client for an online community.
 +
 
 +
Thanks to '''vulchor''' and '''pixelhate''' on the Nexus "New Vegas Technical Support" forum for quickly assisting with the following information:
 +
 
 +
* By default, GOG installs the game to "C:\GOG Games\Fallout New Vegas".  This avoids the problems with Steam's default location under the "C:\Program Files" tree.
 +
 
 +
* GOG provides a customized set of INI files.  Be sure to backup the "Fallout_default.ini" file before making any changes as a precaution.
 +
:* Includes new line "STestFile2=FalloutNV_lang.esp".  This file's function has not been determined, but removing the file itself does not prevent the game from running.  It's removal may be related to the warning about content no longer being present, listed below.
 +
 
 +
* 4GB patching attempts don't work, but this is because that feature is already incorporated into the GOG versions of the games (and GECK).  Patching is not required.  They already will use up to 4GB of memory for the game.  (NOTE: The latest versions of the "4GB Patcher" program are fully compatible and do not break the GOG version any more, but do cause the GOG version to automatically load the NVSE plugin if present.  This feature may be required and tested for by some mods.)
 +
 
 +
* "NVSE" v5.0b3 (Stable) installs and works without modification.  Problems reported are most likely due to attempting to install by way of mod managers.  See [[#Checklist| Checklist item #4]].
 +
 
 +
* "LOOT" v0.11.0 works without modification.
 +
 
 +
* "xEdit/[http://www.nexusmods.com/newvegas/mods/34703/? FNVedit]" should work, but might have trouble locating the GOG game folder until updated if not installed there.
  
==Specific Solutions==
+
* Warning message "Unable to start steam automatically. Your game may not launch correctly" is given when starting the game through FOMM (which has recognized it automatically).  This warning can be ignored.
  
=== Issue: Application load error(s) ===
+
* Trying to start a save after installing NVSE v5.0b3 will prompt "This save relies on content that is no longer present. Some object may no longer be available" even for the first save after the Doc Mitchell "chargen" sequence, with no mod installed at the time.  This warning can be ignored.
Specifically error codes: 5:0000065434/P:0000065432
 
* Cause: Indicate the Steam Client is not loaded.
 
  
* Solution:  The client may be in "Offline" mode and minimized, but must remain running while launching the game, even with "nvse_launcher" or "fnv4gb".
+
* The "G.E.C.K." is pre-installed, but has the original GECK.INI file.  This needs to be modified to enable loading multiple masters.  See [[#Issue: GeckCustom.INI file|Issue: GeckCustom.INI file]].
  
=== Issue: Vanilla game CTDs on startup ===
+
* The "GOG Galaxy" support, however, requires Windows 7 so this has "broken" XP and Vista support by default.  A post on the GOG forum says their tech support responded:
Uninstalled and re-installed the game but even without mods it crashes on startup.
+
<div name="Simulated code box" class="boilerplate metadata" id="Warning Notice"
* Cause-1: Likely you forgot to clear out your "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder.  The game places your specific versions of the Fallout and Fallout_prefs INI files there, along with your save gamesThese are not replaced when you verify/re-install the game.
+
style="margin:0px 10px 10px 20px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
/* Remove the next four 'white-space' lines to restore default white-space processing. */
 +
white-space: pre-wrap;      /* css-3 */
 +
white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
 +
white-space: -pre-wrap;      /* Opera 4-6 */
 +
white-space: -o-pre-wrap;    /* Opera 7+ */
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">- We no longer perform compatibility tests for Windows XP and Vista, so I'm unable to guarantee that the game will work correctly on Windows XP as it was not tested.
 +
- The game can be installed and played on a computer without an Internet connection. Downloading the standalone installer and moving it manually to the offline computer will be required.</div>
 +
: There's a workaround for getting functional on systems older than Windows 7 that is reported to be effective involving taking a '''"steam_api.dll"''' from any Steam game, renaming it '''"GalaxyWrp.dll"''' and replacing the one in the GOG FNV folder with the renamed Steam file.  Or you can simply delete (suggest rename by adding something to the extension) if you don't need the additional languages that file provides.  Doing this will break "GOG Galaxy" integration, but since Galaxy doesn't run on older Windows versions any longer anyway, supposedly that doesn't matter to you.  However, if you care about achievements, "local file verification", and cloud saving, those are "GOG Galaxy" only features as well.  Suggest burning your downloaded files to a CD/DVD/Blu-ray in case you need to reinstall again and have a slow internet connection or are worried about losing access to the GOG servers.  Check the game release thread on the [https://www.gog.com/forum/fallout_series#1496664056 GOG forums] for more info.
 +
: The "workaround" has been confirmed to work on Windows XP.
 +
 
 +
<span id="Issue: GOG version won't start from FOMM"></span>
 +
 
 +
=== Issue - GOG version will not start from FOMM ===
 +
You get the error message: "Unable to start steam automatically. Your game may not launch correctly."
 +
* Cause: Unknown.
 +
:* Solution: The very first time, use the "FalloutNVLauncher.exe" so it will setup your specific hardware settings.  The "load order" you established in FOMM will not change and NVSE should also work.  Thereafter you can simply use the NVSE launcher "nvse_loader.exe", which FOMM can be configured to launch.
 +
:: Note that the GOG version does not need or work with any version of the 4GB patcher.  It is already modified to use 4GB of RAM.  See [[#Issue: GOG DRM-free, non-steam version of FNV compatibility|Issue: GOG DRM-free, non-steam version of FNV compatibility]].
 +
 
 +
<span id="Issue: How to disable the Steam Overlay"></span>
 +
=== Issue - How to disable the Steam Overlay ===
 +
Sometimes it is necessary to turn off the Steam Overlay in the Steam Client in order to resolve a conflict.
 +
* Cause: The Steam Overlay uses a technique that can conflict with other applications or tools using a similar technique.  This solution assumes disabling the Steam Overlay is the preferred method of resolving this conflict.
 +
 
 +
* Solution:
 +
** Open the Steam Client.
 +
** Select "Steam | Settings" from the top menu bar.  This will open a "Settings" window.
 +
*** Select the "In-Game" option.
 +
*** Disable (uncheck) the "Enable the Steam Overlay while in-game" option.
 +
*** Click on the "OK" button to close the "Settings" window.
 +
** (Optionally) Select "Go off-line".  Without the Overlay, there is no real reason for the processing overhead of being "on-line" to the Steam Server.  This will require restarting the Steam Client, but will thereafter remain in effect until you choose to change it again.
 +
** Minimize the Steam Client.  (Even in "off-line" mode, it is necessary to start the Steam Client for the DRM licensing engine to enable play.)
 +
** Launch your game from a shortcut on the desktop.
 +
 
 +
<span id="Issue: Incomplete save game load"></span>
 +
=== Issue - Incomplete save game load ===
 +
After loading a savegame (almost always in an exterior cell) most of the in-game sounds won't play, a lot of references won't render, some of the landscapes might be incomplete, and entering menus/console has a long delay; even though you are not using the built-in "auto savegame" feature.
 +
 
 +
* Cause: This seems to be related to the NVSR "post FCU" problem, even when using the '''redmaxblower''' configuration.  (See '[[#Issue:_CTD_after_10-20_minutes_of_play_.28post-Win10_2017_FCU.29|Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)]]').
 +
:* Solution: User '''VariableEagle''' discovered that disabling three Win10 background "local services" seems to resolve this.  He happened to disable all three at the same time, and is not certain all three are required to resolve the problem.
 +
::* Logon using a local "Administrator" account.
 +
::* Open the Windows "Task Manager" (either by "< Right-click >" on the Taskbar and selecting it from the "context menu" that appears, or one of the other methods in the article [https://www.windowscentral.com/how-identify-and-terminate-high-resource-processes-using-task-manager-windows-10 How to use Windows 10 Task Manager to kill processes that drain resources]).
 +
::* Select "Services" tab and then "< Right-click >" on "Open Services".
 +
:::* Find the service: '''GraphicsPerfSvc''', "< Right-click >" on it and select "Stop".
 +
:::* Then go to the "Properties" of that service and change the "startup type" to "Disabled".
 +
:::: According to [http://servicedefaults.com/10/graphicsperfsvc/ GraphicsPerfSvc Service Defaults in Windows 10]: "GraphicsPerfSvc is a Win32 service. In Windows 10 it is starting only if the user, an application or another service starts it."  Apparently it was added in build 1709 ("FCU" aka "Redstone 3"), but existed as far back as [http://procpedia.com/file/10789/What-is-GraphicsPerfSvc-dll-and/ Win7].  There a number of reports in the past of this service consuming 100% of CPU resources continuously.  It is also a suspect in game stuttering problems (especially in "full screen" mode).  It's default "startup type" is supposed to be "manual".
 +
:::* Repeat the last two steps for the service: '''GameRecorderSVC'''.
 +
:::: This appears to be the service required by the "screen capture button" (at least on Lenova laptops; it is not listed on the site [http://servicedefaults.com/10/ ServiceDefaults] or other sites listing similar service defaults).
 +
::* Use the "registry editor" ''regedit'' to disable the '''Xbox Game Monitor''' service by going to '''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xbgm''' and change '''Start REG_DWORD''' from "3" to "4". Restart Windows after making those changes.
 +
::: This service is used by the Win10 "Game Bar" DVR. - Source: [https://www.windowscentral.com/how-disable-and-remove-game-bar-windows-10-creators-update How to disable the Game Bar and DVR in Windows 10].
 +
 
 +
<span id="Issue: LongLoads"></span>
 +
=== Issue - Long loading times ===
 +
Symptoms: Loading a "save game file" takes longer than it used to, by several (e.g. 5-10) minutes.  It does eventually complete loading, so this is not the "infinite roulette wheel" problem discussed in "Issue - Incomplete save game load".
 +
 
 +
* Cause: Varies but is generally an indication the engine is processing more information in the save game file or having difficulty locating/reading the file.  This may be the result of "save game bloat".  The following are things to check first to determine the cause of the problem.
 +
:* Diagnostic checklist.
 +
::# Have you tried "defragging" your disk drive?
 +
::# Have you checked the [https://www.nexusmods.com/newvegas/mods/53635 NVAC] and [https://www.nexusmods.com/newvegas/mods/67883 NVSE] logs for loading errors?
 +
::# Are you using the same "file slot" for your saves or "quick saves"?  (Not recommended.  There are mods which ensure a new file is created for each of those purposes, such as "[https://www.nexusmods.com/newvegas/mods/45652 CASM]" and "[https://www.nexusmods.com/newvegas/mods/57465 Clean Quick Saves]".)
 +
::# Have you tried loading the save game immediately after exiting to the desktop and re-launching instead of from the main menu, and if so does the time to load vary?  (This suggests the problem is with some plugin(s) that are loading when the game starts as opposed to something when the game is saved, or vice versa.)
 +
::# Does the game re-load fine upon the death of your character or using a quicksave file created in that game session?  (This suggests the problem is with some plugin(s) that are loading when the game starts as opposed to something when the game is saved.)
 +
::# Did you check that you are using exactly the same mod manager "profile" (i.e. current game configuration) with the exact same "load order" as previously?
 +
::# Have you "merged plugins" together into custom ESP files to reduce the number of used plugin slots, and then possibly added the same plugin to multiple merged plugins or even loaded that plugin again separately?  If the file names are NOT the same, the engine will load multiple copies of a plugin and uselessly add to it's processing load.
 +
::# Are you using a number of mods which spawn more "actors" (NPCs or Creatures) into the game?
 +
:::: When you first add mod plugins, they don't have the same impact as later on because they haven't spawned as many actors in the beginning as later.  The longer you play such a plugin, the more spawned actors the save game file has to keep track of (even when they are "dead", because each actor/corpse is also a "container").  At some point you cross the "tipping point" where you start to see the impact in terms of loading times.  This is unlikely to be early in the game, unless you have a number of mods which spawn in the same cells.  (The "Mojave Wasteland" exterior is primarily one large cell.)
 +
:::: The same applies to everything you move (e.g. a door is opened but not closed again, as well as "loot" you pickup).  If it is something unique to a mod (only that plugin has it defined), then the record for that item has to be found in that plugin, which is why you will corrupt your save game if you remove that plugin later onThe record is no longer valid.  If you are a "hoarder" (like me) you have to be careful to sell off unique plugin items to keep the bloat down.  Selling items lets the game reset them back to their default location.
 +
:* Solution: If you determine the problem is "bloat", follow the "[[FNV_General_Mod_Use_Advice#Clean_Saves|Clean Saves]]" procedure after disposing of the items which create "bloat".  Then, if you still have issues, you can try the tool "[https://www.nexusmods.com/newvegas/mods/49396?tab=description New Vegas Save Cleaner]" after you have made backups of the save game files.  Please read the instructions in the downloaded package carefully.  If you don't understand what it is doing, then read the comments page or ask in the [https://forums.nexusmods.com/index.php?/forum/354-new-vegas-mod-talk/ forum].
  
:* Solution-1a: Try renaming the "Users" folder INI files first.  Then if that fails move the "saves" elsewhere, delete that FalloutNV folder's content, and re-install again.  If you have to re-install again anyway, be sure to install to a folder that is not under the default "C:\Program Files" folder tree.  See [http://wiki.nexusmods.com/index.php/Installing_Games_on_Windows_Vista%2B Installing Games on Windows Vista+] for the rationale and guidance.
+
<span id="Issue: MissingVCRuntime"></span>
  
:* Solution-1b: Consider if the problem happens with other Steam gamesIf so, check out the [[#Issue: Problems point to Steam as the source|Issue: Problems point to Steam as the source]] entry.
+
=== Issue - Missing MSVCR120.dll ===
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 10px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Being an older game, FNV looks for a number of "runtime library" (DLL) files from specific older packages.  It does not know about later releases which may be fully "backwards compatible"One of these packages is the Visual Studio C++ 2013 redistributable (aka "MSVC2013 Runtime") or individual files from this package (such as "MSVCR120.dll"). It is common to have multiple versions of such libraries (both release year and 32 or 64-bit versions) installed at the same time.  Even if you are running a 64-bit version of Windows, you need the 32-bit version of this package for FNV (which is a 32-bit game).
  
* Cause-2: If the CTD occurs before you get to the Main/Pause Menu, likely it is a "missing master file" required by a mod.
+
Most people find the [https://www.microsoft.com/en-us/download/details.aspx?id=40784  Visual C++ 2013 Redistributable package (x86)] resolves this problem for them.  Note there are "File Paths" for both 32-bit (x86) and 64-bit (x64) versions on the same download page.  Scroll all the way to the bottom and double check which you are downloading.
 +
</div>
  
:* Solution-2: See the wiki article [http://wiki.nexusmods.com/index.php/Missing_Masters Missing Masters] for a tutorial on how to determine the missing file and fix this problem.
+
<span id="Issue: Modded game CTDs on startup"></span>
  
* Cause-3: Recently (mid 2016) nVidia driver updates and some Windows 10 updates have started to cause CTDs upon startup to previously trouble-free games. Apparently FNV is now old enough that it has been dropped from the "test suites" for these productsThis is a common, routine practice in the industry.
+
=== Issue - Modded game CTDs on startup ===
 +
* Cause-1: If the CTD occurs '''before''' you get to the Main/Pause Menu, likely it is a "missing master file" required by a mod plugin.
 +
:* Solution-1: Load your entire "load order" into [http://www.nexusmods.com/newvegas/mods/34703/? FNVedit] and see if it reports any "missing master" errors for any pluginsSee the wiki article [http://wiki.nexusmods.com/index.php/Missing_Masters Missing Masters] for a tutorial on how to determine the missing file and fix this problem.
 +
::* Re-check the mod download page for any required files you may have missed or removed.
  
:* Solution-3a: The "New Vegas Anti-Crash" (NVAC) mod has been reported to conflict with the offending nVidia driversIt may prove necessary to make a choice between the two depending upon which need is greaterIn general, avoid upgrading your video card drivers unless the latest fixes a particular problem you are encountering.
+
* Cause-2: If the CTD occurs during an initial loading screen '''after''' you get past the Main/Pause Menu, likely it is a plugin that is sorted in the wrong order.
 +
:* Solution-2:
 +
::* Re-check the mod download page for any required files you may have missed or removed.
 +
::* Try sorting your "load order" with [https://loot.github.io/ LOOT]You may need to make some manual adjustments to meet mod requirements to the "load order".
 +
::* Remove any unused plugins (ESM or ESP extensions) from the "Data" folder.  They count against the "plugin cap" and 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 "Missing Master" error.
  
:* Solution-3b: Depending upon the nature of the Windows update (all updates provide a link to a MS Knowledge Base article explaining the update in detail), reverting to the "system restore point" prior to the update may be a reasonable solution.  However, in the long term this might prove to be a security risk, so be sure to report the problem and track the status of the update for possible fix and re-release.
+
<span id="Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)"></span>
  
=== Issue: Problems point to Steam as the source ===
+
=== Issue - NVSE - fails to load after update KB4058043 to Win10 FCU ''v1709'' ===
 +
This can also manifest as a general slowdown and loss of some sounds.
 +
: Once it has been installed previously functioning NVSE logs report the following when the game is launched:
 +
<pre>
 +
old winmain = 01E1F720
 +
couldn't write memory (update winmain)
 +
couldn't init hook
 +
Couldn't inject DLL.
 +
terminating process</pre>
 +
: Many thanks to '''Derialund''' of the "Fallout New Vegas Technical Support" forum for initial reporting and investigation of mitigation regarding this issue.
 +
* Cause: Windows Update [http://support.microsoft.com/en-us/help/4058043/microsoft-store-reliability-improvements-for-windows-10-version-1709-d KB4058043, December 15, 2017] to Win10 FCU (v1709), also known as the "Meltdown and Spectre Vulnerability" patch.  There are other KB numbers for the same patch applied to various build numbers.  See the articles referenced below.
 +
: According to Microsoft Support:
 +
:<span style="margin:0px 10px 10px 0px;border:1px solid #DAA520;color: lightgray; background-color:#424242;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">''This update makes reliability improvements to Microsoft Store and fixes an issue that could cause app update failures and cause Microsoft Store to generate unnecessary network requests.''</span>  (Presumably (based upon timing and effect) this is part of the mitigation effort against the '''Meltdown''' and '''Spectre'''  vulnerabilities in processors' “speculative execution” architecture existing since 1995.  For a "layman's explanation" of this vulnerability. please see the [http://www.redhat.com/en/blog/what-are-meltdown-and-spectre-here%E2%80%99s-what-you-need-know What are Meltdown and Spectre] article.)
 +
: Microsoft is continuing to roll out a series of patches to fix this vulnerability.  This article on [http://www.techarp.com/guides/microsoft-spectre-meltdown-patch/ Techarp] dated 23 Feb 2018 has the rollout schedule and Knowledge Base article numbers for various builds.  The official Microsoft word on this vulnerability is [http://support.microsoft.com/en-us/help/4073757/protect-your-windows-devices-against-spectre-meltdown here].
 +
: The problem occurs with FNV even when it is installed on a different drive from the default install location (i.e. NOT "C:\Program Files(x86)") and the executables have been added to the "Data Execution Prevention" ('''DEP''') exception list.
 +
: FCU now includes [http://blogs.technet.microsoft.com/srd/2017/08/09/moving-beyond-emet-ii-windows-defender-exploit-guard/ Windows Defender Exploit Guard (WDEG)].  This is the successor to "Enhanced Mitigation Experience Toolkit" ('''EMET'''), and "to prevent possible compatibility, performance, and stability issues, Windows will automatically block or remove EMET on Windows 10 systems starting with the Windows 10 Fall Creators Update."  (Details in the linked article.)  A 1:04:51 minute [http://www.youtube.com/watch?v=ABuFjGBbyWA video] focused on '''WDEG''' and how it fits into Microsoft's "End to End Protection" strategy is available as well.  Configuration instructions are found in [http://www.ghacks.net/2017/10/25/configure-windows-defender-exploit-guard-in-windows-10/ Configure Windows Defender Exploit Guard (WDEG) in Windows 10].  '''WDEG''' works with '''DEP''' but apparently it's settings override those set in '''DEP'''.
 +
:* Solution: Unknown.  The problem has been reported to the '''NVSE''' team.
 +
:* Mitigation (For Windows 10): As for the '''FNV''' and '''NVSE''' problem in particular, inside '''WDEG''', there are two main configuration ''profiles'': "System settings" and "Program/Application settings". To solve this problem it is necessary to add an entry for both '''FalloutNV.exe''' and '''NVSE_loader.exe''' to '''WDEG''' under "Program/Application settings".  There, every security option must be ''override'' and/or ''superimposed on deactivate''.
 +
:: Practically, you have to:
 +
::# Open the '''Windows Defender Security Center'''.
 +
::# Go to "App & Browser control".
 +
::# Scroll down the page and go to "Exploit Protection" section. Then click on "Exploit Protection Settings".
 +
::# Inside the result page, click on "Program Settings" tab.
 +
::# Click on "Add program to customize".
 +
::# Click on "Choose exact file path" and search for the game root folder (with the main game executables, where '''FalloutNV.exe''' and '''NVSE_loader.exe''' should be).
 +
::# In the "Program Settings" page should appear the entry with the full path (e.g. "D:\Fallout\FalloutNV.exe").
 +
::# Mouse over such an entry and click on it, and then on the button "Edit".
 +
::# Inside the resulting settings page, there are various entries like:
 +
::#* Arbitrary Code Guard (ACG)
 +
::#* Block low-integrity images
 +
::#* etc.
 +
::#: Then under each entry there's a check box with the description: "Override system settings". Under it there's an '''On/Off''' "switch" or "slide-box".
 +
::#:: That checkbox must be checked for every entry; and then every "slide-box" must be turned to OFF.
 +
::: Overall, 21 System overrides should be indicated under the "Fallout Executable" entry list, indicating that everything is turned "off".
 +
:* Mitigation (for older versions of Windows: untested): Those without access to '''WDEG''' can see if [http://support.microsoft.com/en-us/help/2458544/the-enhanced-mitigation-experience-toolkit Enhanced Mitigation Experience Toolkit (EMET) 5.52] will suffice in the same manner instead.  This free tool is approaching "end of life" on 31 July 2018 (at the moment).  After that, only Windows 10 will be supported and security patched.  Note that the "EMET User Guide" is a separate download.
 +
 
 +
<span id="Issue: Problems point to Steam as the source"></span>
 +
=== Issue - Problems point to Steam as the source ===
 
Errors such as a "Preparing to Launch" message loop, or nothing apparently happening when you click to start any Steam game, or system error messages ask to troubleshoot Steam.
 
Errors such as a "Preparing to Launch" message loop, or nothing apparently happening when you click to start any Steam game, or system error messages ask to troubleshoot Steam.
 
* Cause: A corrupted "ClientRegistry.blob" file.
 
* Cause: A corrupted "ClientRegistry.blob" file.
Line 126: Line 625:
 
** Now when you try launching your game the issue should be solved (or at least you should get a different error).
 
** Now when you try launching your game the issue should be solved (or at least you should get a different error).
  
=== Issue: How to disable the Steam Overlay ===
+
<span id="Issue: Regional Non-English language version of the game displaying English dialogue"></span>
Sometimes it is necessary to turn off the Steam Overlay in the Steam Client in order to resolve a conflict.
+
=== Issue - Regional Non-English language version of the game displaying English dialogue ===
* Cause: The Steam Overlay uses a technique that can conflict with other applications or tools using a similar techniqueThis solution assumes disabling the Steam Overlay is the preferred method of resolving this conflict.
+
Why are my DLCs in English instead of my Regional language?
 +
 
 +
* Cause: The menu and interface (text) files language is determined by the language you select when download/updating the game through Steam/GOG.  You should have "<DLC>_lang.esp" files for your Regional language installed, but they are not "active".  There should be corresponding "<DLC>_lang.nam" files, but aren't.  Even when present the "*_lang.esp" files cannot normally be "made active", as the default "*.nam" files force the game to load the "INT (English)" versions of the DLCs instead.
 +
:* Solution-1a: Remove the incorrect language code "*.nam" files.
 +
::* If these "*.nam" files are not present, try to "activate" the "*_lang.esp" files.  Then engage in conversation with a DLC NPC to verify you are now getting the dialogue in your Regional language.
 +
 
 +
:* Solution-1b: The mod [http://www.nexusmods.com/newvegas/mods/65508 Voice Actor BSA files] lets you swap the language Voice Actor BSA file (Fallout - Voices1.bsa) to a different one of your choice.  This enables you to have the text in one language and the voices in another.
 +
 
 +
:* Solution-1c: See also [[#Issue: Regional Non-English language version of the game with different language audio?|Issue: Regional Non-English language version of the game with different language audio?]] solution as that is a similar (though reversed) situation.
 +
 
 +
:* Otherwise, contact your Regional Steam provider about the problem.
 +
 
 +
<span id="Issue: Regional Non-English language version of the game with different language audio?"></span>
 +
=== Issue - Regional Non-English language version of the game with different language audio ===
 +
How do I get the audio in one language (e.g. "English") along with my Regional language (e.g. "Italian") for subtitles?<br>
 +
(With thanks to '''PipBoyUser''' of the Nexus Fallout "New Vegas Discussion" forum for investigating and reporting the following.)
 +
 
 +
* Cause: The language used for the Audio (voices) and subtitles installed for the game depend upon which Regional language version of the game you install.  (The general process of making a game compatible with different Regional languages is described for Steam developers in this [http://partner.steamgames.com/doc/store/localization localization] article.)
 +
 
 +
:* Solution-1:  In order to "mix" different voice and subtitle languages, you need to install both language versions (in the correct order) and copy files from one install into the other language version.  You want to install the game for the language you want the Audio to be voiced in (to preserve the Audio filenames and paths used), and then replace the "*.ESM" and "*.NAM" files with those from the Regional language version.  (Examination has shown the "*.ESM" files contain at least some "in-game" text in the Regional language.  The "*.NAM" files tell the game engine to load certain "master" (i.e. the DLC ESM) files automatically even if they are not selected as part of the "load order", and come in language specific versions.)
 +
:: This is a multi-step process, taken in the following order:
 +
::# Install the game in your Regional language version (the one you want the subtitles to be using).
 +
::# Open the "Fallout_default.INI" file: "[General]" section, "sLanguage=" entry, and note for later use the exact language name used (e.g. "ITALIAN").
 +
::# Copy all the vanilla and DLC game "*.ESM" and "*.NAM" files somewhere else safe for later use.
 +
::# Now re-install the game, this time choosing the language version which you wish to hear spoken (e.g. "ENGLISH").
 +
::# Replace the the current install's  "*.ESM" and "*.NAM" files with those you backed up from the Regional language version earlier.
 +
::# Edit the three INI files (see the [http://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice#Game_INI_files Game INI files] section of the wiki "FNV General Mod Use Advice" article), find the "[General]" section entry "sLanguage=" and change the value of that (e.g. "ENGLISH") to that of your desired subtitle language noted earlier.  (Case and spelling are significant.)
 +
:: You should now hear the voices in the installed language and see the subtitles in your designated regional language.  <span style="color: green;background-color:#fff5f5;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Remember that if you "verify local files", the "*.ESM" and "*.NAM" files will probably get restored to those of the Audio language, so you will probably have to replace them with your copies from the Regional language backup.</span>
 +
 
 +
<span id="Issue: NVSE - Regional Non-English language version of the game won't load NVSE"></span>
 +
 
 +
:* Solution-2: See also [[#Issue: Regional Non-English language version of the game displaying English dialogue|Issue: Regional Non-English language version of the game displaying English dialogue]] solutions  as that is a similar (though reversed) situation.
 +
 
 +
<span id="Issue: Regional Non-English language version of the game won't load NVSE"></span>
 +
=== Issue - Regional Non-English language version of the game will not load NVSE ===
 +
Example: Various methods to start the "enplczru" version of the game (Eastern Europe: Czech Republic, Poland, Hungary, and Slovakia; aka "PL/CZ/RU" version) with NVSE gets Steam error: "P:0000065432" or "5:0000065434".  Normally this error indicates the Steam Client app is not running, but in this instance it is merely the closest guess by the game as to the cause of the problem.
 +
 
 +
* Cause: NVSE does not accept "language" parameters on the command line.
 +
:* Solution-1: NVSE should be launched indirectly from [http://www.nexusmods.com/newvegas/mods/55061/? 4GB Fallout New Vegas Updated] or [http://www.nexusmods.com/newvegas/mods/62552/? FNV 4GB Patcher] modified game executables, which will accept a language (i.e. "SteamAppID") parameter, and then launch NVSE.  Each regional version of the game has a unique SteamAppID.  Here is how to identify what this AppID is and apply it:
 +
:# Right click your '''FalloutNV.exe''' file in the Steam game folder, and create a shortcut to the desktop.
 +
:# Right click the newly created desktop shortcut and open "properties".
 +
:# It should say something like "steam://rungameid/22490".  Copy that last number (the game's SteamAppID).
 +
:# Right click the 4GB launcher shortcut, and open "properties".
 +
:# In the "Target" text box, change the number in the " -SteamAppId 22380" parameter to your actual SteamAppID number (i.e. "22490").
 +
: Note that because the path to the game contains embedded spaces, the entire path needs to be placed within quotation marks (i.e. "<path>") everywhere it is used in the shortcut.  The AppID parameter goes outside of the quotes, on the "target" property line ... as in ("E:\Games\SteamLibrary\steamapps\common\Fallout New Vegas enplczru\fnv4gb.exe" -SteamAppID 22490) without the "(parentheses)".
 +
 
 +
:* Solution-2: Some people reported early success by renaming their regional version named game folder (i.e. "Fallout New Vegas enplczru" to "Fallout New Vegas": the English version name).  It is not reported if this causes issues later on with language specific patches, which is why it is the secondary solution.
 +
 
 +
:* Solution-3: : User '''sanassar''' in the "New Vegas Mod Troubleshooting" forum [http://forums.nexusmods.com/index.php?/topic/3148629-nvse-with-enplczru-version/#entry64689921 thread] provided the following solution.  It has been [edited] and reformatted for clarification.
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 50px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">I managed to get my "enplczru" [regional version] with the "application error P:0000065432" and "couldn't read arguments" errors working.
 +
 
 +
This is what I did and I have no idea which one of these steps fixed it but there is no harm in doing all of these, please bear with me:
 +
 
 +
* Install NVSE first by following the instructions at http://nvse.silverlock.org/.  [If you have problems, see the  '[[#Checklist|Checklist]] Item #4' entry in this document.]
 +
 
 +
* This part is only for the normal people, like me, who do '''not''' have "Fallout NV" installed in the default directory where windows is installed  - "C:\[Program Files]". If you are not normal and have it installed in "C:\[Program Files]" - ignore this step.
 +
: Also bear in mind that if you are not normal and have the game in "C:\[Program Files]" but the folder's name is '''"Fallout New Vegas enplczru"''', you should do this as well!!
 +
 
 +
:* I went to "C:\Program Files (x86)\" and created a folder called "Steam" and in it a folder called "SteamApps" and in it a folder called "common". So the whole path looks like this now:
 +
:: <span style="margin:0px 10px 10px 10px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">C:\Program Files (x86)\Steam\SteamApps\common</span>
 +
 
 +
:* I opened Command Prompt and wrote this:
 +
:: <span style="margin:0px 10px 10px 10px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">cd c:\program files (x86)\steam\steamapps\common</span> - which basically navigates Command Prompt to the file you created.
 +
 
 +
:* Then I typed in the following:
 +
:: <span style="margin:0px 10px 10px 10px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">mklink /d "Fallout New Vegas" "<Your full Fallout NV enplczru directory>"</span> [- replace "<Your full Fallout NV enplczru directory>" with your actual "target" (NOT "C:\Program Files") folder name.]
 +
:: Mine looks like this:
 +
:: <span style="margin:0px 10px 10px 10px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">D:\Games\Steam\SteamApps\common\Fallout New Vegas enplczru</span>
 +
:: so my command line looked like this:
 +
:: <span style="margin:0px 10px 10px 10px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">mklink /d "Fallout New Vegas" "D:\Games\Steam\SteamApps\common\Fallout New Vegas enplczru"</span>
 +
:* To check if this worked you now must have a "Fallout New Vegas" folder in your "C:\Program Files (x86)\Steam\SteamApps\common" with a little arrow on it. This is a ''[http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/ symbolic link]''. It means any program looking for "Fallout New Vegas" in "C:\Program Files (x86)\Steam\SteamApps\common" [tree] will find it, but the folder itself will be located on another drive, which is cool.
 +
 
 +
* The second part is about getting NVSE to load [with the game] properly. For this I only managed to do it through the "[http://www.nexusmods.com/newvegas/mods/55061/ 4GB Fallout New Vegas - Updated]" mod.  (This mod is superseded by [http://www.nexusmods.com/newvegas/mods/62552 FNV 4GB Patcher] (by the same author) which now supports '''US-EU-AU / DE (No Gore) / ENPLCZRU''' versions as well.) This is a tool that let's you load "Fallout New Vegas" with lots of Mods and Texture Packs without getting crashes. It sets a "4GB Virtual Memory Address Space" for the game to use, hence its name.
 +
 
 +
:* So [download the 4GB mod].
 +
:* Download and install the mod, either by using [a mod manager such as Vortex or "Nexus Mod Manager") or manually - just read the [mod] instructions.
 +
:* Then go to the mod folder (mine is at "D:\Games\Steam\steamapps\common\Fallout New Vegas enplczru\Mods\FNV4GB-55061-1-9\FNV4GB-1-9"), and ...
 +
:* Create a shortcut of "fnv4gb.exe" either on your desktop or the start menu [or somewhere you will find it easily].
 +
:* Right click the shortcut and add this string:
 +
:: <span style="margin:0px 10px 10px 10px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">-SteamAppId 22490</span> at the end of the "Target:" field.
 +
:: So [my shortcut] looks like this:
 +
:: <span style="margin:0px 10px 10px 10px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">"D:\Games\Steam\steamapps\common\Fallout New Vegas enplczru\Mods\FNV4GB-55061-1-9\FNV4GB-1-9\fnv4gb.exe" -SteamAppId 22490</span>.
 +
 
 +
You are done!
 +
 
 +
Now if you want to run the game:
 +
* Make sure that Steam [Client] is running.  [This can be in either "online" or "offline" mode.]
 +
* Start the game using the shortcut you created and modified in the previous step.
 +
* TADAA!
 +
 
 +
If you want to check whether the NVSE works just press the " <`> " command line key in the game main menu and type getNVSEversion. You should get a version number. Mine is 5.
 +
</div>
 +
 
 +
<span id="Issue-FNC-MO2"></span>
 +
=== Issue - Unable to install FNC with MO2 ===
 +
Often described as being unable to find the FNV or FNC ESM files after installation.
 +
 
 +
: Thanks to '''Purr4me''' (Kitty Black) for the basis of following:
 +
 
 +
The "Fallout New California (FNC)" mod comes as an EXE installer.  This causes confusion among users of the "Mod Organizer 2 (MO2)" manager.  DO NOT point the installer to the game "Data" folder if you intend to operate the game from within MO2.  Here is how to install FNC for use with MO2.  (The basis of this may or may not work with other similar managersIt has not been tested with them like it has with MO2, so use at your own risk.)
 +
 
 +
# Install the base Fallout New Vegas game and NOTHING ELSE.
 +
# Run the initial game setup from the "Steam Client" or GOG "Galaxy" if needed so it has detected and is configured for your hardware.
 +
#: DO NOT patch the Steam version to use 4GB of memory (GOG doesn't need it); and do not install NVSE or any other addons or mods.  Just leave the raw base game files and folders alone.
 +
# Install MO2 and point it's FNV profile setup to the location of the raw game files (where FalloutNV.EXE is located).
 +
# Run MO2, and launch the FNV game from within it.
 +
#: Create a "save game" file and exit the game.
 +
# Close MO2.  (This is important to get the base game profile established correctly.)
 +
# Open MO2 (again) and add the "Fallout New California (FNC)" EXE file as a "1 time executable" to the drop-down menu.
 +
#: The files from the "FNC EXE" should then be extracted into an isolated folder.
 +
#: MO2 will automatically create the appropriate folders for the game files as needed.
 +
# When the "1 time executable" process is done:
 +
## hit the "Sort" button, and then,
 +
## run the game.
 +
#: Once the game has been entered and you can confirm you are now running "Fallout New California (FNC)", you can exit and apply the 4GB Patch (if needed), as well as NVSE and other plugins and mods as needed without any major problems beyond the usual mod conflicts.
  
* Solution:  
+
<span id="Issue: Vanilla game bugs"></span>
** Open the Steam Client.
 
** Select "Steam | Settings" from the top menu bar.  This will open a "Settings" window.
 
*** Select the "In-Game" option.
 
*** Disable (uncheck) the "Enable the Steam Overlay while in-game" option.
 
*** Click on the "OK" button to close the "Settings" window.
 
** (Optionally) Select "Go off-line".  Without the Overlay, there is no real reason for the processing overhead of being "on-line" to the Steam Server.  This will require restarting the Steam Client, but will thereafter remain in effect until you choose to change it again.
 
** Minimize the Steam Client.  (Even in "off-line" mode, it is necessary to start the Steam Client for the DRM licensing engine to enable play.)
 
** Launch your game from a shortcut on the desktop.
 
  
=== Issue: Vanilla game bugs ===
+
=== Issue - Vanilla game bugs ===
Most that have been officially patched or are XBox or PS console only are available on the [http://fallout.wikia.com/wiki/Fallout:_New_Vegas_bugs Wikia Fallout Portal] page.
+
Most that have been officially patched or are XBox or PS console only are available on the [http://fallout.wikia.com/wiki/Fallout:_New_Vegas_bugs Wikia Fallout Portal: Bugs] page.
  
 
* Solution: Community "game fixer" mods.  The following are specifically recommended, though their effectiveness varies by system.  Install and test individually in the following order:
 
* Solution: Community "game fixer" mods.  The following are specifically recommended, though their effectiveness varies by system.  Install and test individually in the following order:
** [http://www.nexusmods.com/newvegas/mods/34832/? New Vegas Stutter Remover (NVSR)] (requires [http://nvse.silverlock.org/ NVSE]. The 5.0 beta versions are stable.  Check version requirements of other mods when choosing.)
+
:* [http://www.nexusmods.com/newvegas/mods/53635/? New Vegas AntiCrash (NVAC)] (Essential: solves most common CTDs).
** "Sheson memory patch" for NVSE. (Increases "heap size".  Use either the "heap replacement" feature of NVSR or thisBoth 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|Issue: CTD without warning, "out of memory error", or stops responding]] sub-topic for simple but detailed instructions for enabling this patch.
+
:* [http://www.nexusmods.com/newvegas/mods/66537 New Vegas Tick Fix (NVTF)] (Win7-10 alternative to NVSR, with fewer features.)
** [http://www.nexusmods.com/newvegas/mods/53635/? New Vegas AntiCrash (NVAC)] (solves most common CTDs),
+
:* [http://www.nexusmods.com/newvegas/mods/34832/? New Vegas Stutter Remover (NVSR)] (requires [http://nvse.silverlock.org/ NVSE].  The 5.0 beta versions are stable.  Check version requirements of other mods when choosing which version of NVSE to use.)
** [http://www.nexusmods.com/newvegas/mods/51871/? Better Game Performance] (optional: some reports of minor slowdowns),
+
::* There are several reports in the download page "comments" that NVSR causes CTDs after 10-20 minutes of play once the Win10 "Fall Creator's Update" (FCU) of Nov 2017 has been installed where previously everything had been stableThose experiencing this problem are recommended to see [[#Issue:_Recent_(post-Win10_FCU)_CTDs_after_10-20_minutes_of_play|Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play]]. (Windows 7+ users are advised to consider using mod [http://www.nexusmods.com/newvegas/mods/66537 New Vegas Tick Fix (NVTF)] instead, as it is designed to avoid the problems though with fewer features than NVSR.)
** [http://www.nexusmods.com/newvegas/mods/51664/? 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),
+
::* Core processors prior to I5 or I7 are suggested to use '''NVSR_4-1-32''' (simpler options) with the [https://taleoftwowastelands.com/content/ttw-performance-guide nvsr_older_processors] file of INI edits from the first post on the linked TTW page.
** [http://www.nexusmods.com/newvegas/mods/45104/? Mission Mojave Ultimate Edition - FNV Community Patch (MMUE)] (and it's various optional mod compatibility patches),
+
::* Those with later processors are advised to use '''NVSR_4-1-36 or later''' with the [https://taleoftwowastelands.com/content/ttw-performance-guide nvsr_newer_processors] file of INI edits from the first post on the linked TTW page.
** [http://www.nexusmods.com/newvegas/mods/44204/? New Vegas Enhanced Content (NVEC)] (notice it has "bugfix" modules if you don't want the "complete version" with enhancement mod inclusions).
+
::: (The only differences for 4.1.36 should be removing the overrides for previous versions as they aren't needed.)
 +
::: These INI edits are advised as performance settings suitable for FO3, FNV, and TTW.
 +
:* [http://nvse.silverlock.org/ New Vegas Script Extender] "Sheson memory patch". (Increases "heap size".  Use either the "heap replacement" feature of NVSR or this.  Both together do not conflict (different "heaps"), 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|Issue: CTD without warning, "out of memory error", or stops responding]] sub-topic for simple but detailed instructions for enabling this feature.
 +
:* [http://www.nexusmods.com/newvegas/mods/51664/? Yukichigai Unofficial Patch (YUP)] (and the various optional patches for it and other mods.  Highly recommended.  There are other YUP patch files than on that page you may have to search out for other mods).
 +
:* [http://www.nexusmods.com/newvegas/mods/45104/? Mission Mojave Ultimate Edition - FNV Community Patch (MMUE)] (and it's various optional mod compatibility patches).  <span style="margin:0px 10px 10px 0px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Use either YUP or MMUE, but not both as they overlap considerably and cause unresolved conflicts.  YUP is more actively updated.</span>
 +
:* [http://www.nexusmods.com/newvegas/mods/44204/? New Vegas Enhanced Content (NVEC)] (optional: Notice it has separate "bugfix" modules if you don't want the "complete version" with enhancement mod inclusions).
 +
:* [http://www.nexusmods.com/newvegas/mods/51871/? Better Game Performance] (optional: some reports of minor slowdowns.  It removes "unessential" things that some mods or quests might rely upon).
 +
 
 +
<span id="Issue: Vanilla game CTDs on startup"></span>
 +
 
 +
=== Issue - Vanilla game CTDs on startup ===
 +
Uninstalled and re-installed the game but even without mods it crashes on startup.
 +
* Cause-1: Likely you forgot to clear out your "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder when you had Steam "verify local files".  The game places your specific versions of the "Fallout" and "FalloutPrefs" INI files there, along with your save games.  These are not replaced when you verify/re-install the game if they are found to already exist there.
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 50px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">
 +
Note that if you are currently or have used "Mod Organizer", MO uses its own copies of "Fallout.ini" and "FalloutPrefs.ini" (from when the MO profile was created), located in "\Steam\steamapps\common\Fallout New Vegas\Mod Organizer\profiles\<Your Profile Name>". These files need to be changed as well.</div>
 +
 
 +
:* Solution-1a: Try renaming the "Users" folder INI files first.  Recall that the "Prefs" INI file gets created only when you run the original "FalloutNVLauncher.exe" and identify your hardware under "Options" on the first menu.  Subsequently if that fails move the "saves" elsewhere, delete that "Users" FalloutNV folder's content, and re-install again.  If you have to re-install again anyway, be sure to install to a folder that is not under the default "C:\Program Files" folder tree.  See [http://wiki.nexusmods.com/index.php/Installing_Games_on_Windows_Vista%2B Installing Games on Windows Vista+] for the rationale and guidance.
 +
 
 +
:* Solution-1b: Consider if the problem happens with other Steam games.  If so, check out the [[#Issue: Problems point to Steam as the source|Issue: Problems point to Steam as the source]] entry.
 +
 
 +
* Cause-2: A third-party program running in the background is interfering with the game.
 +
:* Solution-2: Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc.; at least on a temporary basis to see if they are interfering.
 +
 
 +
* Cause-3: In mid 2016, nVidia and AMD driver updates and some Windows 10 WDDM updates started to cause CTDs upon startup to previously trouble-free games.  This was determined to be caused by changes to the "Windows Device Driver Kit" (WDDK) at that time.
 +
:* Solution-3a: Win10 November 2016 updates have fixed these issues.  Make sure you have applied your system updates.
 +
 
 +
:* Solution-3b: The "[http://www.nexusmods.com/newvegas/mods/53635/? New Vegas Anti-Crash]" (NVAC) mod as of v7.5.0.0 (released 25 Oct 2016) has been reported to fix the conflict with the broken video drivers from nVidia and AMD.
 +
 
 +
:* Solution-3c: Rolling back to nVidia drivers 368.81 or 368.69; or AMD driver 16.8.3 have been reported to successfully resolve the problem with Win10.  In general, avoid upgrading your video card drivers unless the latest fixes a particular problem you are encountering.  (Support and testing for older games can get dropped in newer versions.)  To prevent Win10 automatically doing such upgrades to any drivers in future updates, see this article on [http://www.makeuseof.com/tag/take-back-control-driver-updates-windows-10/ Taking back control of Windows 10 driver updates].
 +
 
 +
:* Solution-3d: Depending upon the nature of the Windows update (all updates provide a link to a MS Knowledge Base article explaining the update in detail), reverting to the "system restore point" prior to the update may be a reasonable temporary solution if this occurs in the future.  However, in the long term this might prove to be a security risk, so be sure to report the problem and track the status of the update for possible fix and re-release.
 +
 
 +
<span id="Issue: Vanilla game Hangs on startup"></span>
 +
=== Issue - Vanilla game Hangs on startup ===
 +
When you open the launcher, it functions as it should with the music in the background. Also have audio by the time the main menu loads. Whenever you load a game, the loading screen with the roulette wheel has no audio and this screen will freeze for one to two seconds (as evidenced by the ball in the roulette wheel stopping). Screen will then go black for a few seconds, and the game will load, but have no audio at this point and there is severe lag.
 +
 
 +
* Cause-1: Win10 has DirectX12 drivers, but the DX9 driver the game is expecting is not being found.
 +
: While Win10 comes with DirectX12 installed and is backwards compatible with older DX versions, older games do not know that and are looking for specific versions of DX library files (i.e. d3d9'''''_32'''''.dll) and not finding them.  So you need to install the appropriate "DirectX End-User Runtimes" as well: ones which are compatible with Win 8.1+.<span style="margin:0px 10px 10px 10px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Note that you need the 32-bit version for 32-bit games.</span>  (I make it a practice to always download both the 32-bit and the 64-bit versions of any libraries I manually install, so I am covered either way.  There is a reason they published a version for both 32-bit and 64-bit.  They are not "interchangeable", and are separate installs going into different locations.)
 +
: (Games that used DX7 and 8 are murky territory. Many will run on OS's newer than XP, but may require fixes/tweaks.  Always use the latest available "runtime" versions of those DX libraries.)
 +
: Some games try to install an older DX version they come bundled with.  Those versions may not be compatible with the later versions of Windows, which is why you should manually install the version you know is compatible.  Then those games will see that DX version is already installed and not try to install their bundled version causing incompatibility problems.
 +
 
 +
:* Solution-1: For DX9, manually install the [https://www.microsoft.com/en-us/download/details.aspx?id=8109 DirectX End-User Runtimes (June 2010)] which is Win 8.1+ compatible.  Download the full runtime package.  DO NOT use the "Web Installer" version.
 +
::* When the DX installer asks where to install the files to, you choose any folder you like, but generally have it unpack the files to a folder on the desktop or one dedicated to that purpose anywhere, because this folder can be deleted or emptied after the final install is done.  (DirectX does not actually get installed at this point. The files are only 'unpacked' from an archive)
 +
::* Once the files are unpacked to this folder you open the folder and locate DXSETUP.exe (the actual installer).
 +
::* Run this installer (as an Administrator) to finalize the DirectX re-installation.
 +
::* When the installer is finished delete this folder.
 +
:: Each game uses a specific DX file, or files,  (e.g. d3dx9_32).
 +
:: A newer game may use two DX files (e.g. d3dx9_42 and d3dx10_42).
 +
:: See the MS article [https://answers.microsoft.com/en-us/windows/forum/games_windows_10/how-to-make-win10-run-directx-90/c7b61bc6-0b5e-4233-aefe-cfbe3c49d930 How to make Win10 run DirectX 9.0] for more details.
 +
 
 +
* Cause-2: The game is not finding all the asset and resource files it requires.  Especially under Windows 10, some files upon installation can get "black listed", which means they get deleted immediately without the installer realizing it.
 +
 
 +
:* Solution-2a: If you haven't already, move the game out of the default "C:\Program Files" folder.  See the wiki article [http://wiki.tesnexus.com/index.php/Installing_Games_on_Windows_Vista%2B Installing games on Windows Vista+] for instructions.
 +
 
 +
:* Solution-2b: If your graphics card is an "Intel" brand or on-board graphics chip, you need to install the mod [http://www.nexusmods.com/fallout3/mods/17209/? Intel HD graphics Bypass package] (from the FO3 section of the Nexus mod site but it works for FNV as well).  This "by-passes" an issue with those chips by placing an expected DLL file in the game root folder.
 +
 
 +
:* Solution-2c: Some have reported that playing in "windowed mode" (see [[#Issue: Playing at greater than 1920x1080 resolution|Issue: Playing at greater than 1920x1080 resolution]], Solution-2) has made the game playable when other solutions didn't.
 +
 
 +
:* Solution-2d: If you are having any audio problems, check the manufacturer of your sound card for any updated drivers.  The "default" drivers provided to the manufacturer of your computer or included with the original install of Windows may have updates that fixed problems surfacing after that point in time.  Microsoft does not always distribute the latest versions of all subsystem drivers.
 +
 
 +
:* Solution-2e: There are "behind the scenes" interactions between the video, sound, and mouse subsystems.  Logitech brand mouse drivers have a long history of their more advanced features causing problems with games (such as the "jump to new button" or "locate cursor" features).  Other vendor products are not immune to similar problems.  Try using only the basic features and gradually add features after testing.  If that is not sufficient, then see if an updated driver helps.  Consider as well the possibility of rolling back to a previous driver which was known to work.
 +
 
 +
:* Solution-2f: If you are still having problems, then you need to determine which assets are missing.  Install the 32-bit version of the [http://www.dependencywalker.com/ Dependency Walker] tool.  Then run "Dependency.exe", pointing to the game EXE to examine.  You are looking for red entries which signal "missing assets", which means it is not finding files the game requires.  Some of these will be Windows system files (typically 32-bit versions if you are running a 64-bit system; which is expected).  Initially you are looking for missing game files.  If there are none, then either the game files are corrupted or the "load order" needs to be fixed.
 +
::* If you have more than a few "missing assets" (i.e. files from Steam for Windows compatibility), then fire up the game with the Steam Client in "online mode" and launch it from the Steam Library (so it will install those assets it considers "temporary" while in game that it installs upon launch.  If you can get to the main menu in "windowed mode", use <Alt+Tab> to switch out of the game and then run "Dependency.exe" again against the game EXE file (while it is loaded into memory).  You should now find all or most of those "red" entries are now "black".
 +
::* If you still have "missing assets" from the game the files may be corrupted (in which case you can try to re-install or "verify local files"), or they are getting "black listed", in which case you may need to install them while in "Safe Boot" mode.
 +
::* Otherwise, make note of which are missing and seek assistance on the [https://forums.nexusmods.com/index.php?/forum/350-new-vegas-technical-support/ New Vegas Technical Support] forum.  Be sure to include your version of Windows, hardware specs, where you have the game installed, and what steps you have already taken.
 +
 
 +
== Solutions to Performance problems ==
 +
 
 +
<span id="Guide: Performance Tutorial Videos"></span>
 +
=== Guide - Performance Tutorial Videos ===
 +
 
 +
As many people prefer to view a video over reading instructions, the following "performance setup" tutorials are recommended:
 +
 
 +
*[http://www.youtube.com/watch?v=sJOrDhghr60 Fallout New Vegas | FPS & Stability (definitive guide)] 12:11 minutes, 2018 video by '''GamerPoets'''.
 +
::See also [[#Issue: TTW Performance Guide abstract|Issue: TTW Performance Guide abstract]].
 +
*[http://www.youtube.com/watch?time_continue=488&v=plWow9dGI70 Modding Fallout NV 'Ultimate Edition' part 7&nbsp;: Performance] 19:05 minutes, 2012 Video by '''Gopher'''.
 +
 
 +
:
 +
::Please bear in mind that there are later alternatives to many of the specific mods he mentions in this video if any of them don't work for you. 
 +
 
 +
Videos usually do not cover any particular part of their subject in depth. They are useful for getting started, but as they are seldom updated written guides are intended to provide more supplementary information when you encounter difficulties.
 +
 
 +
<span id="Issue: FPS drops over time"></span>
 +
=== Issue - FPS drops over time ===
 +
 
 +
*Cause-1: This problem has been associated with [https://www.nexusmods.com/newvegas/mods/42180/ FNV Project Reality MkI] by '''JJC71''' settings. (E.g. Initial FPS around 60, but over time it drops to roughly 30 FPS.) The mod was last updated in 2011.
 +
 
 +
:
 +
:*Solution-1: Go into "Mod Configuration Manager" (MCM) and enable all the options in '''Project Reality''', then exit out of MCM and wait a few seconds. Now go back in and disable all the options under '''Project Reality''' in MCM again. Instantly your FPS should be restored to what it was initially. See the comments tab on the download page regarding other issues. 
 +
 
 +
*Cause-2: There is some fairly compelling evidence that the game's texture cache system "leaks memory" over time. This generally means it allocates memory but fails to release it all properly when no longer needed; eventually leading to lowering FPS and CTDs. There is evidence that larger image sizes (aka "higher resolution images") speed up the problem to occurring after roughly 20-60 minutes of play.
 +
 
 +
:
 +
:*Solution-2: While not really a "fix", try using "low graphics quality" settings to see if this increases the amount of time you can play before seeing the same symptoms. If so, this is an indicator such leakage is your problem. If you have "texture replacements", try switching to low to moderate resolution images (1024x1024 or 2048x2048 pixels; the game default size is 512x512). Choose what you replace with care. "Post-processors" such as ENB and SweetFX, as well as mods that "improve" images and textures (e.g. "Fallout Character Overhaul" (FCO), "New Vegas Redesigned" (NVR), and "Freeside Open") can also contribute to the problem due to their increased demand upon the video stream. Use such in moderation and with careful examination of their impact on performance over time. Remember that the game engine has not been updated since 2010. 
 +
 
 +
<span id="Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters"></span>
 +
=== Issue - '''Full screen mode''' exhibits CTDs and stutters or micro-stutters ===
 +
 
 +
*Cause: Newer or "high powered" systems seem more prone to exhibit these symptoms. Recall the game was designed for Windows Vista+ and Xbox systems with no more than two CPUs and single monitors at 60 FPS.
 +
 
 +
:
 +
:*Solution: Try running the game in "windowed mode". This is a built-in game setting (under "Options" when you use the "FalloutNVLauncher.exe" to start) that has been reported to completely eliminate both stutter/micro-stutter and CTDs on some "high powered" systems. 
 +
::If you don't like the appearance in "windowed mode", try installing and using the (2015) mod "[http://www.nexusmods.com/newvegas/mods/59266/? OneTweak for NVSE]" by '''virusek''' instead of the older (2011) "[http://rd.nexusmods.com/newvegas/mods/41381 Fake fullscreen]" mod suggested in Gopher's video, or the slightly newer, more full featured (2013) version called "[http://rd.nexusmods.com/newvegas/mods/42956 Game Companion - Fake FullScreen]". All of these make "windowed mode" look as if "full screen".
 +
::There is also an "open source" app called "[http://github.com/Codeusa/Borderless-Gaming Borderless Gaming]" which works with virtually any game (including those from Steam). It's free, but confusingly talks about "buying it on Steam"; by which it means if you do choose to buy it ($3.99 USD) the proceeds support it's development. 
 +
 
 +
<span id="Issue: Game in slow motion"></span>
 +
=== Issue - Game in slow motion ===
 +
 
 +
The foundation of game performance is to first optimize your system for gaming. The wrong settings can actually hurt performance, and the defaults are very conservative.
 +
 
 +
*[http://www.nexusmods.com/newvegas/mods/53635/? New Vegas Anti-Crash (NVAC)]
 +
*[http://www.nexusmods.com/newvegas/mods/34832/? New Vegas Stutter Remover (NVSR)] (Win 10 users: See also [[#Issue:_CTD_after_10-20_minutes_of_play_.28post-Win10_2017_FCU.29|Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)]].
 +
*[http://www.tweakguides.com/TGTC.html Complete System customization and optimization for Windows].
 +
* [https://web.archive.org/web/20161008023921/http://www.tweakguides.com/TGTC.html Complete System customization and optimization for Windows].
 +
* [https://web.archive.org/web/20161004212522/http://www.tweakguides.com/ATICAT_1.html Tweakguide's ATI Catalyst Guide] (driver optimizations for all games.)
 +
* [https://web.archive.org/web/20160719081231/http://www.geforce.com/whats-new/guides/new-vegas-tweak-guide#1 Tweakguide's nVidia GeForce Guide] (driver optimizations for all games.)
 +
* [https://web.archive.org/web/20161025065631/http://www.tweakguides.com/Fallout3_1.html Tweakguide's General Fallout game guide] (specifically for FO3 and FNV.)
 +
*[http://www.geforce.com/whats-new/guides/new-vegas-tweak-guide#1 Tweakguide's nVidia specific FNV Guide.]
 +
 
 +
[[File:FNVLauncher OptionsMenu Detail.jpg|thumb|LauncherOptionsDetail Figure]] The "FalloutNVLauncher" "Options" screen has a section labelled "Detail" in the middle of the screen. This has four buttons labelled "Low", "Medium", "High", and "Ultra". (See [[:File:FNVLauncher_OptionsMenu_Detail.jpg|LauncherOptionsDetail Figure]]. {{Thumbnail_enlargement_message}}) These are predefined sets (presets) of specific graphics setting configurations, the details of which can be found in INI files of the same names (e.g. "Low.INI") located in the game root folder. Most of these same settings can individually be adjusted by selecting the "Advanced" button in that section. They are described in the "TweakGuide's General Fallout game guide" article. &nbsp;The Launcher runs DirextX diagnostics to determine video card capabilities in determining which preset to recommend.&nbsp; They DO NOT (as has been suggested elsewhere) have anything to do with image sizes or resolution.
 +
 
 +
'''Queued''', the author of the NVAC mod, reports in the [https://forums.nexusmods.com/index.php?/topic/1197661-nvac-new-vegas-anti-crash/page-352#entry15646425 NVAC support thread]:
 +
<blockquote>
 +
'I looked through New Vegas code as I was making that list to determine if they read the setting and then if they actually used the variable set after reading the setting, so I'm fairly confident in the "Does nothing" notes in particular. Aside from INI settings, there is also a crazy amount of Game Settings (set via esp / esm / script / console) that also are never used by the game.'
 +
</blockquote>
 +
:The "list" he mentions was from the tool [http://www.nexusmods.com/newvegas/mods/40442/? New Vegas Configator], which outside of that program must be translated to settings in the INI files as described in "Tweakguide's General Fallout game guide". It follows with '''Queued''''s comments on the values (which are ''not'' recommendations) used by someone having CTDs, given in "("parentheses")" for reference only:
 +
:*Fullscreen (OFF) - No problem.
 +
:*Anisotropic Filtering (8) - No problem.
 +
:*Antialiasing (8x) - No problem, though 8x is ridiculously taxing; traditional MSAA is crazy inefficient and slow.
 +
:*Shadows (ON) - No problem.
 +
:*Shadow Quality (2) - No problem.
 +
:*Shadow Filtering (2) - No problem.
 +
:*Max Shadows in Interiors (12) - No problem.
 +
:*Full Scene Reflections (ON) - Probably fine; I'm not sure which setting this maps to as the Configator made up descriptive names.
 +
:*Water Reflections Width (2048) - No problem, though is Height also set to match?
 +
:*Object fade distance (15) - No problem.
 +
:*Item fade distance (15) - No problem.
 +
:*Actor fade distance (15) - No problem.
 +
:*Tree LOD fade (80000) - Technically no problem, but as far as I'm aware, vanilla New Vegas doesn't use the Tree LOD system and Tree LOD models are part of Object LOD instead.
 +
:*Object LOD fade (100000) - No problem.
 +
:*Land Quality (1.5) - No problem.
 +
:*Threaded Morpher (ON) - Does nothing; the game reads the value but never uses it.
 +
:*Threaded Blood (ON) - Does nothing; the game never even reads this value.
 +
:*Threaded Particles (ON) - Does nothing; the game reads the value but never uses it.
 +
:*Threaded AI (ON) - Possible cause of crashes; use at your own risk.
 +
:*Models Cloned in Background (ON) - Does nothing; the game never even reads this value.
 +
:*Load Files in Background (ON) - Likely safe; however, use at your own risk.
 +
:*Load lip files in background (ON) - Unknown impact; use at your own risk.
 +
:*Havok Threads (7) - Does nothing; the game never even reads this value.
 +
:*Grids loaded (12) - LEAVE THIS AT 5. This needs to be an odd value (5, 7, 9, etc.) and the game has code that only works properly when this is at the default of 5. Turning this up drastically increases memory and processor use. Also, this is probably why you're crashing outdoors. [Larger values may cause scripts to prematurely trigger upon cell loading.] 
 +
 
 +
Added: Note that 'uGridsToLoad=' is directly linked with 'uInterior Cell Buffer=' and 'uExterior Cell Buffer=' values. Best to leave all three alone.
 +
 
 +
:
 +
:*Pre-Emptively Unload Cells (ON) - Possible cause of crashes; use at your own risk.
 +
:*Unload cells on fast travel (ON) - Possible cause of crashes; use at your own risk.
 +
:*Use hard drive cache (ON) - Unknown impact; use at your own risk.
 +
:*Preload Size Limit (223) - Dumb setting; this is the data buffer for Bink video. 
 +
:Others who have looked at the code do not disagree with '''Queued'''.
 +
:As system components vary, only experimentation will tell which values will improve your performance.
 +
 
 +
*Cause-1: Fallout INI files are configured with wrong (too high) an "iFPS=" setting.
 +
 
 +
:
 +
:*Solution-1: Set the "FPS" setting to a maximum of "=60". 
 +
::Note that too high an FPS over 60 can cause a "havok physics" problem with objects falling from clipping through geometry.
 +
:::Make backups of the INI files before changing them. 
 +
::*The Fallout INI files have an "iFPSClamp=" setting under the "[General]" section. Do not set this to other than "=0" if you have NVSR "bManageFPS = 1".
 +
::*New Vegas Stutter Remover (NVSR) "Data\nvse\plugins\NV_Stutter_Remover.ini" has to have "bManageFPS = 1" under the "Master = {" section before the setting "MaximumFPS = 60" under the "FPS_Management = {" section will take effect. Check that the "MinimumFPS" setting is not higher than the maximum; something like "= 20" is noticeable while still playable. If NVSR is managing FPS, do not leave the three Fallout INI files with a setting other than "iFPSClamp=0".   
 +
 
 +
*Cause-2: For some people, the problem is [http://www.nexusmods.com/newvegas/mods/34832/? New Vegas Stutter Remover (NVSR)] "Data\nvse\plugins\NV_Stutter_Remover.ini" has "bManageFPS =" set to something other than 0.
 +
 
 +
:
 +
:*Solution-2: Edit the "NV_Stutter_Remover.ini" setting to "bManageFPS=0" and have the three Fallout INI files use "iFPSClamp=60" or less. 
 +
::
 +
:::Make backups of the INIs before changing them.   
 +
 
 +
*Cause-3: Many mod scripts running, especially during mod initialization. If specifically in Goodsprings, be aware that the "Weapons.of.the.New.Millenia" "cache cabinet"/"cheat chest" is known to cause this, but only in Goodsprings.
 +
 
 +
:
 +
:*Solution-3: Review your mods and reduce the number that initialize only in that specific area. 
 +
 
 +
*Cause-4: This seems to be a general problem with the FO3/FNV Gamebryo engine over time. The exact cause has not been pinned down.
 +
 
 +
:
 +
:*Solution-4: Reboot your computer. This seems to restore things to normal frame rates, at least for a time. 
 +
 
 +
*Cause-5: You are running Windows 10. Win10 is not the best platform for running older, 32-bit games. It flat out says it is incompatible with FO3 for instance. It is easy to demonstrate that even in various "compatibility modes" it is not performing the same as under previous versions. (Though try either "Win7" or "VistaSP2" compatibility mode. Some have reported improvement after the Win10 FCU {aka "Redstone 3"} update by disabling any compatibility mode.) One report went from 10-15 FPS (or less) with Win10 on a high-end desktop box to 30-40 FPS with Win7 on an older laptop.
 +
 
 +
:
 +
:*Solution-5a: If possible, use a dedicated computer with an older OS such as Win7 for your 32-bit games. 
 +
 
 +
:
 +
:*Solution-5b: For advanced users: If you have a Windows 10 Education, Professional, or Enterprise edition you can use the included '''Win10 Hyper-V system''' and try running the game in a Win7 "virtual machine". A "virtual machine" can get around some OS incompatibilities even though it is running on the same hardware due to the different drivers in use. See [https://msdn.microsoft.com/virtualization/hyperv_on_windows/quick_start/walkthrough_compatibility HyperV on Windows compatibility] for the hardware requirements and a walk-through of the installation process. Note this requires you to have or obtain an ".iso" file of the desired OS install media. (If none of this option makes sense, you probably don't want to mess with it. Otherwise, educate yourself as it is beyond the scope of this wiki.) 
 +
 
 +
*Cause-6: Your hardware can't cope.
 +
 
 +
:
 +
:*Solution-6: either reduce game settings for texture quality and/or screen resolution to less demanding levels, or invest in better hardware. 
 +
::
 +
::*Ensure you are using any Graphics card with it's own VRAM instead of your motherboard CPU to display and render your game. This means, if you have both an "addon" graphics card and a "builtin to the motherboard" graphics chip, use the addon card. An "onboard" graphics chip (typically without VRAM in a laptop) has to use "system ram", which is both slower than dedicated video VRAM, but also takes that memory away from what the game can use. This would just be a video driver (or possibly a BIOS selection) configuration change. 
 +
::Specific component upgrades recommended are (in order of effectiveness for the price):
 +
::*System RAM,
 +
::*More Video RAM in a faster graphics card,
 +
::*Faster CPU processor (number of cores is much less important for 32-bit games like FNV; but this option will often require a motherboard and/or power supply upgrade as well, typical making it more expensive than any other options overall),
 +
::*Faster disk drive. (This is the slowest solution; even an SSD, though that is the best choice for this option, is not really suited to games. It's most effective holding the OS.)   
 +
 
 +
<span id="Issue: Graphics (vanilla game) "glitchy" immediately after exiting Doc Mitchell's"></span>
 +
 
 +
=== Issue - Graphics in vanilla game ''glitchy'' immediately after exiting Doc Mitchells ===
 +
 
 +
Unless the camera is pointed at the sky or your feet, the ground and all other textures disappear. Messages would become "black boxes", the entire screen becomes black and occasionally flash different colors. Just "glitchy". Eventually after a short period of time the game will CTD.
 +
 
 +
*Cause: You have some incompatible video settings.
 +
 
 +
:
 +
:*Solution: Re-run the game launcher (FalloutNVLauncher.exe) to re-detect your hardware. Try changing between "HDR" and "Bloom" in the game "Graphics Settings" under the game launcher menu. Note you want your video card adapter settings to be compatible with your game settings. Other common settings that may have been or need to be adjusted can be found the [[#Issue:_ENB_is_not_working|Issue: ENB is not working]] entry. See also the [[#Solutions_to_Graphics_problems|Solutions to Graphics problems]] section for other possible conflicts. 
 +
 
 +
<span id="Issue: Lag or "microstutters" even with "New Vegas Stutter Remover" installed (or not)"></span>
 +
=== Issue - Lag or ''microstutters'' even with '''New Vegas Stutter Remover''' installed or not ===
 +
 
 +
All visual stuttering problems are caused by the video stream having to wait for the "art assets" required to render the display. Mostly these are due to the disk drive being orders of magnitude slower than VRAM, with System RAM (e.g. "ENBoost") being in between.
 +
 
 +
"Microstuttering" is caused by the game engine updating at an unusual refresh rate that does not sync with your monitor's refresh rate. You can try getting NVSE and NVSR to alleviate "microstutter" at the cost of overall frame rate.
 +
 
 +
Keep in mind that this game was designed for older PC and XBox console systems, and it is now possible for your new "latest and greatest" gaming machine to be faster than it can handle. There are internal design choices that cannot be overcome. The following are "mitigations" that have been found to help some people.
 +
 
 +
*Cause-1: Companions impose heavy script processing penalties. More than two companions, while possible, will definitely cause lag according to the game developers. The game is unable to tell if a vanilla companion is "actually with you" or merely "befriended" but sitting elsewhere in another cell (such as in the Lucky 38 suite).
 +
 
 +
:
 +
:*Solution-1: Release ("part ways" from) unused companions to return to where they were recruited. If you are not informed you have lost the Perk granted by that companion, you have not actually "released" them. There are "companion dismissal terminals" found in the game to help with this for companions, even those not currently with you. One is found in the Lucky 38 Casino by the Casino floor elevator and another in front of the Gun Runners HQ shack outside Freeside's East gate. 
 +
 
 +
*Cause-2: Use of NVSR setting "bHookLightCriticalSections=1".
 +
 
 +
:
 +
:*Solution-2: Disable NVSR hooking Critical Sections ("bHookLightCriticalSections=0)" if you are experiencing heavy stutter or see [[#Issue:_Recent_.28post-Win10_FCU.29_CTDs_after_10-20_minutes_of_play|Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play]]. 
 +
 
 +
*Cause-3: The stutters can come from the game looking for control inputs from the attached game controller device first, then the keyboard/mouse though both are enabled.
 +
 
 +
:
 +
:*Solution-3: Disconnect the controller if you are not using it. Regardless, in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV\FalloutPrefs.INI" file look for "bGamePadRumble=" and ensure it is set to "0". 
 +
 
 +
*Cause-4: Video card settings are not optimized for the game.
 +
 
 +
:
 +
:*Solution-4a: nVidia - There is a third-party tool called [http://download.orbmu2k.de/download.php?id=51 nVidia Inspector]. (The author's [http://orbmu2k.de/tools/nvidia-inspector-tool#more-244 blog page] is in German, but does not appear to have been recently updated.) There is a [http://www.youtube.com/watch?v=syE55-jEzb8 Increase nVidia GTX performance with nVidia Inspector] video covering the basics of how to use the non-intuitive interface. If you are launching the game from any renamed executable other than the vanilla name (i.e. "FalloutNV.exe", which MO renames to "FalloutMO.exe"), you need to add it to the nVidia profile so it will recognize that name as "the game" and adjust it's performance settings accordingly. 
 +
::
 +
:::The driver profile for FNV/FO3 "Ambient Occlusion" (AO) is reported to be buggy ever since nVidia updated it to HBAO instead of SSAO years ago. You can use '''nVidia Inspector''' to change the AO profile though. The '''Wolfenstien profile''' is reported to work pretty well.   
 +
 
 +
:
 +
:*Solution-4b: There is a later spin-off of '''nVidia Inspector''' called [http://pcgamingwiki.com/wiki/NVIDIA_Profile_Inspector NVIDIA Profile Inspector], which is a tool created for pulling up and editing Application Profile settings within the Nvidia drivers. 
 +
 
 +
:
 +
:*Solution-4c: AMD/ATI - [http://www.amd.com/en-gb/innovations/software-technologies/catalyst AMD Catalyst Control Center] has game settings for CCC as well. While not as full featured as "nVidia Inspector", there is also [http://www.radeonpro.info/2013/04/download-radeonpro-preview-1-1-1-0-13apr2013-with-improved-overdrive-and-sweetfx-1-4-support/ Radeon Pro] which still works well even though development stopped in 2013 when it's author was hired to work with [http://www.radeonpro.info/2014/03/important-announcement-about-radeonpro/ AMD Gaming Evolved's Raptr]. 
 +
 
 +
*Cause-5: Some older video systems may have to pull from the hard drive more often or need more processing room with "high definition" textures.
 +
 
 +
:
 +
:*Solution-5a: [http://www.auslogics.com/en/software/disk-defrag/ Disk Defrag] (free) your hard drive. All hard drives that are not "solid state devices" (SSDs) require "defragmentation" periodically. This reduces the lag from the physical magnetic "head" movement to locate sections of file scattered the disk platter and increases efficiency. 
 +
 
 +
:
 +
:*Solution-5b: See the '[[#Issue:_Is_ENBoost_for_everyone.3F|Issue: Is ENBoost for everyone? ]]' entry which enables the dynamic use of more system memory (if available) to assist video processing. Some people have found this to help with stutters and lag. 
 +
 
 +
*Cause-6: Some people have reported an improvement upon adjusting some INI settings.
 +
 
 +
:
 +
:*Solution-6a: In all three INI files, under the "[General]" section set the following values: 
 +
::<pre>bUseThreadedAI=1</pre>
 +
 
 +
 
 +
&nbsp;
 +
 
 +
:
 +
::and add the line:
 +
::<pre>iNumHWThreads=</pre>
 +
 
 +
 
 +
and set that to however many cores your processor has. Note this added line is not considered a general "performance" tweak (the game does multi-threading by default and the "iNumHWThreads=" setting may restrict it) and is not recommended for everyone as a matter of course. Some people have experienced adverse effects. Use with caution and test the result. When in doubt, start with "2".
 +
 
 +
:
 +
:*Solution-6b: Some "sounds", such as large explosions, can cause video stuttering as well. (The video, mouse, and audio systems are all interconnected in that they compete for priority of resources at the same high level.) Some have found that adding more vanilla BSA files to the "sEssentialFileCacheList=" list under "[General]" in the INI files makes a difference. For example: 
 +
<div class="boilerplate metadata" id="Notice_Box" style="margin:0px 10px 10px 50px;  border:1px dashed #DAA520;  color: lightgray;  background-color:#333333;  padding:3px;  word-wrap: break-word">sEssentialFileCacheList=Data\Fallout.esm|Data2\Fallout.esm, Data\Music\Special\MainTitle.mp3, Data\Fallout - Sound.bsa|Fallout - Sound.bsa, Data\Fallout - Voices1.bsa|Fallout - Voices1.bsa, Data\Fallout - Meshes.bsa|Data2\Fallout - Meshes.bsa, Data\Fallout - Textures.bsa|Data2\Fallout - Textures.bsa, Data\Fallout - Textures2.bsa
 +
sUnessentialFileCacheList=Data\Music\Dungeon\*.xma, Data\Music\Base\*.mp3, Data\Music\Battle\*.mp3, Data\Music\Explore\*.mp3, Data\Music\Public\*.mp3, Data\Music\Special\*.mp3
 +
</div>
 +
:
 +
::and increasing the size of the "Audio cache" under the "[Audio]" section as follows: 
 +
<div class="boilerplate metadata" id="Notice_Box" style="margin:0px 10px 10px 50px;  border:1px dashed #DAA520;  color: lightgray;  background-color:#333333;  padding:3px;  word-wrap: break-word">iAudioCacheSize=4096
 +
iMaxSizeForCachedSound=512
 +
</div>
 +
:
 +
::This basically allows the game to cache much more into memory then it otherwise would, as it seems textures and meshes are excluded from memory, as well as large sound effects, resulting in a momentary freeze whenever they are loaded. May not stop a slight lag on the first explosion, but should greatly reduce any lag on explosions shortly after that. Just bear in mind that memory given to "cache" is not available for other uses by the game engine. There is always a "trade-off". 
 +
 
 +
*Cause-7: Some people has reported stuttering while standing in place and turning the camera.
 +
 
 +
:
 +
:*Solution-7: Try disabling Windows [http://www.technipages.com/windows-enable-disable-superfetch Superfetch] and [http://helpdeskgeek.com/windows-7/windows-7-file-search-indexing-options/ File search indexing] features (available since Win7) to see if it improves the situation. (See [http://www.osnews.com/story/21471/SuperFetch_How_it_Works_Myths Superfetch: How it Works & Myths] for more detail.) Note that Windows system updates may restore these settings without notice as something MS thinks should be enabled. 
 +
 
 +
*Cause-8: Writing files to disk is the slowest thing the game does. Whether these are "save game files" or "logs", you want to minimize the number of times these get written.
 +
 
 +
:
 +
:*Solution-8a: Disable game logging unless you have an immediate need for it. 
 +
 
 +
:
 +
:*Solution-8b: If you are using CASM or some similar "auto-save" mod to manage your save game files (recommended), try increasing the "time between saves" set in the "save frequency"; and reducing the number of occasions it saves to the minimum (e.g. disable most "Autosave Events" in CASM) and see how that impacts the game seeming to freeze temporarily. 
 +
 
 +
:
 +
:*Solution-8c: The one modern thing the game does benefit from is being put on an SSD. Load times aren't improved that much; but stutter is greatly reduced, and the pause when the game autosaves with CASM is gone. 
 +
 
 +
* Cause-9: See also [[#Issue_-_MOD_IMPACT_-_FPS_drop_or_stutter_on_semi-auto_hits|Issue - MOD IMPACT - FPS drop or stutter on semi-auto hits]].
 +
 
 +
* Cause-10: There is a known game engine bug when firing a weapon that uses multiple projectiles (e.g. "shotguns").
 +
:* Solution-10: The mod [http://www.nexusmods.com/newvegas/mods/58277 JIP LN NVSE Plugin] has a solution for this: "bMultiProjectileFix - Fixes an engine bug where using weapons which fire multiple projectiles per shot could often cause brief lags and FPS drops when hitting live targets."  Reportedly, it'll still lag if the number of pellets the shotgun fires is large, but vanilla numbers should be fine.
 +
 
 +
<span id="Issue: MouseSensitivty"></span>
 +
=== Issue - Mouse sensitivity reduced ===
 +
Symptoms: Mouse sensitivity inside any interior is about half that of the value in exteriors.
 +
 
 +
* Cause-1: "[https://geckwiki.com/index.php?title=ImageSpace Image Space]" systems can configure the base display effects for a cell or worldspace. This would allow designers to drive post-processed "film" effects through the editor, giving much greater control and more of a "film" feel. Some of the effects include blurring, coloring, and HDR/Bloom effects. The ImageSpace form can be opened from the [https://geckwiki.com/index.php/World_Spaces World Spaces] menu.  Mods can make edits which damage how these work.
 +
:* Solution-1: The mod "[https://www.nexusmods.com/newvegas/mods/42847/ PWV - Project Wasteland Vision]" makes some edits to "[https://geckwiki.com/index.php?title=ImageSpace_Modifier ImageSpace Modifier (IMOD)]" records for explosions, plasma, and scope FX.  Removing those edits with [http://www.nexusmods.com/newvegas/mods/34703/? FNVedit] resolved the problem for the reporting user.
 +
 
 +
* Cause-2: Mouse driver, especially some brand "additional features" such as accelerators.
 +
:* Solution-2a: Check the vendor brand support forums to see if there are any similar reports.
 +
:* Solution-2b: Start troubleshooting by disabling any optional mouse driver features, test, and then add desired features one at a time.
 +
:* Solution-2c: If you have more than one mouse available, try swapping out brands.
 +
:* Solution-2d: Try an older version of the driver as well, as later versions often drop support/testing for older games.
 +
:* Solution-2e: There are hidden interactions between the Audio, Mouse, and Video drivers.  If there has been a recent update to one of these, test by rolling it back to the previous functional version to see if there is an improvement.
 +
 
 +
<span id="Issue: NPCs and Creatures are moving at "hyper-speed""></span>
 +
 
 +
=== Issue - NPCs and Creatures are moving at ''hyper-speed'' ===
 +
 
 +
See video [https://youtu.be/iV1V4P1uMjM FNV hypersped NPCs] for an example. The NPCs in the background are following their AI routines at a greatly accellerated speed or twitching while standing idle.
 +
 
 +
*Cause: There is an '''actor value''' called "speedmult" that does pretty much as the name implies; it's a multiplier for player and NPC movement speed. The default value is 100. In fact, its rare to see any humanoid with a speedmult greater than 100. So ranges from 700-27000 are ridiculous, but a buggy script can have this result. Once such a bugged script gets into a "save game" it (or it's results) may be impossible to remove, so always know which save you can revert to before adding a new mod to your "load order". Just one of the reasons why any mod (even updates) needs to be tested prior to adding to your saved game.
 +
 
 +
:
 +
:*Solution: Isolate the mod causing the problem and report it to the author with detailed information as to how to replicate it so they can fix it. 
 +
::You can test by selecting any NPC exhibiting this behavior in the console (< ~ > key and click on the NPC) and entering "getav speedmult" to see the current value and "setav speedmult 100", which should set the speed back to normal. (The "getavinfo" version of the command gets the current value of a '''skill/stat''' like "speedmult" as well as any modifiers (but not their source) that are being applied at the moment.)
 +
::However, you need to get the NPC to "reload" before this reset value will take effect. One way is to use the console "kill" command after selecting the target NPC, and then "resurrect" them. They should then behave at normal speed for them. (Note the console "kill" command will blame your character for their death.) Do not target "leveled list" generic NPCs such as those in a "faction" like "Raiders", "NCR", "Legion", etc.. The "resurrect" command respawns a random one from the "leveled list". You can use "resurrect 1" to get the same one you targeted to "stand up" as they are at the moment (i.e. naked if you stripped them of gear) as if they had been unconscious. "Named" NPCs are the safest targets for such tests. 
 +
 
 +
*Known mods with the problem:
 +
 
 +
:
 +
:*The "JIP LN" version (contributed by someone else) of [http://www.nexusmods.com/newvegas/mods/63348/? Awesome Crippling Effects] mod by '''PsychorGames'''. The main "non NVSE/JIP LN" file version is confirmed to not have the problem. It seems the problem can persist in save games even after reverting to the "vanilla" (non NVSE) version until the above "setav speedmult 100" solution is applied. 
 +
::This mod has unresolved reported bugs which (as of v1.7) affect:
 +
::*'''Yes Man''' Quest: Change in Management - Because of the crippling effects, '''Yes Man''' dies when installing himself to the Mr. House terminal, breaking the quest, meaning that the quest doesn't progress and the Mr. House terminal cannot be interacted with.
 +
::*Securitrons in The Strip and/or Lucky38 suddenly become hostile for unknown reasons.
 +
::*Companions with crippled limbs stop following, or can't get up and the challenge "Knocked up" would get completed over and over again. 
 +
::There are reports that removal of the mod resolved these additional bugs.
 +
::Version 1.8 of this mod has now been released to address these issues. Confirmation is needed. Check the "Comments" and "Bugs" tabs on the mod download page. 
 +
 
 +
<span id="Issue: SOUND - Ambient music skips/jitters/hiccups/pops/stutters"></span>
 +
=== Issue - SOUND - Ambient music ''skips-jitters-hiccups-pops-stutters'' ===
 +
 
 +
The ambient music is choppy in both vanilla and modded games. This doesn't happen to the radio music during normal gameplay, but does during loading screens or transitioning between tracks (i.e. going from ambient "explore" music to "combat", or entering new locations with different music).
 +
 
 +
*Cause: Old advice for FO3 was to uninstall '''"ffdshow"''', a codec mainly used for decoding of video in the MPEG-4 ASP (e.g. encoded with DivX or Xvid) and H.264/MPEG-4 AVC video formats, but it supports numerous other video and audio formats as well. (The user configures '''ffdshow''''s audio and video settings by launching the '''"ffdshow video decoder configuration program"''' independently of any media player.) Alternatively one could try to add FO3 to it's "exception" list.
 +
 
 +
:
 +
:*Solution-1: FNV appears to require at least some of the codec features provided by '''"ffdshow"'''. If needed it can be re-installed as part of the [http://www.cccp-project.net/ CCCP codec pack] or directly from the [http://ffdshow-tryout.sourceforge.net/ ffdshow tryouts] website. (Alternative codecs may also provide the needed features.) Be sure to install the '''32-bit''' version, as that is what the game needs. Some have reported that only the '''"CCCP codec"''' (without '''"ffdshow"''') is needed. Install the same as any other '''Windows''' program. 
 +
::
 +
::*Remove '''falloutnv.exe''' and '''falloutnv4gb.exe''' programs from the list of '''"ffdshow"''' exceptions.   
 +
 
 +
:
 +
:*Solution-2: Edit the "Users" INI files under the "[Audio]" section, and change the following settings as indicated: 
 +
<div class="boilerplate metadata" id="Notice_Box" style="margin:0px 10px 10px 50px;  border:1px dashed #DAA520;  color: lightgray;  background-color:#424242;  padding:3px;  word-wrap: break-word">iAudioCacheSize=2048 to "=8192"
 +
iMaxSizeForCachedSound=256 to "=1024"<br/> bMultiThreadAudio=0 to "=1"
 +
</div>
 +
:
 +
:*Solution-3: De-fragment your disk drive and reduce background programs to the essential minimum. 
 +
 
 +
:
 +
:*Solution-4: The [http://www.nexusmods.com/newvegas/mods/61265 OGG Vorbis Libraries] have an update mod which has solved a stutter occurring every 15 seconds for some users. (These libraries are used by the vanilla game.) The '''Vorbis OGG Library''' is a set of DLL files which you have to manually install/copy into the game root folder (where the "FalloutNV.exe" file is found). Mod managers don't recognize or place them properly. They will need to '''''overwrite''''' the existing files. '''GamerPoets''' has a "[http://www.youtube.com/watch?v=KkVWoccWoXY Performance & Stability Guide]" YouTube video which covers this library at the 3:07 minute mark. (Note the different section timemarks are displayed at the top of the screen.) The mod [http://www.nexusmods.com/newvegas/mods/65854 FNV BSA Decompressor] transcodes all sound '''fx''' in ".*OGG" format to ".WAV" so they function in the game. It's installation is described at the 10:12 minute mark of '''GamerPoets''' previously linked "Performance & Stability" video. 
 +
 
 +
:
 +
:*Solution-5: You may need to use a '''Windows''' tool such as [http://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer Process Explorer] to track down which app or service is grabbing cycles. 
 +
 
 +
<span id="Issue: SOUND - Combat causes audio desync"></span>
 +
 
 +
=== Issue - SOUND - Combat causes audio desync ===
 +
Upon entering combat: an audio desync occurs for the duration of the battle. This desync is a long (5+ second) delay in audio effects, and during this delay cannot switch weapons using hotkeys.  Reported as an issue running "Tale of Two Wastelands".
 +
 
 +
* Cause: the AVAST anti-virus program specifically has been identified as causing this problem, even when "shields" are turned off and "falloutnv.exe" is excluded.
 +
:* Solution: Disable or uninstall AVAST anti-virus completely.
 +
:: If you play the game in "offline mode", you shouldn't need to have any anti-virus or anti-malware service running.  There are programs (search the web on "game boosters") which help you shut down services which are not essential while playing a game.
 +
 
 +
<span id="Issue: SOUND - Combat causes infinite loop sound"></span>
 +
 
 +
=== Issue - SOUND - Combat causes infinite loop sound ===
 +
 
 +
A "weird" AmbientFX (special effect) noise appears during combat (freqently by firing a Laser weapon) and won't terminate unless you either quit the game or reload a save game.<br/> (Thanks to users '''harlandgg''' for discovering the cause, and '''HadToRegister''' for reporting it to the FNV Forum so it could be included here.)
 +
 
 +
*Cause: Following instructions for installing the mod [http://www.nexusmods.com/newvegas/mods/64807? Vanilla Restored Audio Patch] causes the folder "\Data\Sound\fx\amb\steampuddle" to be installed/restored. The files in this folder do not appear to have set "loop end" points, causing them to play infinitely. This problem is common to EVE, YUP and UPP (Unofficial Patch Plus) users as they will flag ash/goo piles and impact sounds with ''AMBSteamPuddleLP''.
 +
 
 +
:
 +
:*Solution: Delete the entire "\Data\Sound\fx\amb\steampuddle" folder. (The rest of the mod works fine.) 
 +
 
 +
<span id="Issue: SOUND - No music or sound"></span>
 +
=== Issue - SOUND - No music or sound ===
 +
 
 +
(See also [[#Issue:_Radio_station_music_doesn.27t_play|Issue: SOUND - Radio station music doesn't play]] for that specific problem.)
 +
 
 +
*Cause-1: If this problem occurs when you first start the game, then it's likely there may be an audio "codec" conflict between what you have installed under Windows and what the game in question requires, or a necessary "codec" is missing. (A "codec" is a "DirectShow filter", and there is a chain of them in the registry establishing which order to try them in to determine which to use. "DirectShow" is a component of the DirectX (DX#) API system used by games running under Windows.)
 +
 
 +
:
 +
:*Solution-1a: Win10 has DirectX12 drivers, but the DX9 driver the game is expecting is not being found. See "Cause-1" under [[#Issue:_Vanilla_game_Hangs_on_startup|Issue: Vanilla game Hangs on startup]]. 
 +
 
 +
:
 +
:*Solution-1b: Some have found that installing a third-party "DirectX: DirectShow codec" resolves the problem. There are a number available on the internet. The [http://www.codecguide.com/ K-Lite Codec Pack] is often mentioned especially for older versions of Windows. Be sure to get the 32-bit version, as FNV is using 32-bit libraries. 
 +
 
 +
*Cause-2: 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 "[http://wiki.nexusmods.com/index.php/Fallout_NV_Mod_Conflict_Troubleshooting Fallout NV Mod Conflict Troubleshooting]" guide. This may be due to a Windows Update for the "Meltdown and Spectre Vulnerabilities".
 +
 
 +
:See also the related [[#Issue:_Incomplete_save_game_load|Issue: Incomplete save game load]].
 +
:*Solution-2a: Not all "codecs" are created equal, and sometimes Windows versions and specific games are very particular. Codec uninstall routines often fail to completely remove all signs from the registry, and the residue can create problems. The mod [http://www.nexusmods.com/newvegas/mods/35868/? DirectShow Filter _Codec_ Reset] by '''Blade FireLight''' is designed to "reset" the chain of "codecs" to the defaults used by Windows 7. However, it may not work with later versions of Windows. [http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/ HEED THE WARNING ABOUT CREATING A 'SYSTEM RESTORE POINT' FIRST!] Anything affecting the registry has the potential to turn your computer into "a brick", unable to do anything but sit there. A power outage can happen to anyone at any time. 
 +
::
 +
::*Do not, I repeat, DO NOT follow the advice you can find on the internet about installing AC3 encoder and configuring it… two of us in the forum lost *all* sounds because of that.   
 +
 
 +
:
 +
:*Solution-2b: You might be able to resolve the problem with another tool designed to "reset" your codecs back to Windows defaults. There are a number of free tools avaialbe to deal with this listed on [http://www.raymond.cc/blog/fix-video-playback-problems-by-removing-bad-codecs/ this web page] 
 +
 
 +
*Cause-3: If your problem occurs after you attempted to uninstall something and no solution you've tried has worked, you may need more drastic measures.
 +
 
 +
:
 +
:*Solution-3: Either return to a [http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/ Windows system restore point] prior to your installation of the problematic software, or use MS's own [http://www.microsoft.com/en-us/download/details.aspx?id=49975 Use Reset to restore your Windows 10 PC]. 
 +
 
 +
<span id="Issue: SOUND - Radio station music doesn't play"></span>
 +
=== Issue - SOUND - Radio station music does not play ===
 +
 
 +
Everything (ambient sound, footsteps, dialogue, radio announcer) is working fine except the radio music is missing.<br/> (See instead [[#Issue:_No_music_or_sound|Issue: SOUND - No music or sound]] for the more general problem.)
 +
 
 +
*Cause-1: There is an audio "codec" conflict between what you have installed under Windows and what the music in question requires, or a necessary "codec" is missing. (A "codec" is a "DirectShow filter", and there is a chain of them in the registry establishing which order to try them in to determine which to use. "DirectShow" is a component of the DirectX (DX#) API system used by games running under Windows.)
 +
 
 +
:
 +
:*Solution-1a: Win10 has DirectX12 drivers, but the DX9 driver the game is expecting is not being found. See "Cause-1" under [[#Issue:_Vanilla_game_Hangs_on_startup|Issue: Vanilla game Hangs on startup]]. 
 +
 
 +
:
 +
:*Solution-1b: Some have found that installing a third-party "DirectX: DirectShow" "codec" resolves the problem. There are a number available on the internet. The [http://www.codecguide.com/ K-Lite Codec Pack] is often mentioned especially for older versions of Windows. Be sure to get the 32-bit version, as FNV is using 32-bit libraries. 
 +
 
 +
:
 +
:*Solution-1c: Not all "codecs" are created equal, and sometimes Windows versions and specific games are very particular. Codec uninstall routines often fail to completely remove all signs from the registry, and the residue can create problems. The mod [http://www.nexusmods.com/newvegas/mods/35868/? DirectShow Filter _Codec_ Reset] by '''Blade FireLight''' is designed to "reset" the chain of "codecs" to the defaults used by Windows 7. [http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/ HEED THE WARNING ABOUT CREATING A 'SYSTEM RESTORE POINT' FIRST!] Anything affecting the registry has the potential to turn your computer into "a brick", unable to do anything but sit there. A power outage can happen to anyone at any time. 
 +
::
 +
::*Do not, I repeat, DO NOT follow the advice you can find on the internet about installing AC3 encoder and configuring it… two of us in the forum lost *all* sounds because of that.   
 +
 
 +
:
 +
:*Solution-1d: Sometimes the music is there, but the volume (even with the settings to max) is so low you can barely tell it's there. This is likely a "codec" problem. See the earlier possible "codec" solutions. 
 +
::
 +
::*Alternatively, [http://www.youtube.com/watch?v=vpQShdafsFA Tutorial - Fallout New Vegas Radio Fix] video by '''KitsuneJimmy''' explains that in the game "Data\Sound\songs\radionv" folder, the MP3 files are recorded at 72 decibels, while normally commercial music is recorded at 89 decibels. The tool [http://mp3gain.sourceforge.net/ MP3Gain] analyzes and adjusts MP3 files so that they have the same target volume (89 decibels). It can process the entire folder at once; but it's always a good idea to back it up first in case of problems. The first time you load the game after doing so, it may take longer than usual to get to the main menu.   
 +
 
 +
:
 +
:*Solution-1e: The game doesn't like USB speakers/headsets and non-stereo setups. It is always worth a try to set your audio setup to 2.0 stereo in the Windows Control Panel. 
 +
 
 +
:
 +
:*Solution-1f: Sometimes there is a technical difference between the jacks on the front and back panels of the computer chassis. Be sure to test using both sets. 
 +
 
 +
:
 +
:*Solution-1g: Possibly your issue is speaker related. For example with 7.1 sound speakers: after testing them in control panel, found 2 of them werent working so set it to 5.1. Then they worked. 
 +
 
 +
:
 +
:*Solution-1h: A known problem with the audio in this game is if you have that Razer driver installed that lets you hear surround sound on the headphones. Since it is an incompatibility issue, you cannot use both: either remove the Razer drivers entirely and use the headphone as stereo 2.0, or get another speaker/headphone that plugs into the standard audio-out jack. 
 +
 
 +
:
 +
:*Solution-1i: Windows Control Panel "Realtek HD Audio Manager" control was set for 5.1 sound properly, except that there was a "speaker fill" setting that was unchecked and this little setting apparently turns the stereo-only signal into a 5.1 surround signal. 
 +
 
 +
:
 +
:*Solution-1j: The last resort is trying to reinstall the drivers of your sound card. Either the latest one or the one that it came with on cd or from the manufacturer's site. This will put the default codec up top in the Windows preferred codecs list. 
 +
::Locate the sound card or integrated audio device driver for your version of Windows on the vendor site and re-install. (These are often different from those available from "Microsoft Updates".) [http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/ Create a Windows System Restore Point] first! 
 +
 
 +
*Cause-2: By default the game only plays radio music while the Mojave Wasteland is enabled/loaded. When you load a DLC worldspace, the Mojave worldspace (and thus the music) is disabled. Sometimes it is not re-enabled upon returning to the Wasteland. This is usually confined to the save game made at that time, but it might be an unknown vanilla game bug or a mod conflict in your particular "load order", and can be carried forward thereafter. People have performed a "speed-run" through the same DLC from a save game made prior to entering it the first time and not had the problem occur upon exit. Others have had it happen only on subsequent runs through the DLC. It's a fairly rare problem.
 +
 
 +
:
 +
:*Solution-2a: You can use nearly any script command in the console. The difference is mainly that you'll need to use the numerical '''Reference-ID''' (next to the text '''Editor-ID''' or '''Base-ID''' in wiki tables). On that note, you can use these commands in-game on any reference if you have the correct ID it is expecting. 
 +
::(Here's a good comprehensive reference for console commands: [http://fallout.gamepedia.com/Gamebryo_and_Creation_console_commands_(all) Gamebryo and Creation console commands (all)]. Even though a command is listed, that doesn't guarantee full functionality. Best thing to do is to test it.)
 +
::Fortunately, for every actor or object in the vanilla game, including the DLCs, these numbers are available on all the Fallout wiki sites, like Wikia's Nukapedia or Gamepedia's The Vault for example. But, unfortunately, NOT for the Radio Stations, which use Talking Activators (form type "TACT"). You will need to know their "common name", which you can look up by their "Editor-ID" in [http://www.nexusmods.com/newvegas/mods/34703/? FNVedit] under "Name" field. Then in the game console, enter the command: 
 +
<div class="boilerplate metadata" id="Warning_Notice" style="margin:0px 10px 10px 50px;  border:1px dashed #DAA520;  color: lightgray;  background-color:#424242;  padding:3px;  white-space: pre-wrap;  white-space: -moz-pre-wrap;  white-space: -pre-wrap;  white-space: -o-pre-wrap;  word-wrap: break-word">save <SomeFileName> 1</div>
 +
:
 +
::This will create a text "dump file" '''<SomeFileName>.fos.txt''' in your "My Games\FalloutNV\Saves" folder. This file is a list of various information (including Ref-IDs) currently in your loaded save game. (It's not documented what other parameters than "1" will produce.) Now search that file for the "common name" of the radio station you want. (Check the type of entry. You don't want quest or script references.) The first column entry is the "Ref-ID" of that station. Make a note of it.
 +
::The Common Name "Mojave Music Radio" has Editor-ID "vCountryRadio" and a Base-ID of 0016B46F, but does not have a location marker as it is enabled by script automatically when you leave Doc Mitchell's house at the beginning of the game. At least in my "dumpfile" it did not appear as a Ref-ID. 
 +
<div class="boilerplate metadata" id="Warning_Notice" style="margin:0px 10px 10px 50px;  border:1px dashed #DAA520;  color: lightgray;  background-color:#424242;  padding:3px;  white-space: pre-wrap;  white-space: -moz-pre-wrap;  white-space: -pre-wrap;  white-space: -o-pre-wrap;  word-wrap: break-word">Editor-ID (Ref-ID):
 +
Radio New Vegas (0014DF03) Black Mountain Radio (000E6188) Sierra Madre Broadcast (010062B4) Happy Trails Expedition Broadcast (0200E74A)
 +
</div>
 +
:
 +
::There's the command [http://geckwiki.com/index.php/GetBroadcastState GetBroadcastState] to make sure that it's not broadcasting. And then there's [http://geckwiki.com/index.php/GetDisabled GetDisabled] to confirm it's not a disabled reference. Then you can try [http://geckwiki.com/index.php/SetBroadcastState SetBroadcastState] from the console; as well as disabling and then enabling the radios' Talking Activator references. You can try [http://geckwiki.com/index.php/MoveTo Player.MoveTo <stationRef>] to have a look at the "station" as well but many are buried inside terrain features such as mountains.
 +
::Examples: 
 +
<div class="boilerplate metadata" id="Warning_Notice" style="margin:0px 10px 10px 50px;  border:1px dashed #DAA520;  color: lightgray;  background-color:#424242;  padding:3px;  white-space: pre-wrap;  white-space: -moz-pre-wrap;  white-space: -pre-wrap;  white-space: -o-pre-wrap;  word-wrap: break-word">prid 0014DF03 &nbsp;; sets the following command to apply to the Ref-ID of 'Radio New Vegas'.
 +
GetBroadcastState &nbsp;; returns "0" if OFF (static); "1" if broadcasting OR "0014DF03".GetDisabled&nbsp;; returns "1" if disabled; otherwise "0" for Ref-ID of 'Radio New Vegas' "0014DF03".SetBroadcastState 1&nbsp;; "0" turns OFF; "1" turns ON continuous broadcast.
 +
</div>
 +
:
 +
::Note that range considerations still apply. You won't pick up '''Black Mountain Radio''' if you aren't near it.
 +
::The above are probably all you will need. But for completeness sake, here is the information on the '''JIP LN NVSE Plugin''' ''music'' functions: (parameter in brackets is [optional]). 
 +
 
 +
:
 +
::Note the "ambient or atmospheric music" is dependent upon the current cell and is separate and distinct from the radio "songs". They are controlled independently. These are '''JIP NVSE''' addon functions. As such they require '''JIP LN NVSE''' to be installed, and are intended to be used in scripts. Their use as console commands has not been verified. 
 +
 
 +
:
 +
::"(musicState:int) IsMusicPlaying [musicType:form]". Returns the playback state of the game's current background (ambience) music:
 +
::*0 Not playing
 +
::*1 Paused
 +
::*2 Playing 
 +
::The ''musicType'' argument may be either a Music Type form, a Media Location Controller form, or it may be entirely omitted. Omitted paraemter returns currently playing music (if any).
 +
::Examples: 
 +
<div class="boilerplate metadata" id="Warning_Notice" style="margin:0px 10px 10px 50px;  border:1px dashed #DAA520;  color: lightgray;  background-color:#424242;  padding:3px;  white-space: pre-wrap;  white-space: -moz-pre-wrap;  white-space: -pre-wrap;  white-space: -o-pre-wrap;  word-wrap: break-word">set iMusicState to IsMusicPlaying
 +
printc "Current Music state is&nbsp;%g" iMusicState
 +
</div>
 +
:
 +
::"SetMusicState musicState:int{0, 1, 2}". Sets the playback state of the game's current background music:
 +
::*0 Stop Playback
 +
::*1 Pause Playback
 +
::*2 Resume Playback 
 +
::Note: The Stop Playback state will stop music played by [http://geckwiki.com/index.php/PlayMusic PlayMusic], otherwise it will replay the current music from the beginning. 
 +
 
 +
:
 +
::Example:
 +
::*"SetMusicState 2"&nbsp;; (resume Playback.)   
 +
 
 +
&nbsp;
 +
 
 +
:
 +
:*Solution-2b: Failing the use of Ref-IDs and console commands, there is a mod [http://www.nexusmods.com/newvegas/mods/62555 Radio New Vegas Everywhere] uploaded on the Nexus that keeps Radio New Vegas enabled always (as long as the Player is enabled), so you can try downloading that. The mod [http://www.nexusmods.com/newvegas/mods/62551/? Music Pack for Radio NV - ver 1.3] by the same author adds 250 tracks (nearly every song in the game) to RNV. 
 +
 
 +
:
 +
:*Solution-2c: [http://geckwiki.com/index.php/FadeSFX FadeSFX] disabled all the sounds except the music. This is useful when showing Bink Video files. FadeSFX is reversable, it appears, by simply [http://geckwiki.com/index.php/PlayBink playing a Bink video file]. As soon as the video ends, sound is restored. As far as can be told, it is still irreversible without playing a video. 
 +
::The Bink video has to be on disk and not in a BSA. The only one on disk by default is "Data\Video\FNVIntro.bik". So try the console command: 'playbink "FNVIntro.bik" 1 1 1 1'. (The double-quotes around the ".bik" filename are required.) You can use the <ESC> key to interrupt the video, which should restore your music if "FadeSFX" was what disabled it. 
 +
 
 +
<span id="Issue: System Network configuration"></span>
 +
 
 +
=== Issue - System Network configuration ===
 +
 
 +
Unless you are running a LAN, there are some default configuration settings you can change to improve your Internet download performance and reduce system memory use. It may also reduce incidents of CTDs.
 +
 
 +
*Cause: Anything that searches for system updates, or all the computers in a home or business network; or tries to determine the Internet Bandwidth while online: all use RAM to run as "services" in the background. When you are running your game in "Offline" mode, you don't need any of those functions running at all. Most of the time you only need them when the computer boots up and not again until something changes.
 +
 
 +
:
 +
:*Solution: Read the following carefully. Not all will apply to your situation. Be prepared to revert to a known good configuration. YOU have to know what that configuration is. The system does not maintain "save files" for device configurations. 
 +
::
 +
::*Open the "Network and Sharing Center/Internet" Control Panel applet.
 +
::*"< Left-Click >" on the "Change adapter settings" option in the left hand edge.
 +
::*"< Right-click >" on the "Ethernet" adapter icon, and select "Properties". (This will require you to enter an "Administrator" password to proceed.)
 +
::*You should see a "Networking" tab which lists various "protocols" in the large white box under the identification of your network adapter model. Those with a "Check" in the box are "enabled". Any that are listed are "installed". 
 +
:::
 +
:::*"[http://support.microsoft.com/en-us/help/322267/removing-client-for-microsoft-networks-removes-other-services Client for Microsoft Networks]". This protocol is intended for a "home" or "small business" Local Area Network (LAN) that cannot be seen across the Internet. It is actually the '''Workstation''' service. If you remove this service, the '''Netlogon''' and '''RPC Locator''' services are also removed. Unless you have such a setup, it is not of use to you, so disable it by unchecking the box.     
 +
<div class="boilerplate metadata" id="Notice_Box" style="margin:0px 10px 10px 90px;  border:1px dashed #DAA520;  color: red;  background-color:#ffffffff;  padding:3px;  word-wrap: break-word">Note that if you have your own router (or WiFi connection) between your computer and your ISP modem, you have a "home LAN". Disabling this protocol could cause you to lose your Internet connection immediately. Test!</div>
 +
:
 +
::
 +
:::
 +
:::*"[http://blogs.technet.microsoft.com/windows_vpc/2009/12/06/networking-in-windows-virtual-pc/ Virtual PC Network Filter Driver]" is only of use if you run a "Virtual PC with networking". The "Virtual PC" is not available at all on the "Home Edition" of any Windows verson. Unless you have a need, disable it.
 +
:::*"[http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/qos-packet-scheduler-bug/5793456c-a5be-48de-abd8-839d9fcbf452 QoS Packet Scheduler]" is installed by default for Local Area Networks (LAN). It's purpose is to prioritize particular types of application traffic (e.g. "Voice over Internet Protocol" ('''VoIP''')) where having a certain amount of bandwidth is crucial. If you do not need to prioritize network traffic and its works fine without '''QoS packet scheduler''' you may choose to keep it disabled. Testing to see it's effects is recommended.
 +
:::*"[http://support.microsoft.com/en-us/help/199346/disable-file-and-printer-sharing-for-additional-security File and Printer Sharing for Microsoft Networks]" works in conjunction with the "Client for Microsoft Networks" protocol. Again it is of use only with a "home" or "business" LAN and it does require the "Client for Microsoft Networks" protocol to be installed and active. Even then, it can be disabled if you don't need to directly access files and printers between different devices in the network. Microsoft advises unbinding it from the '''TCP/IP''' protocols if possible and binding it only to a LAN protocol such as "Client for Microsoft Networks" for security reasons. See the linked article.
 +
:::*"[http://en.wikipedia.org/wiki/Link_Layer_Topology_Discovery Link-Layer Topology Discovery]" has two protocols: 
 +
::::
 +
::::*"Mapper I/O Driver"
 +
::::*"Responder". 
 +
::::"Link-Layer Topology Discovery" is used by Microsoft's "Network Map" feature to display a graphical representation of the local area network (LAN) or wireless LAN (WLAN), to which the computer is connected. It operates strictly on a given local network segment. It cannot discover devices across routers, an operation which would require Internet Protocol level routing. Unless your LAN needs it, disable both protocols.     
 +
 
 +
<span id="Issue: TTW Performance Guide abstract"></span>
 +
=== Issue - TTW Performance Guide abstract ===
 +
 
 +
From the [http://taleoftwowastelands.com/viewtopic.php?t=6050 TTW Performance guide] thread, and updated from '''GamerPoets'''' latest revised [http://www.youtube.com/watch?v=sJOrDhghr60 Fallout New Vegas | FPS & Stability (definitive guide)] YouTube video.
 +
 
 +
<span style="margin:0px 10px 10px 10px;  border:1px solid #00C600;  color: green;  background-color:#fff5f5;  padding:3px;  word-wrap: break-word">Note: [http://taleoftwowastelands.com/viewtopic.php?f=48&p=59475#p59475 Tale of Two Wastelands (TTW)] rewrite/update from v2.9.4b to v3.2 has been released as of 10 Nov 2018. It is only available on the TTW site.</span>
 +
 
 +
For those not familiar with TTW, it is a conversion of FO3 (purchased separately) to run on the FNV game engine. You can effectively and seamlessly play the FO3 (East Coast campaign) storyline through into the FNV (Mojave Desert campaign) with the same character. [http://www.nexusmods.com/newvegas/mods/45138 Fallout New California (FNC)] conceptually is a separate campaign (located in California) that occurs before both of FO3 and FNV, with a different character generation and requires a "new game" start, but is intended to eventually (currently in Beta test) allow you to continue as the "Courier" (or not) into the Mojave. TTW is not officially supported by FNC, but some have reported that they do work together. (Check the [http://docs.google.com/document/d/1Iciq_jIMJvZLMjkDQdCP0tDHmezpFme9nUKjDiZ1HGU/mobilebasic FNC Recommended Mods List] AND the [http://docs.google.com/document/d/14OpRnF5zW4x-qZMQ62JZgM5A4Xq02TAsDoKwKd41P_s/mobilebasic FNC Incompatibilities List] for the latest information.)
 +
 
 +
As a result, the "Performance Guide" for TTW is applicable for FNV (and probably FNC) players as well.
 +
 
 +
Required:
 +
 
 +
*[http://nvse.silverlock.org/ New Vegas Script Extender (NVSE)] v5.1b4+.
 +
*[http://www.nexusmods.com/newvegas/mods/53635 New Vegas Anti Crash (NVAC)].
 +
*[http://www.nexusmods.com/newvegas/mods/62552 FNV 4GB Patcher] The newest 4GB patcher by '''RoyBatty''' and '''LuthienAnarion'''.
 +
 
 +
Recommended:
 +
 
 +
*[http://www.guru3d.com/files-details/nvidia-inspector-download.html Nvidia Profile Inspector] highly recommended for Nvidia users, but aging.
 +
*[http://wiki.step-project.com/Guide:AMD_Catalyst_Control_Center S.T.E.P. AMD Catalyst Control Center Guide] For ATI users: you need to create a new profile in CCC.
 +
*[https://taleoftwowastelands.com/download/file.php?id=2998 NVSR INI for Newer Processors] Last updated 15 Dec 2017. Login to the TTW site is required for access.
 +
*[https://taleoftwowastelands.com/download/file.php?id=2997 NVSR INI for Older Processors] Last updated 15 Dec 2017. Login to the TTW site is required for access.
 +
 
 +
Details:<br/> 1.) Video Driver Profiles. Note this step has been moved in the '''GamerPoets'''' video to be part of the '''ENBoost''' section, but no longer mentions "Nvidia Profile Inspector" or AMD's "Radeon Control Panel". It only refers to the "Nvidia Control Panel" (and by implication the "AMD Catalyst Control Center") which are part of the respective driver installation. "Inspector" instructions are included here from the thread for completeness for those looking into the original recommendations, but the recommendation applies regardless of the tool used.
 +
 
 +
*Search for "Fallout New Vegas" within the "Nvidia Profile Inspector". You have to add the game EXEs to the profile, then hit <apply> and exit "Inspector", and you never have to do it again until you update your drivers.
 +
 
 +
:
 +
:*Set "Multi-display/mixed-GPU acceleration" to "Single display performance mode".
 +
:*Finally set "Power Management Mode" to "Prefer maximum performance". 
 +
::Here's a [http://i.imgur.com/6nYPWVX.png visual example]. 
 +
 
 +
2.) Fallout "User" INI files. Search through '''Fallout.ini''' and '''FalloutPrefs.ini''' within your "Users\Documents" game folder.
 +
 
 +
:
 +
:*Under "[General]": 
 +
::
 +
::*"bUseThreadedAI=0" to "1".
 +
::*insert "iNumHWThreads=2" below "bUseThreadedAI=1".   
 +
 
 +
3.) Fallout_Default INI file. Search through '''Fallout_default.ini''' within your "Steamapps\common\Fallout New Vegas" folder. (This so if your "Users" folder INI files get reuilt for any reason they will include these tweaks.)
 +
 
 +
:
 +
:*Under "[General]": 
 +
::
 +
::*"bUseThreadedAI=0" to "1".
 +
::*insert "iNumHWThreads=2" below "bUseThreadedAI=1".   
 +
:*Make a backup of this file, as it will be replaced if you ever use Steam's "verify local files" option. 
 +
::Note: "FalloutCustom.INI" is used by "JIP LN NVSE" plugin to override settings in '''default''' game INI files only. 
 +
:Here's a [http://i.imgur.com/7rc6Gkq.png visual example].
 +
 
 +
4.) Cellpurging. If using '''Zan's AutoPurge Crash Protector''' mod, uninstall it and use the following superior INI setting changes in all three of the INI files from above:
 +
 
 +
:
 +
:*Under "[General]": 
 +
::
 +
::*"bPreemptivelyUnloadCells=0" to "1".   
 +
:*Under "[BackgroundLoad]": 
 +
::
 +
::*"bSelectivePurgeUnusedOnFastTravel=0" to "1".   
 +
 
 +
5.) Audio. These may help with "audio stuttering" problems. However, some people have found these adjustments to cause some Win10 NVSR configurations to CTD. Test.
 +
 
 +
:
 +
:*Under "[Audio]" 
 +
::
 +
::*"iAudioCacheSize=2048" to "8192".
 +
::*"iMaxSizeForCachedSound=256" to "1024".   
 +
 
 +
6.) NVSE. Open the game "Data" folder, and search for the "NVSE" sub-folder. (This assumes you have installed NVSE.)
  
=== Issue: Unable to draw weapons, fire, or crouch ===
+
:
Also related: Sunny Smile's initial greeting dialog is actually that from a later stage:
+
:*Once there, create a text file and name it "nvse_config.ini." Make sure to create it inside the "NVSE" folder, not the nested "plugins" sub-folder.
: Initial greeting: "Cheyenne, stay. Don't worry, she won't bite, unless I tell her to."
+
:*Add the following lines: 
: Later greeting: "Yeah alright. Let's just get done with this first and we'll talk later. Preferably somewhere I can get a stiff drink and Cheyenne can cool down".
+
<div class="boilerplate metadata" id="Notice_Box" style="margin:0px 10px 10px 50px;  border:1px dashed #DAA520;  color: lightgray;  background-color:#333333;  padding:3px;  word-wrap: break-word">[Memory]
* Cause: Removal of all "tumbleweeds" from the game.  The first "tumbleweed" seen upon exiting Doc Mitchell's house after creating a character is scripted.  It's absence (i.e. a mod to remove all tumbleweeds also removes that script event) breaks the game.
+
DefaultHeapInitialAllocMB=400
 +
</div>
 +
:Here's a [http://i.imgur.com/C1DLMyz.png visual example].
 +
 
 +
7.) NVSR. Stop by the [http://www.nexusmods.com/newvegas/mods/34832/? New Vegas Stutter Remover] Nexus page, and download file "NVSR_4-1-32" (under "Old Files") if you're processor predates i5 or i7. For newer processors, download "NVSR_4-1-36" or later.
 +
 
 +
:
 +
:*Edit the "Data\NVSE\plugins\sr_New_Vegas_Stutter_Removers.ini" file as follows: 
 +
::
 +
::*Under the "Master = {" section, set all settingsto "= 0" except: 
 +
:::
 +
:::*"bReplaceGetTickCount = 1"
 +
:::*"bFastExit = 1"   
 +
::*This is as far as the '''GamerPoets'''' [http://www.youtube.com/watch?v=sJOrDhghr60 Fallout New Vegas | FPS & Stability (definitive guide)] YouTube video takes things. Various security updates have complicated the NVSR configuration situation immensely. Things are still being discovered. The following were previous recommendations which still tend to work for versions of Windows prior to Win10.   
 +
 
 +
:
 +
::
 +
:::
 +
:::*Setting "bHookCriticalSections = 1" is generally recommended, but can be problematic for many Win10 users depending upon the level of updates installed. See the [[#Issue:_CTD_after_10-20_minutes_of_play_.28post-Win10_2017_FCU.29|Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)]] entry and the [http://www.nexusmods.com/newvegas/mods/34832 Nexus NVSR download] comments page for various options. Expect to need "trial and error" testing.
 +
:::*Note: If you do not use any texture mods you may enable ''bReplaceHeap = 1''. In that event, Set the "Heap = {" section" settings "iHeapSize = 384" and use "iHeapAlgorithm = 6".     
 +
:*When allowing NVSR to manage your FPS: "bManageFPS = 1" and settings under the "FPS_Management = {" section; "Vsync" provided by the game's engine or other sources must be shut off to avoid conflict between them. 
 +
 
 +
8.) V3.0 Shaders.<br/> <span style="margin:0px 10px 10px 10px;  border:1px solid #cc3333;  color: red;  background-color:#fff5f5;  padding:3px">WARNING: If you intend to use ENB's graphics post processing, it only works with v2.0 Shaders. DO NOT perform this step, nor enable the Fallout INI's "[Display]" setting "bAllow30Shaders=1". Leave it at "=0".</span>
 +
 
 +
:Edit both the "Users" folder '''Fallout INI''''s "[Display]" setting "bAllow30Shaders=0" to "1". This will ALLOW (not force) the use of v3.0 Shaders.
 +
:Open the "Renderinfo.txt" within your documents; "Documents\My Games\FalloutNV". There will be a line for the "Shader Package&nbsp;: ##" (where "##" is "13" in the following example). This is the number suffix of the filename of the shader package expected to have a v3.0 Shader supported by your video card.&nbsp; If not present, your card was not detected by DirectX as able to support v3.0 Shaders.
 +
:*Now, go to the Shaders folder within your game "Data" folder, and rename '''shaderpackage013.sdp''' to '''shaderpackage013.sdp_backup'''. Once done, make a copy of '''shaderpackage019.sdp''' (which is always the provided v3.0 Shader package), and rename it to '''shaderpackage013.sdp''' so it will get utilized. Ignore the periods ending my sentences of course.
 +
:*Do note, 13 is solely an example; the shader package "19" should be renamed to depends on the number your "Renderinfo.txt" displays. 
 +
 
 +
9.) VORBIS Libraries. Download [http://www.nexusmods.com/newvegas/mods/61265/? Ogg Vorbis Libraries] to improve audio performance. The mod [http://www.nexusmods.com/newvegas/mods/65854 FNV BSA Decompressor] will automatically install these libraries if their archives are found in the game root folder. '''TTW''' will include the '''Decompressor''' as part of it's installer.
 +
 
 +
10.) ENBoost. At this time the latest version is v0.322, which has been updated without changing the version number ... so be sure to download again. You should be able to use the "WrapperVersion". See this post about '''ENBoost''' from '''MajinCry''' [http://taleoftwowastelands.com/viewtopic.php?p=55126#p55126 Configuring ENB Fallout New Vegas]. The basic points (and quotations) are:
 +
 
 +
:
 +
:*Play the game in "Windowed" mode if you don't want to crash upon "alt-tabbing" with '''EnableUnsafeMemoryHacks=true''' (below). "That setting is a game changer, as it greatly reduces stuttering if not completely eliminating it, when models and textures are being loaded (e.g, traveling across cells, transitioning from interior <-> exterior). So have New Vegas in windowed mode, and everyone's happy. Also, when a game is in windowed mode (Windows 7 and newer), the game gets triple buffering. This means you can have VSync enabled without the framerate juddering between 15 <-> 30 <-> 60fps."
 +
:*Disable the Steam Overlay (actually any game overlays; this is not multi-player). "It causes issues when the interface pops up (e.g, recieving a message from another player) where many objects become fully transparent, and has caused issues for some users when '''ExpandSystemMemoryX64=true'''."
 +
:*in the '''''video card driver''''' configuration, set: 
 +
::
 +
::*Anisotropic Filtering = "Use Application Settings"
 +
::*Anti-Aliasing Mode = "Use Application Settings"   
 +
 
 +
:
 +
:*in the '''enblocal.ini''' file, set:
 +
:*[GOBAL] 
 +
::
 +
::*UseENBoostWithoutGraphics=true
 +
::*UsePatchSpeedhackWithoutGraphics=true (set "false" if using ENB Graphics as well)   
 +
:*If you want to use ENB's graphics modifications alongside the ENBoost part, set: 
 +
::
 +
::*UseENBoostWithoutGraphics=false
 +
::*UsePatchSpeedhackWithoutGraphics=false   
 +
 
 +
&nbsp;
 +
 
 +
:
 +
:*[MEMORY] 
 +
::
 +
::*ExpandSystemMemoryX64=true
 +
::*ReduceSystemMemoryUsage=false
 +
::*DisableDriverMemoryManager=false
 +
::*DisablePreloadToVRAM=false
 +
::*EnableUnsafeMemoryHacks=true (loads all images into VRAM, reducing "hitches" while loading cells)
 +
::*ReservedMemorySizeMb=512 (test by lowering in increments of 128)
 +
::*VideoMemorySizeMb=<value from ENB's "VRAMsizetest" tool> for a single GPU. (Win 8 users are limited to 4096 due to a bug in the DirectX driver.) 
 +
::Notes:  
 +
::*ReduceSystemMemoryUsage=true (for those hitting an out of memory issue (not necessarily GPU VRAM, but application virtual ram); noticable FPS increase; fires off multiple copies of '''enbhost.exe''' as needed, reducing "virtual game memoryy").  
 +
::*'''MajinCry''' found: "When '''EnableUnsafeMemoryHacks=true''', ENB will automatically disable '''ReduceSystemMemoryUsage'''." So, we might set '''ReduceSystemMemoryUsage''' to "true" and not worry about it whenever we change '''EnableUnsafeMemoryHacks=false'''.  
 +
::*[ENGINE] 
 +
:::
 +
:::*ForceAnisotropicFiltering=false (uses the game settings instead)     
 +
<div class="boilerplate metadata" id="Warning_Notice" style="margin:0px 10px 10px 50px;  border:1px solid #cc3333;  color: green;  background-color:#fff5f5;  padding:3px;  white-space: pre-wrap;  white-space: -moz-pre-wrap;  white-space: -pre-wrap;  white-space: -o-pre-wrap;  word-wrap: break-word">'''MajinCry''' comments (typo's corrected): '''EnableUnsafeMemoryHacks=true''' brings two major benefits. And these are brought about as the game's models and textures are no longer mirrored into RAM (as is standard with Direct3D 9). Stuttering is exceptionally reduced, as is memory usage in the '''FalloutNV.exe''' process.
 +
If you have texture mods installed, with the amount of memory being used exceeding your GPU's VRAM, Set '''EnableUnsafeMemoryHacks=false''', '''ReduceSystemMemoryUsage=true''', '''AutodetectVideoMemorySize=true'''. We lose the benefit of reduced stuttering brought by '''EnableUnsafeMemoryHacks''', but gain the benefit of the game no longer crashing or corrupting when the VRAM is not able to hold all of the game's models, textures, shaders, render targets, and frame buffers. This is done by ENB launching multiple '''ENBHost.exe''' processes, that are then filled with the game's models and textures.
 +
 
 +
If you have a card with a large amount of memory (e.g. 8GB+), it's pretty much impossible for you to reach the limits of your VRAM, so you can just keep '''EnableUnsafeMemoryHacks=true''' and have the best of both worlds.
 +
</div>
 +
*Example '''enblocal.ini''' files for:
 +
 
 +
:
 +
:*[https://pastebin.com/vhpRAFS0 best performance] (no texture replacers, 2GB VRAM).
 +
:*[https://pastebin.com/ix9G7wfg game with texture mods & small GPU VRAM] (size of all loaded resources > GPU VRAM size). 
 +
 
 +
<span id="Issue: Vsync (V-Sync) ON or OFF"></span>
 +
=== Issue - Vsync ''aka V-Sync'' ON or OFF ===
 +
 
 +
"Short for Vertical Sync, Vsync is a display option found in some 3-D computer games that allow the gamer to synchronize the frame rate of the game with the monitor refresh rate for better stability. If the Vsync is turned off, gamers might obtain a higher frame rate but this action may introduce artifacts in the game." - Webopedia. Vsync can also have an effect on "lag". The purpose of Vsync is to eliminate "tearing", a disjointed image. For an in-depth explanation of how VSync (aka "V-Sync") affects "tearing", see the [http://hardforum.com/threads/how-vsync-works-and-why-people-loathe-it.928593/ How VSync works, and why people loathe it] article on the "HardForum.com" site.
 +
 
 +
*Cause: The short answer is: if you have "triple-buffering" on your video card, then use VSync, because "3buff" is designed to solve the problems with Vsync. If you don't have triple-buffering, then you have to make a choice based upon the effect on your game and FPS rate. Read the article!
 +
 
 +
:
 +
:*Solution-1a: Some games (including FNV) have a setting for disabling VSync. Most modern video cards have an option for it in their driver control programs. Some "post-processors" (such as ENB) have an option as well. You need to check them all. 
 +
 
 +
:
 +
:*Solution-1b: FNV's hardware configuation option doesn't seem to actually have any effect. You can try manually setting this "off" in all three of the "Fallout.INI" files by changing the "iPresentInterval=1" variable to "iPresentInterval=0". Be sure you have a backup of the original INI files before making any changes. (See the [[FNV_General_Mod_Use_Advice#Game_INI_files|Game INI files]] section of the "FNV General Mod Use Advice" article for details if you don't know about the locations of the INI files.) 
 +
 
 +
<span id="Issue: What INI edits seem to be most beneficial to performance"></span>
 +
=== Issue - What INI edits seem to be most beneficial to performance ===
 +
 
 +
*Cause: There are many INI settings you can adjust across many utilities, but it can be difficult to tell which are most helpful to improving performance in general.
 +
 
 +
:Solution: The information provided in the [http://taleoftwowastelands.com/viewtopic.php?p=55250#p55250 Tale of Two Wastelands (TTW) Performance Guide] covers specific INI settings for a number of different utilities such as the three game INI files, NVSE, the correct version of NVSR to use depending upon your processor, and some nVidia card specific tweaks. These setting seem to be equally helpful for both FNV and FO3 as well as TTW. See also the [[#Issue:_TTW_Performance_Guide_abstract|Issue: TTW Performance Guide abstract]] entry.
 +
 
 +
== Solutions to Crash To Desktop ''aka CTD'' problems ==
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 10px;border:1px dashed #DAA520;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog because the game engine was not able to predictably handle the errorPlease see the "Windows Error Messages" section of the wiki "[http://wiki.nexusmods.com/index.php/How_to_read_most_Bethesda_game_error_logs How to read most Bethesda game error logs]" article.
 +
 
 +
Logs generated by the game itself (not Windows) are found in the game folder, where the "FalloutNV.EXE" file is located.
 +
 
 +
Checking such logs should always be your first step, as separating "Windows System" from "Game" generated errors will save you from fruitlessly spending lots of time looking in the wrong direction for the cause.
 +
</div>
 +
 
 +
<span id="Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)"></span>
 +
=== Issue - CTD after 10-20 minutes of play ''post-Win10 2017 FCU'' ===
 +
<span id="Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play">(Formerly: Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play)</span><br>
 +
<span style="color: green;background-color:#fff5f5;">Update: The mod [http://www.nexusmods.com/newvegas/mods/66537 NVTF - New Vegas Tick Fix] is a lighter, fully Windows 10 compatible, completely rewritten version of the 64hz micro-stutter bug script fix from NVSR, including '''Fast Exit''' and a '''high FPS fix''' for exceeding 60FPS.  NOTE: NVTF v3.0 is now NOT supported when used in conjunction with NVSR.
 +
</span>
 +
* There are several reports in the download page "comments" that NVSR causes CTDs after 10-20 minutes of play once the Win10 "Fall Creator's Update" (FCU) of Nov 2017 has been installed where previously everything had been stable.
 +
: Please read ''ALL'' the proposed solutions before implementing any.  Expect to need to engage in some "trial-and-error" testing.
 +
:* Solution-1: The mods [https://www.nexusmods.com/newvegas/mods/69779/? New Vegas Heap Replacer (NVHR)] combined with [http://www.nexusmods.com/newvegas/mods/66537 NVTF - New Vegas Tick Fix] should round out all the needed functionality of NVSR, enabling it's complete removal.  This is now the recommended solution for Windows 7 and 10 users.
 +
:* Solution-2: Those experiencing this problem who still want to continue using NVSR can try setting the NVSR INI file "Master" section to ''bHookCriticalSections= 0'', which will disable the use of "CriticalSections" features and the heap related algorithm and size settings in NVSR. (The ''bFastExit'' fix still reportedly works.)  Some have found it necessary to discontinue use of NVSR completely.  Others have found that they could implement partial solutions (detailed below as "other" solutions).  "Your mileage may vary."  Note that this may re-introduce some stuttering and depressed FPS if using large texture replacement images (e.g. greater than 2048x2048).
 +
 
 +
:* Solution-3: If "Solution-2" eliminates the CTD problem, or once you have installed the Win10 April 2018 SCU "1803/Redstone 4" system update, you may be interested in trying the configuration posted by user '''redmaxblower''' [http://forums.nexusmods.com/index.php?/topic/249379-new-vegas-stutter-remover/page-188#entry59460386 here] in the NVSR thread which restores much of NVSR's stutter reduction functionality.  It includes '''ENBLocal.ini''' settings for '''ENB Series''' users as well.
 +
 
 +
:* Solution-4: It has been found that you can set ''bHookCriticalSections= 1'', and then ''iDefaultMode = 1'' in the "CriticalSections" subsection of "sr_New_Vegas_Stutter_Remover.ini".  The "1" value just means NVSR uses the vanilla mechanism anyway.  Setting "iDefaultMode =" to anything other than "1" seems to cause the problem.  (It defaults to "3".)
 +
 
 +
:* Solution-5:  User '''Brad852''' (and others) has achieved a stable and stutter free game with the following tweaks to the NVSR v4-1-36 configuration:
 +
::* Make sure the settings under "Master = {" are:
 +
:::* bManageFPS = 1
 +
:::* bHookCriticalSections = 1
 +
:::* bHookLightCriticalSections = 0
 +
:::* bHookHashtables = 1
 +
:::* bReplaceHeap = 1
 +
:::* bReplaceGetTickCount = 1
 +
:::* bLogToConsole = 0
 +
:::* bFastExit = 1
 +
:::* bFlushLog = 1
 +
:::* iSchedulingResolution = 1
 +
:::* bReplaceRandom = 1
 +
:::* bExperimentalStuff = 0
 +
:::* iMainHookPoint = 1
 +
 
 +
::* Under "CriticalSections = {, set:
 +
:::* "iDefaultMode=3"
 +
:::* "bUseOverrides=1"
 +
 
 +
::* Under "OverrideList = {", third "Critical Section = {" ("CallerAddress = 0xA044FE") section:
 +
:::* delete "Spin = 6000"
 +
 
 +
::* This '''Brad852''' configuration seems to CTD for some users if the ''iAudioCacheSize'' or ''iMaxSizeForCachedSound'' values are altered in accordance with '''GamerPoets'''' latest revised [http://www.youtube.com/watch?v=sJOrDhghr60 Fallout New Vegas | FPS & Stability (definitive guide)] YouTube video (i.e. "[Audio]", "iAudioCacheSize=2048" to "8192"; "iMaxSizeForCachedSound=256" to "1024").
 +
 
 +
:* Solution-6: User '''AnonymousPlum''' has posted a promising [http://www.nexusmods.com/newvegas/mods/65606?tab=description Stabilised NVSR ini File for Windows 10] after a number of experiments which can be used as a starting point.  However, take the time to read the comments page as there are various reports of success, failure, and alternative settings from commenters (including user '''redmaxblower''', author of '''Solution-2''').  There is now a version of the file which disables the NVS[[R]] "heap replacement" in favor of the NVS[[E]] replacement technique (which was the most severe criticism).
 +
 
 +
:* Solution-7: '''Team Moki''' has posted a "mod" [http://www.nexusmods.com/newvegas/mods/66063 Ultimate Fallout New Vegas Stutter Removal for WIndows 10 and 7] consisting of a fully tweaked '''NVSR''' "\NVSE\Plugins\sr_New_Vegas_Stutter_Remover.ini" file.
 +
 
 +
:* Solution-8: See also the related [[#Issue: Incomplete save game load|Issue: Incomplete save game load]] which covers some background services that may need to be disabled.
  
* Solution:
+
<span id="Issue: CTD on interior/exterior/"fast travel" cell change"></span>
** Temporary: Move to somewhere you know you should be able to use all those functions, open the in-game console (<~> key), and enter "EnablePlayerControls" (without the quotes) and hit <Enter>.
 
** Permanent: Uninstall any mods that remove all tumbleweeds before creating a new character.  Often this functionality is incorporated into "performance" mods, so if it isn't mentioned in the description some testing may be required.  However, once the character has stepped outside of Doc Mitchell's so the scripted "tumbleweed" event occurs, they may be installed.
 
  
=== Issue: CTD on interior/exterior/"fast travel" cell change ===
+
=== Issue - CTD on interior or exterior or ''fast travel'' cell change ===
* Cause-1: Most crashes on cell-change are caused by the autosave feature choking because it's trying to write data into a save it corrupted the last time you changed cells.  Note this may mean your last several saves are corrupt.  Auto-saves are dangerous because they are seldom able to tell when the game is in the middle of doing something else critical.
+
* Cause-1: Most crashes on cell-change are caused by the autosave feature choking because it's trying to write data into a save it corrupted the last time you changed cells.  Note this may mean your last several saves are corrupt.  "Auto-saves" are dangerous because they are seldom able to tell when the game is in the middle of doing something else critical.
  
:* Solution-1: Most importantly, completely disable all manner of autosaves in the game options. [http://www.nexusmods.com/newvegas/mods/36730/? CASM] and [http://www.nexusmods.com/newvegas/mods/45652/? CASM with MCM] attempt to provide more control over such situations. [http://www.nexusmods.com/newvegas/mods/62181/? 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 five seconds with nothing happening are still safest. Also, you can use [http://www.nexusmods.com/newvegas/mods/57465 Clean Quick Saves] to create a new "quick save" file every time. You will need to periodically clean old ones out, but the purpose of a quick save is for a "temp" for safety's sake rather than a place to go back to.  They do not save as much data as a "full save".
+
:* Solution-1: Most importantly, completely disable all manner of autosaves in the game options. The [http://www.nexusmods.com/newvegas/mods/36730/? CASM] and [http://www.nexusmods.com/newvegas/mods/45652/? CASM with MCM] mods attempt to provide more control over such situations. [http://www.nexusmods.com/newvegas/mods/62181/? 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 five seconds with nothing happening are still safest. Also, you can use [http://www.nexusmods.com/newvegas/mods/57465 Clean Quick Saves] to create a new "quick save" file every time, which is safer than overwriting an existing file. You will need to periodically clean old ones out (they count against the total number of save files you are allowed), but the purpose of a quick save is as a "temp" for safety's sake rather than a place to resume the game session from.  They do not save as much data as a "full save".  QSaves are best reloaded when you are still in the same cell (preferably in the same position) as when you saved.
 +
:: Please see also the 'Fourth Rule: Reloading "save game" files' section of the wiki [[#FNV_General_Mod_Use_Advice | FNV General Mod Use Advice]] article.
  
 
* Cause-2: Crashes on cell transition will happen more often the more mods you have that affect NPC's & levelled lists.
 
* Cause-2: Crashes on cell transition will happen more often the more mods you have that affect NPC's & levelled lists.
Line 175: Line 1,589:
 
:* Solution-3: See [[#Issue: CTD without warning, "out of memory error", or stops responding|Issue: CTD without warning, "out of memory error", or stops responding]] sub-topic.
 
:* Solution-3: See [[#Issue: CTD without warning, "out of memory error", or stops responding|Issue: CTD without warning, "out of memory error", or stops responding]] sub-topic.
  
=== Issue: CTD without warning, "Out of Memory error", or stops responding ===
+
<span id="Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu"></span>
 +
=== Issue - CTD without warning or ''Out of Memory error'' or stops responding after the Main Menu ===
 
Happens without error messages, as if the game runs out of memory, or the OoM error message.
 
Happens without error messages, as if the game runs out of memory, or the OoM error message.
* Cause: The vanilla game's default "heap size" is very conservative and can easily be exhausted by a modded game.  There are a couple of distinct types of "heap" and it is not clear which is running out of memory.  One is used in programming to implement a data structure such as a priority queue, and another in memory management as an area for dynamic memory allocation and swapping code around.  Both types are commonly used.
 
  
:* Solution-1: Increase the heap allocation size. Initially use either the "Sheson memory patch" or NVSR.  The current NVSR (v4.1.36) "heap replacement" can also run into "out of memory" errors regardless of the algorithm chosen in some situationsBoth can work together, but even if they are not attempting to change the same heap allocation (unknown), their combined effect with the suggested sizes is to use up almost 1GB of game memory (out of 2-3.8GB) for this purpose.
+
*Cause-1: By default 32-bit games can only use 2GB of RAM not matter how much is installed, even if you are running a 64-bit version of the Operating System (OS).
 +
:* Solution-1a: If you are on a 32-bit OS system with at least 3GB of RAM, see this [http://wiki.nexusmods.com/index.php/2-4GB_game_memory_limits_and_solutions 2-4GB game memory limits and solutions] article on configuring to use the maximum memory you can before implementing the next solution64-bit OS systems usually do not need to alter their configuration, but that article covers them as well.
 +
:* Solution-1b: You need to be using a FNV4GB Loader such as [http://www.nexusmods.com/newvegas/mods/55061/? 4GB Fallout New Vegas Updated] or an LAA flag Patcher like the more recent [http://www.nexusmods.com/newvegas/mods/62552/? FNV 4GB Patcher].  This will give the game access of up to 3.8 GB of memory(The remainder is used by the system.)
  
::* 1a: Activate the "Sheson memory patch" (unknown type of heap) in NVSE.  This may require creating the "Data\NVSE"  folder, and the file "nvse_config.ini" in that folder(They are not automatically created by NVSE when you install it.)  Copy and paste the following two lines into the "nvse_config.ini" file:
+
* Cause-2: The vanilla game's default "heap size" is very conservative and can easily be exhausted by a modded gameThere are a couple of distinct types of "heap" and it is not clear which is running out of memory.  One is used in programming to implement a data structure such as a ''priority queue'', and another in memory management as an area for ''dynamic memory allocation'' and swapping code around.  Both types are commonly used.
<code>
 
[Memory]
 
DefaultHeapInitialAllocMB=448
 
</code>
 
::: Using a size of "240" or "256" is suggested if you are not using FNV4GB or some other means to utilize the maximum ~4GB of game memory.
 
  
::* 1b: Alternatively, The mod [http://www.nexusmods.com/newvegas/mods/34832/? New Vegas Stutter Remover] (requires  [http://nvse.silverlock.org/ NVSE]) contains both an adjustable heap size and alternative heap algorithms (unknown type of heap).  These are disabled by default for maximum stability, so it is necessary to read the provided documentation and edit the NVSR INI file.
+
:* Solution-2: Increase the heap allocation size.  Initially it's recommended to enable the "New Vegas Script Extender" (NVSE) "Sheson memory patch".  If that does not resolve the issue, you can try configuring "heap replacement" in "New Vegas Stutter Remover" (NVSR).  The current NVSR (v4.1.36) "heap replacement" can also run into "out of memory" errors regardless of the algorithm chosen in some situations.  It's effectiveness varies among users and systems.  Both can work together, as they are not attempting to change the same heap allocation, but their combined effect with the suggested sizes is to use up almost 1GB of game memory (out of 2-3.8GB) for this purpose. NVSR's current "heap replacement/allocation" routines have problems and should be used with caution.  See [[#Issue:_CTD_after_10-20_minutes_of_play_(post-Win10_2017_FCU)|Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)]].
:::* A larger heap size of 450(MB of RAM) is suggested, but Intel processors work more efficiently when they align with multiples of 16 bytes, so I suggest using a heap of 448, 464, or 512.
+
::* Solution-2a: Activate the "Sheson memory patch" (unknown type of heap) in NVSE.{{NVSE Configuration}}
:::* There are several "heap algorithms" and only some experimentation on your part will tell you which works best for your system.  This is documented in the INI file (located in the "Data\NVSE\Plugins" folder) as well as the download page.
+
::* Solution-2b: Optionally, the mod [http://www.nexusmods.com/newvegas/mods/34832/? New Vegas Stutter Remover] (requires  [http://nvse.silverlock.org/ NVSE]) contains both an adjustable heap size and alternative heap algorithms (unknown type of heap).  These are disabled by default for maximum stability, so it is necessary to read the provided NVSR documentation and edit the "sr_New_Vegas_Stutter_Remover.ini" file, which is under the "Data\NVSE\Plugins" folder.
:::* The current NVSR (v4.1.36) "heap replacement" and algorithms can be reliably demonstrated to increase the number of CTDs and "out of memory" errors under certain circumstances, so only testing will tell if it is a solution for you.  However, many have success with it in typical modded games. Other features of NVSR are still of practical use.
+
:::* That NVSR "heap" section is only used if you have "bReplaceHeap=1" in the "[Master]" section of that INI.  You should want to implement it because you are still getting crashes after implementing "Sheson".  It's effectiveness has varied results for different users.
 +
:::* A larger heap size of 450(MB of RAM) is suggested, but Intel processors work more efficiently when they align with multiples of 16 bytes, so I suggest using a heap of 448, 464, or 496.  Keep it under 500, which seems to be the limit for NVSE.
 +
:::* There are several "heap algorithms" and only three algorithms that use the "heap size" setting (3,5, or 6), so some experimentation on your part will tell you which works best (if at all) for your system.  This is documented in the INI file as well as the download page.
 +
:::* The current NVSR (v4.1.36) "heap replacement" and algorithms can be reliably demonstrated to increase the number of CTDs and "out of memory" errors under certain circumstances, so only testing will tell if it is a solution for you.  However, many have success with it in typical modded games.
 +
:::* Other features of NVSR are still of practical use.  Some people have found that disabling NVSR's heap ("Heap Replacement=0") solves their "out of memory" CTDs.
  
:* Solution-2: Enable two "purge cells" options in the "Fallout.INI" file:
+
* Cause-3: Too many cells loaded consuming memory.
<code>
+
:* Solution-3: Enable two "purge cells" options in the three "INI" files:
[General]
+
::<pre>
bPreemptivelyUnloadCells=1
+
::: [General]
</code>
+
::: bPreemptivelyUnloadCells=1
 +
::</pre>
 
:: and
 
:: and
<code>
 
[BackgroundLoad]
 
bSelectivePurgeUnusedOnFastTravel=1
 
</code>
 
  
Solutions 1 and 2 can safely be combined.
+
::<pre>
 +
::: [BackgroundLoad]
 +
::: bSelectivePurgeUnusedOnFastTravel=1
 +
::</pre>
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 10px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">
 +
Avoid auto-purge mods and NEVER use the ''PurgeCellBuffers'' (PCB) command. It's a debugging tool used for testing cell and reference loading, not a magic fix for memory problems.  Overly aggressive purging will cause stutter as purged cells have to be loaded from disk into memory for rendering.  Use the above INI settings if you want the game to clear buffers more aggressively than it does by default.
 +
</div>
 +
 
 +
* Cause-4: Exhausting video memory.
 +
:* Solution-4: See the sub-topic [[#Issue: Is ENBoost for everyone?|Issue: Is ENBoost for everyone?]] in this article about an option to increase available memory for rendering video related objects.
 +
 
 +
* Cause-5: Some have found it either necessary or desireable to configure their system to disable the "onboard" video adapter and use only the "addon" video card GPUs.  Depending upon the hardware architecture of the system, this may not be optimal.
 +
 
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 30px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Most modern "MotherBoards" (MoBo) have an integrated video adapter chip built-in (aka "onboard").  This is connected to the "Central Processing Unit" (CPU), and may be slower than a dedicated video card.  Modern video adapters come with one or more "Graphic Processor Units" (GPU), and "addon" video cards are installed into the "peripheral adapter" slots.
 +
 
 +
CPUs are not the same as GPUs.  CPUs are "general" processors, and GPUs are "graphics" processors.  There are differences in the hardware "buss" bandwidth, buffers, and speed used by both.  GPUs are optimized for high precision numbers and complex mathematical and geometric calculations which are necessary to render graphics.  Some CPUs (particularly laptops) sacrifice precision math processing to reduce power drain and increase battery life, and their "onboard" video chips come without dedicated VRAM for video memory (they have to share system RAM).  (If the details are of interest, suggest you read [http://harrydawsonunit20task2and3.weebly.com/central-processor-unit.html this CPU article] and [http://harrydawsonunit20task2and3.weebly.com/graphic-processor.html this GPU article].  In particular pay attention to the neglected role of "L-caches".)
 +
 
 +
The CPU is responsible for directing the graphics data from memory and disk to the video adapter (just as for any "peripheral" device).  Until it does so, the GPU has nothing to work on.  So it is the first potential bottleneck.  A MoBo integrated video adapter MAY be able to work in conjunction with an "addon" video card, or it may obstruct one.  This is one of those specific design features nobody talks about and you can only work it out by trial and error.  A video adapter and it's GPU(s) are essentially a "black box" to the CPU.  However, it does recognize which "port" (connector) the display is plugged into.  As far as the CPU is concerned, the video adapter and the "display" are basically the same: a one way street it sends graphics commands down with (at best) a stop light to prevent overflows.  The video adapter handles the signaling requirements of the display.
 +
</div>
 +
:* Solution-5: As a general "rule of thumb": the more processors, the better.  The video card may have a "device driver" or "control application" which will allow configuration of the use of the GPUs for specific purposes.  Unless you have specific knowledge and reasons, it is best to let the system choose how to handle ALL the GPUs.  A bad configuration may cause CTDs.
 +
 
 +
Solutions 1-4 can safely be combined, but those with less than 4GB of system RAM need to exercise caution and only implement one at a time, as they will come at the expense of memory otherwise needed by the game and OS.
 +
 
 +
<span id="Issue: CTD upon completion of DLC"></span>
 +
=== Issue - CTD upon completion of DLC ===
 +
For example: 'Fallout New Vegas keeps crashing to desktop, every time I complete the "Old World Blues (OWB)" DLC.  In the "Think tank" after having the last conversation with Dr. Klein, and then exiting the think tank... It crashes to desktop. I can tell it's the end of Old World Blues, because of the fact that sometimes it will play music for a second, (like it does at the end of the other DLCs, along with your video ending). But it just crashes to desktop.'
 +
 
 +
* Cause-1: According to Bethesda Softworks Tech Support - This only happens when playing in "Hard Core" mode and your character is the least bit hungry.
 +
:* Solution-1a: Simply feed your PC until they are full before the final exit from the DLC.
 +
 
 +
:* Solution-1b: There is the mod [http://www.nexusmods.com/newvegas/mods/56651 Skippable DLC Cutscenes], which skips the slideshow but cautions it is not a fix for CTDs.
 +
 
 +
* Cause-2: If not playing in "hard core mode", more than likely you are running out of "heap space" when the slideshows are started.
 +
:* Solution-2: Please search this guide for the term "heap size" (several entries are primarily in the 'Solutions to Performance problems' and 'Solutions to "Crash To Desktop" (CTD) problems' sections.
 +
 
 +
<span id="Issue: CTD upon quitting a modded game"></span>
 +
=== Issue - CTD upon quitting a modded game ===
 +
Upon using the game menu to "Exit to desktop", it simply hangs and Windows reports FNV has stopped responding.  It becomes necessary to use the Windows "Task Manager" ("<Ctrl+Alt+Del>") to terminate the current instance of the program before it can be restarted.  As this can leave system memory in an unknown state, best practice is to reboot the system first.  Naturally this is very annoying.
 +
 
 +
* Cause: This is a common problem with the game engine when enough mods have been added.
 +
:* Solution: [http://www.nexusmods.com/newvegas/mods/34832/? New Vegas Stutter Remover (NVSR)] has a "fast exit" option in it's INI file that fixes this problem (among others).  DO NOT install with a Mod Manager unless it recognizes that NVSE based plugins like NVSR need to go into the "Data\NVSE\plugins" folder.  Follow the "manual install" instructions instead.  Then edit the "sr_New_Vegas_Stutter_Remover.ini" file in the same location from "bfastexit 0" to "bfastexit 1".  Note: This setting still works for most people having the problems addressed in [[#Issue:_Recent_(post-Win10_FCU)_CTDs_after_10-20_minutes_of_play|Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play]].
 +
:: Related: The NVSE plugin [http://www.nexusmods.com/newvegas/mods/53635/? New Vegas Anti Crash (NVAC)] implements structured exception handling and sanity checking to reduce frequency of game crashes.  While this may not be directly related, it is a recommended stability improvement anyway.
 +
 
 +
<span id="Issue: Ash and Goo Piles cause random CTDs"></span>
 +
=== Issue - Ash and Goo Piles cause random CTDs ===
 +
When a spawned actor is killed with an energy weapon, they leave either an "ash" or "goo" pile instead of a body attached to the actor reference in the save game file.  If not "cleaned up" these pile up and eventually lead to "save game corruption".  The problem goes back to FO3 and a script which was supposed to be activated but wasn't.  It can be particularly noticable in exterior "encounter spawn zones" when using energy weapons exclusively with mods that increase the number of encounters before the default cell reset timer kicks in or if the player lingers in the cell too long.
 +
 
 +
* Cause-1: Ash and Goo Piles not being cleaned up before they can cause a problem.  This does not seem to occur with interior cells as the number of piles usually remains low and the default cell reset interval is usually fast enough.
 +
:* Solution-1: There are mods intended to resolve this problem by various methods.  Some of these are:
 +
::* [http://www.nexusmods.com/newvegas/mods/64229 EVE - JIP Ash Pile Tweaks] - replaces EVE's new ash and goo puddles' implementation, from one that uses containers and scripts to move the deceased's contents to them, to a NVSE + JIP LN one that replicates the vanilla mechanics of the piles being activators.  The pile's own scripts has been changed to remain until a cell reset takes place, instead of disappearing right when you revisited them.
 +
::* [http://www.nexusmods.com/newvegas/mods/45484/ Ash and Goo Begone] - does also remove piles of "named NPCs" (including those of "quest NPCS") so don't use energy weapons on them.  It does NOT affect the placed Ash piles in the sacked caravans (they use a different ID) nor the Ash pile left in the Silver Rush after the first time you enter.
 +
::* [http://www.nexusmods.com/newvegas/mods/44710/? FOOK Ash Goo Pile Fix - Complete] - only affects "vanilla" piles, but not those from EVE weapons.  (This fix has been incorporated into YUP.)
 +
::: NOTE: This problem persists in the exterior "BigMT" sections of the DLC "Old World Blues" (and possibly in "Honest Hearts" as well) with all these mods, but not in the interiors.  Until a fix is identified, it is suggested avoiding the use of energy weapons in "BigMT" exteriors unless you can somehow exit the cell (which can trigger the cleanup script upon returning).
 +
 
 +
<span id="Issue: Hi-Rez Texture mod causes CTD"></span>
 +
 
 +
=== Issue - Hi-Rez Texture mod causes CTD ===
 +
Specific known example of this is the 26.3MB [http://www.nexusmods.com/newvegas/mods/65017/? Training Dummy Retexture] file from the mod of the same name.  It is implied (by the alternate 3.1MB "Sane Edition" file) that this image is 6000x6000 pixels.
 +
 
 +
* Cause: Image files have to be sized as a power of 2 from the base of 512x512 pixels.  (512: *2= 1024; *(2^2)= 2048; *(2^3)= 4096; *(2^4)= 8192.)  Normally the GPU will attempt to re-scale images that do not fit, but a very large size may be sufficient to push GPU processing and VRAM limits enough to cause a CTD.  The various images sizes of the textures rendered in a given scene are cumulative.
 +
:* Solution: Either use a more normal sized image, or resize it using a tool such as [http://www.nexusmods.com/oblivion/mods/42116/? Optimizer Textures] that can correct the scale.  Please see also the wiki [[Display_resolution_versus_Image_Size|Display resolution versus Image Size]] article before you decide to simply grab the largest possible size images.
 +
 
 +
<span id="Issue: Removing a Project Nevada Implant freezes the game or CTDs"></span>
 +
=== Issue - Removing a Project Nevada Implant freezes the game or CTDs ===
 +
This is particularly evident when removing a "skill-based" one (i.e. raises the Sneak skill).
 +
* Cause: It appears that, by design with this mod, not only are there distinctions between individual doctors (all are not equally skilled; some need the "cybernetic surgery" book before they can install implants), but it also tracks which installed a particular implant.  More investigation is needed into the untrapped error that is causing the freeze or CTD itself.
 +
:* Solution: It seems the only safe way to remove a PN implant is to use the same doctor who installed it, especially with "book trained" doctors like Doc Mitchell.
 +
 
 +
<span id="Issue: Swap/Page file size and CTDs"></span>
 +
=== Issue - Swap ''aka Page'' file size and CTDs ===
 +
* Cause: The size set for your "page file" can make a difference as well in terms of something called the "commit limit".  This is the sum of physical memory and the sizes of the paging files.  The default system page file configuration does not follow this advice, so it's something to look into if you are still having CTDs.
 +
:* Solution: To properly size the paging file requires determining the maximum total commit charge for the programs you like to have running at the same time.  See "Page File Size and The Commit Limit" section in the wiki [http://wiki.tesnexus.com/index.php/2-4GB_game_memory_limits_and_solutions 2-4GB Game memory limits and solutions] article for details.
 +
 
 +
<span id="Issue: WIN10 Freezes/Hangs and you can't use Task Manager to kill the process"></span>
 +
=== Issue - WIN10 Freezes or Hangs and you can not use Task Manager to kill the process ===
 +
In Windows10 (Home or Pro versions at least) if the game freezes, even if you press "< Ctrl+Alt+Del >" and open the "Task Manager", you are unable to "< Alt+Tab >" from the game to the "Task Manager" in order to kill the process.  However, you can press the "Windows Logo" key (assuming your keyboard has one).  (Those without a "< Windows Logo >" key should read the thread [http://forums.windowssecrets.com/showthread.php/164357-Wndows-logo-key-equivalent-in-non-windows-keyboards Windows logo key equivalent in non-windows keyboards] if they feel the lack.)
 +
 
 +
* Cause: The game "freeze/hang" is preventing normal keyboard "< Alt+Tab >" function.
 +
:* Solution: The "mod" [http://www.nexusmods.com/fallout3/mods/23188 Kill Fallout 3] by '''raz3rITA''' is really a simple BAT file that can be edited to kill the "Task Manager" process of Fallout3.exe, FalloutNV.exe, or Fallout4.exe, and so on, as a single command from the "start menu" accessed by the "< Windows Logo >".  This will enable you to regain keyboard control.  Customization and use instructions are in the mod description.
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 50px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Note: While this does in effect enable you to attempt to resume the game immediately without rebooting, there are risks.  You have no idea what state your system memory is in as a result of whatever hung game up in the first place.  Something was not "normal" to cause the problem.  Not rebooting can lead you on a "wild goose chase" of other problems as a result (such as the "0xC0000005 Invalid access" error).  Starting from a "clean slate" is worth the delay caused by a reboot to my mind.  But the choice is yours.  At least this enables you to perform a normal orderly restart.
 +
</div>
 +
 
 +
== Solutions to Control problems ==
 +
 
 +
<span id="Issue: Console - How to access the in-game "console" command line"></span>
 +
=== Issue - Console - How to access the in-game ''console'' command line ===
 +
There is a setting of "bAllowConsole=1" under the "[Interface]" section of the "Fallout_Default" INI file that must be present as well.  (This setting is also necessary for Oblivion and Fallout 3.)
 +
 
 +
To access the console in the game, press the <'''~'''> (tilde) key on the keyboard. For a complete list of the console commands, type '''help''' in the console.
 +
 
 +
NOTE: The Tilde key should be to the left of the 1 key on the top row. If you are in the UK, and have your keyboard configured for the UK, the key is not going to be the same. To get to the console, press the <'''`'''> (grave accent) key top left of keyboard, instead of the <'''~'''> (tilde) key. (That's where the tilde is on most US keyboards).
 +
 
 +
Source: [http://help.bethesda.net/app/answers/detail/a_id/16893/~/how-do-i-access-the-console-in-the-game%3F The Elder Scrolls III: Morrowind Support] page:
 +
 
 +
<span id="Issue: Console - in-game console ['''~'''] (tilde) key doesn't work"></span>
 +
 
 +
=== Issue - Console - in-game console default key does not work ===
 +
Source: [http://help.bethesda.net/app/answers/detail/a_id/16893/~/how-do-i-access-the-console-in-the-game%3F The Elder Scrolls III: Morrowind Support] page:
 +
 
 +
If you have a system with the '''Microsoft eHome''' (remote sensor, aka "infrared") or '''MS Media Center''' devices, these will conflict with the program being able to read the scan code for the tilde key from the keyboard. Those Microsoft eHome devices or drivers need to be disabled in order to allow the game to 'see' the tilde key being pressed. The MIRC (Microsoft Infrared Remote Control, aka "Inf Transcvr") seems to disable the tilde <'''~'''> key in both Oblivion and Morrowind. Simply disconnecting the MIRC from the USB port will fix this issue.
 +
 
 +
<span id="Issue: Console - Can't open the in-game "console" command line under Windows 10"></span>
 +
=== Issue - Console - Can not open the in-game ''console'' command line under Windows 10 ===
 +
* Cause: The "key binding" to open the console is hard-coded in the game and apparently this binding is broken under Windows 10.  There is no game provided mechanism to change this.
 +
 
 +
:* Solution: There are a couple of mods that use NVSE as a workaround that may help in this situation.
 +
::* [http://www.nexusmods.com/newvegas/mods/63735/? Console Fix Glasses] by Random Unit
 +
::* [http://www.nexusmods.com/newvegas/mods/63747/? Console Key Rebinder] by Random Unit
 +
 
 +
<span id="Issue: Console - troubleshooting"></span>
 +
=== Issue - Console - troubleshooting ===
 +
Source: [http://fallout.gamepedia.com/Gamebryo_and_Creation_console_commands Gamebryo and Creation console commands]
 +
 
 +
* To enable the "console" for use in-game, in the INI files you must first locate "bAllowConsole" under the "[Interface]" section and set it to "=1" and save, before starting the game.
 +
* Furthermore, the console can be altered in these INI files to modify the text displayed on-screen.
 +
: Assuming a minimum of 768 pixels of vertical display resolution (for 720p monitor), you can change the following values under the "[Menu]" heading to: <pre>iConsoleVisibleLines=XX</pre>
 +
: Replace "XX" with a number of 25 or greater (depending on your screen resolution) to set the maximum number of text lines shown on screen at any one time in the console.
 +
 
 +
* Troubleshooting the console
 +
: The left side of the console might not be visible if you are not using a widescreen display. In this case, type several <tab>s to move the cursor to the right before entering your commands to make typed commands visible. Commands either typed off-screen or tabbed into view will still work equally.
 +
 
 +
: Alternatively, The position of console text can be set in the INI files.
 +
:* Set "iConsoleTextXPos" to 200 or so. Higher figures move console text to the right. This is the main problem.
 +
:* "IConsoleTextYPos" should be approximately 100 or 200 less than your Y resolution. A lower figure moves it up (0 is the top of the screen).
 +
 
 +
: An example for a 1280x1024 (X x Y) 5:4 ratio display:
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 30px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">
 +
{| class="wikitable" style="text-align: left; color: lightgray; background-color:#333333;" cellpadding="10"
 +
|+ '''Console Text Table'''
 +
! Setting !! Default !! New Setting !! Notes
 +
|-
 +
| iConsoleTextXPos ||  30 || 200 || X (left/right) position is higher (which moves it to the right)
 +
|-
 +
| iConsoleTextYPos || 940 || 900 || Y (up/down) pos is 100-200 less than your Y res (here, 1024)
 +
|}
 +
</div>
 +
 
 +
* Console improvements for "ease of use" are now available:
 +
:* [http://www.nexusmods.com/newvegas/mods/65906 Console Paste Support] enables copy-and-paste from other documents.
 +
:* [http://www.nexusmods.com/newvegas/mods/61843 Console Background] Adds a background to the console to enhance readability in bright surroundings.
 +
:* [http://www.nexusmods.com/newvegas/mods/55898 Auto SCOF - Console Logging]  Automatically creates a file in your FalloutNV folder titled "ConsoleOutputFile - mm_dd_yyyy" and starts the log with the time of creation to capture console output.
 +
:* [http://www.nexusmods.com/newvegas/mods/63747 Console key rebinder] in the event your default key <'''~'''> doesn't work.
 +
 
 +
<span id="Issue - GamepadSupport"></span>
 +
<span id="Issue: GamepadSupport"></span>
 +
 
 +
=== Issue - Controls - GamePad Support missing ===
 +
Symptoms: GamePad or Controller does not natively recognize key and mouse controls.
  
=== Issue: HUD-UI-Menu messed up or missing ===
+
* Cause: The game does not provide built-in support for the device.
* Cause: An XML file is missing an expected element. Usually this is caused by a mod installation overwriting the XML file in question.
+
:* Solution: Use a controller adapter keybard mapping program to add this functionality.  See [[#Issue - KeyControllerConflict|Issue - Controls - Mouse and/or keyboard don't work with a game controller installed]] for some options.
 +
::: Note that FNV will also require reconfiguring INI file settings and the use of the [http://www.nexusmods.com/newvegas/mods/58277 JIP LN NVSE Plugin] to support the controller (see [[#Issue - RemoveControllerDefaultButtons|Issue - Controls - How to remove a game controller's default button bindings]]).
  
* Solution: It can get complicated.  Read this [http://wiki.nexusmods.com/index.php/HUD-UI-Menu_issues HUD-UI-Menu issues] wiki article.
+
<span id="Issue - RemapDefaults"></span>
 +
<span id="Issue: Have to remap some essential default key assignments"></span>
  
=== Issue: Game in slow motion ===
+
=== Issue - Controls - Have to remap some essential default key assignments ===
* Cause-1: Fallout INI files are configured with wrong (too high) MinimumFPS setting.
+
* Cause: Various.
 +
:* Solution: For a hardware key failure, most laptops will let you use an external keyboard plugged into the PS2 or USB port.  But if that is not an option, you can "re-map" most crucial key assignments.
 +
::* First of all you are going to need to find a copy of the DirectX "scan codes" that gives you the hex code values, such as [http://geck.bethsoft.com/index.php?title=Template:DirectX_Scancodes this '''GECK''' document].
 +
::* Then open the "FalloutPrefs.INI" file in your "Users" folder and locate the "[Controls]" section.  That lists various "functions" with the "hex scan code" for each.  Change the ones you need (preserving leading zeros so each code is exactly 8 characters long) and save.
 +
::: (Suggest you only change what you have to there to get you into the game main menu where you can use the "Settings | Keyboard" menu interface to make most changes.)
 +
::* See '[[#Issue - KeystrokesPassed|Issue - How to determine what keystrokes are being passed]]' if you have problems.
  
:* Solution-1: Edit the INI files to lower the MinimumFPS setting to something like 20.  This, while noticeable, is still playable.  If the game is still too slow, you will need to reduce either the texture quality or screen resolution, or both.
+
<span id="Issue - RemoveControllerDefaultButtons"></span>
::: Make backups of the INI files before changing them.
+
<span id="Issue: How to remove a game controller's default button bindings"></span>
  
* Cause-2: Data\nvse\plugins\NV_Stutter_Remover.ini has "iFPSClamp" set to something other than 0.
+
=== Issue - Controls - How to remove a game controller default button bindings ===
 +
* Cause: The game lacks a "User Interface" or "Menu" option to change the default keys assigned to console-game type controller buttons.
  
:* Solution-2: Edit the "NV_Stutter_Remover.ini" setting to "iFPSClamp=0".
+
:* Solution-1: If you are using "Lutana's NVSE plugin" (now included as part of the [http://www.nexusmods.com/newvegas/mods/58277 JIP LN NVSE Plugin]), you can call it's [http://geck.bethsoft.com/index.php?title=DisableButton GECK: DisableButton] function from the console (default toggle key "~"), which will ignore the input from the specified controller button but still permit scripts to function. You can put a series of console commands into a "batch file" and call that to execute them all at once.  See the "Batch Examples" section of [http://fallout.wikia.com/wiki/Gamebryo_console_commands Gamebryo Console Commands].
::: Make backups of the INIs before changing them.
+
:: {{Lutana NVSE Plugin Status}}
  
* Cause-3: Many mod scripts running, especially during mod initialization. If specifically in Goodsprings, be aware that the "Weapons.of.the.New.Millenia" "cache cabinet"/"cheat chest" is known to cause this, but only in Goodsprings.
+
:* Solution-2: Edit the "FalloutPrefs.ini" file in your "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder as follows.
 +
::* Find the [Controls] section
 +
::* For the last 4 characters of each control that you want to unbind, put "FFFF".
 +
::: (ex: "Use=00FF0011" becomes "Use=00FFFFFF".)
 +
::* Save FalloutPrefs.ini
 +
:* Now you should be able to use a controller-keyboard mapper program like '''Xpadder''' to assign new keys to the buttons.
  
:* Solution-3: Review your mods and reduce the number that initialize only in that specific area.
+
<span id="Issue - SwitchWeaponsMouse"></span>
 +
<span id="Issue: How to switch weapons using the mouse middle-button/wheel"></span>
  
* Cause-4: Your hardware can't cope.
+
=== Issue - Controls - How to switch weapons using the mouse middle-button or wheel ===
 +
* Cause: This feature from "First Person Shooters" (FPS) is not implemented in FNV.
 +
:* Solution: The mod [http://www.nexusmods.com/newvegas/mods/39997/ FPS Weapon Wheel] by '''vivanto''' provides this functionality to both assignable hotkey and mouse wheel.  MCM menu configuration.
  
:* Solution-4: either reduce game settings for texture quality and/or screen resolution to less demanding levels, or invest in better hardware.  Specific component upgrades recommended are (in order of effectiveness for the price):
+
<span id="Issue - ModsLackControllerSupport"></span>
::* System RAM,
+
<span id="Issue: Mods don't seem to have controller support"></span>
::* Video RAM,
 
::* Faster CPU processor (number of cores is much less important for 32-bit games like FNV; but this option will often require a motherboard  and/or power supply upgrade as well, typically making it more expensive than any other options overall),
 
::* Faster disk drive.  (This is the slowest solution; even an SSD, though that is the best choice for this option.)
 
  
=== Issue: Distant terrain/LOD flickers rapidly ===
+
=== Issue - Controls - Mods do not seem to have controller support ===
This problem seems to occur more frequently with high-end systems, but across all sorts of platforms and video cards.
+
Some mods don't seem to work with a game controller, even though the game works fine in general.
* Cause: Known as "Z-fighting" or "stitching", this is a complex problem in 3D rendering where two or more "primatives" such as "layers" have similar or identical values in the "z-buffer", so they essentially occupy the same space.  The result is the pixels from each layer "fight" to be the one displayed on screen, especially when the point of view changes.  This causes a flickering, noisy display of first one then another color pixel.  See the "[https://en.wikipedia.org/wiki/Z-fighting Z-fighting]" article from Wikipedia for the full technical description.
 
  
* Solution: There is no single solution that applies to every system, and some of these effects cannot be resolved by the playerSee the S.T.E.P. Project Guide [http://wiki.step-project.com/Guide:Z-Fighting Z-Fighting] for examples of the issue and some INI tweaks that may help.  An FNV user tried some similar suggested by Gopher in [https://www.youtube.com/watch?v=XjHt-4Z6PwI this video] and had the most success with adjusting the "fNearDistance=" valueHe reports that anything above "10" results in clipping with arms and weapons in first person mode, but a balance can be reached with some testing.
+
* Cause: Select mods do have controller support, others require an addon such as the "Lutana NVSE plugin", and still others (like Project Nevada) don't have explicit support but can be used with Lutana's "DInput emulation" which maps controller buttons to keys on your keyboardWhat they all have in common is that they require NVSE, another third-party tool. There just isn't any provision for modders to add controller support to their mods, or even custom keyboard hotkeys, without these community toolsets.
 +
:* Solution-1a: Install the [http://nvse.silverlock.org/ New Vegas Script Extender (NVSE)] pluginNote that this has to be installed at the game root folder, so your mod manager may not be able to deal with it properly.  Best to install manually.
 +
:: See [[#Checklist|Checklist item #4]] for how to followup installation and determine the plugin is loading properly.
  
=== Issue: Unable to add either of two "weapon mods" to a weapon ===
+
:* Solution-1b: {{Lutana NVSE Plugin Status}}
* Cause: The mod "Weapon Mod Manager" only checks the first of 3 possible mod slotsIf this is blank, it assumes there are no mods available.
+
:: See also [[#Issue_-_KeyControllerConflict|Issue - Controls - Keyboard and-or mouse don't work with a game controller installed]].  This plugin must be installed to the game "Data\NVSE\Plugins" folderYour mod manager may not recognize that location, and manual installation may be required.
  
* Solution: Edit the "Items | Weapon" entry with GECK so the first and second "Mod Info" tab slots under "Game Effects" are not empty.
+
<span id="Issue - KeyControllerConflict"></span>
 +
<span id="Issue: Mouse and/or keyboard don't work with a game controller installed"></span>
  
=== Issue: Keyboard and/or mouse don't work with a game controller installed ===
+
=== Issue - Controls - Mouse and-or keyboard does not work with a game controller installed ===
* Cause: The game checks for it before the keyboard, and if detected ... disables the use of the keyboard.  Merely being connected can cause the game to ignore the keyboard and mouse.  Game controllers usually do not have the ability to be programmed to send key strokes and mouse buttons to the game interface.  FNV requires a controller (such as the XBox 360) which is "Xinput" compatible.
+
* Cause: The game checks for it before the keyboard, and if detected ... disables the use of the keyboard.  Merely being connected can cause the game to ignore the keyboard and mouse.  Game controllers usually do not have the ability to be programmed to send key strokes and mouse buttons to the game interface.  FNV requires a controller (such as the XBox 360) which is "Xinput" compatible. Some mods will require DirectInput/"DInput" emulation to work with a controller.  (See this [https://en.wikipedia.org/wiki/DirectInput DirectInput] Wikipedia article for an overview and comparison of the two Device Input APIs.)
  
:* Solution-1: Third-party controller adapter software.
+
:* Solution-1: Third-party controller adapter software. There are others, but the most commonly referenced is:
 
::* [http://www.xpadder.com/?lang=english Xpadder] ($9.99) - maps keyboard keys and mouse button actions to your game controller buttons.
 
::* [http://www.xpadder.com/?lang=english Xpadder] ($9.99) - maps keyboard keys and mouse button actions to your game controller buttons.
 
::: Xpadder also allows you to map the mouse pointer to your game controller sticks.
 
::: Xpadder also allows you to map the mouse pointer to your game controller sticks.
 
::: Xpadder can also handle combinations, sequences, toggles, triggers, shift sets, multiple controllers and more.
 
::: Xpadder can also handle combinations, sequences, toggles, triggers, shift sets, multiple controllers and more.
 
::* [http://www.majorgeeks.com/files/details/xpadder_%28last_freeware_version%29.html Xpadder v5.3] (last freeware version: 13 Apr 2008)
 
::* [http://www.majorgeeks.com/files/details/xpadder_%28last_freeware_version%29.html Xpadder v5.3] (last freeware version: 13 Apr 2008)
 +
:::: Note that you will lose rumble/vibration on your controller since you will have to choose the "keyboard" input device in the game options menu.  Xpadder essentially treats the controller like a secondary mouse & keyboard.
 +
::* [https://sourceforge.net/projects/antimicro.mirror/ antimicro] (freeware) Gamepad device specific support with various '''Linux''' distributions, '''Windows''' (Vista and later), and '''FreeBSD''', but with limited support for '''FreeBSD''' and '''Windows XP'''.
 +
:::* [https://www.nexusmods.com/newvegas/mods/70603 FNV Gamepad for mods (Antimicro Profile)] Mod: Gamepad profile for Antimicro configured to offer support for certain FNV specific mods.
  
:* Solution-2: A "Keyboard/Video/Mouse" (KVM) switch that mechanically let's you switch those devices between one computer and another MAY be a possible solution if your game controller will connect to it and you can disconnect the controller from the computer by means of the switch instead of unplugging it.
+
:* Solution-2a: The "Lutana NVSE plugin" provides DirectInput (aka "DInput") emulation modes (as opposed to the newer, more current DirectX Input (aka "Xinput") mode) which enable controller input with mods that normally require the keyboard, such as Project Nevada.  See the mod download page for instructions.  As this plugin also provides many other additional functions, it is often required by other mods.
 +
:: {{Lutana NVSE Plugin Status}}
 +
:* Solution-2b: A missing configurable feature of '''JIP LN NVSE''' mod, and a cleaner implementation of the original '''Lutana''' version is:
 +
::* [https://www.nexusmods.com/newvegas/mods/71894 Controller Support NVSE] by '''Luthien Anarion''' (the LN of JIP LN), Emulates keyboard and mouse inputs when controller buttons are pressed.
  
:* Solution-3:
+
:* Solution-3: A "Keyboard/Video/Mouse" (KVM) switch that mechanically let's you switch those devices between one computer and another MAY be a possible solution if your game controller will connect to it and you can disconnect the controller from the computer by means of the switch instead of unplugging it.
 +
 
 +
:* Solution-4: Disconnect your controller and use only the keyboard.
 
::* Disconnect the game controller from your computer.
 
::* Disconnect the game controller from your computer.
 
::* In the game's Main Menu, select "Settings" and then "Key Mappings".
 
::* In the game's Main Menu, select "Settings" and then "Key Mappings".
::* In the bottom right corner click on "Device" and change it from "controller" to "keyboard/mouse".  ** Then exit the game and restart it from the vanilla launcher.  (This is necessary so it will update the hardware settings in your INI files.)
+
::* In the bottom right corner click on "Device" and change it from "controller" to "keyboard/mouse".   
 +
::* Then exit the game and restart it from the vanilla launcher.  (This is necessary so it will update the hardware settings in your INI files.)
 +
: See also the [[#Issue - ModsLackControllerSupport|Issue - Mods don't seem to have controller support]] entry.
  
=== Issue: Logitech Mouse doesn't highlight or select menu choices ===
+
<span id="Issue - MouseMisbehaves"></span>
 +
<span id="Issue: Mouse controls"></span>
 +
 
 +
=== Issue - Controls - Mouse misbehaves ===
 +
Your mouse doesn't behave "in-game" as it does on the desktop.
 +
 
 +
Pipboy hotkeys:
 +
* TAB = Toggle Pipboy open/closed.  Hold several seconds to toggle Pipboy "flashlight".
 +
* F1 = Stats (submenus for reputation, challenges completed, etc.),
 +
* F2 = Inventory (submenus for weapons, apparel, aid, miscellaneous),
 +
* F3 = Data (submenus for map, quest status, notes, and the radio).
 +
<br>
 +
* Cause-1: Game INI "[Controls]" settings.
 +
:* Solution-1: The default "fForeground=" and "iPresent=" values can conflict with the system mouse acceleration, but changes to them can make menu speeds crazy high, so you need the "bBackground=0" changed to "=1" to fix (slow) the menu speeds.  Some users find that "bBackground Mouse=1" makes the mouse in menus too slow, so some experimentation may be needed.
 +
 +
:: Backup first (see the [[FNV_General_Mod_Use_Advice#Game_INI_files|Game INI files]] section for details), and then edit all three Fallout INI files so they use the following settings:
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 50px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#424242;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">[Controls]
 +
bAlwaysRunByDefault=1<br>
 +
bBackground Mouse=1<br>
 +
bBackground Keyboard=1
 +
</div>
 +
:: Add: under [Controls] to disable mouse acceleration:
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 50px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#424242;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">fForegroundMouseAccelBase=0
 +
fForegroundMouseAccelTop=0
 +
fForegroundMouseBase=0
 +
fForegroundMouseMult=0</div>
 +
:: and Change: (from 1 to 0)
 +
::<pre>iPresentInterval=0</pre>
 +
 
 +
* Cause-2: Using a "more than one monitor" setup, and the mouse does not stay confined to the game screen/window, but unexpectedly moves onto the other monitor(s) causing unwanted events when configured to "extend/span" across the monitors.
 +
: Video cards designed to drive multiple monitors have their own "video control panels" for configuring the monitor setup to either "span" (display a video screen across all the monitors at one as if one large monitor), or "duplicate" the same screen on each monitor.
 +
:* Solution-2: Use the vendor provided control panel to configure the display to "span" the monitors.  Then configure the game to run in "windowed" mode by changing the three INI files setting to "bFullScreen=0".  (Full screen would span across all the monitors at once otherwise.)  If you do not have a vendor "control panel" with multi-monitor setup for your monitors, try this tool:
 +
::* [http://dualmonitortool.sourceforge.net/ Dual Monitor Tools] (open source generic multi-monitor control).
 +
::: It has a setting to lock the mouse to a certain screen with a hotkey if necessary.
 +
:: Finally use one of the following tools to "confine" the cursor to the game window by running it in a "fake fullscreen borderless window":
 +
::* [http://www.nexusmods.com/newvegas/mods/59266/? OneTweak] by virusek.  Requires NVSE.  (There is a Skyrim version as well.)
 +
::* [http://www.nexusmods.com/newvegas/mods/57843/? FullScreenWindowedMode] by TimThompson89.  Also requires a "Script Extender", but works with OBSE, SKSE, FOSE, and NVSE.
 +
 
 +
* Cause-3: There are points in the game where scripts "DisablePlayerControls" deliberately.  Usually this is to prevent the Player from interrupting messages or "cut-away scenes", but sometimes control is not returned to the Player, with the result that the Pipboy menu and other functions like attacking, blocking, and crouching (either with the mouse or the keyboard) fail to work.
 +
:* Solution-3: Use the console command (<~> key) "EnablePlayerControls" (without the quotes).  If this solution is only temporary, see the earlier "Causes" and the [[#Issue - KeyControllerConflict|Issue - Controls - Mouse and/or keyboard don't work with a game controller installed]] entry.
 +
 
 +
<span id="Issue - Mouse(Logitech)"></span>
 +
<span id="Issue: Mouse (Logitech) doesn't highlight or select menu choices"></span>
 +
 
 +
=== Issue - Controls - Mouse ''notably Logitech'' does not highlight or select menu choices ===
 
This issue occurs with the vanilla game and no mods installed.  It may have worked fine with older versions of Windows, but now fails with the latest.
 
This issue occurs with the vanilla game and no mods installed.  It may have worked fine with older versions of Windows, but now fails with the latest.
 
* Cause: Logitech drivers have a long history of problems working with Windows games if any of their "advanced" driver features are used.
 
* Cause: Logitech drivers have a long history of problems working with Windows games if any of their "advanced" driver features are used.
Line 269: Line 1,921:
 
:* Solution-2: Uninstall all Logitech drivers and add-on software like "SetPoint".  Reboot, and install the bare bones "Microsoft Mouse compatible" driver and any updates instead.  If the Logitech mouse won't work with a bare bones MS certified driver, use a different more compatible mouse.
 
:* Solution-2: Uninstall all Logitech drivers and add-on software like "SetPoint".  Reboot, and install the bare bones "Microsoft Mouse compatible" driver and any updates instead.  If the Logitech mouse won't work with a bare bones MS certified driver, use a different more compatible mouse.
  
=== Issue: Scope zoom distortion problems ===
+
<span id="Issue - RemapAmmoSwap"></span>
 +
 
 +
=== Issue - Controls - Remapping the ''ammo swap'' hotkey from key -2- ===
 +
The issue revolves around the fact the game control configuration permits you to remap the "ammo swap" key from the default < 2 > hotkey to something else.
 +
* Cause: Contrary to expectations, this ability to remap "ammo swap" to a different key does not enable you then use the < 2 > key like the other number hotkeys.  '''You cannot get the use of the < 2 > key as an 8th hotkey.'''  Once you unassign the < 2 > key, it won't ever seem to function again.  The game control configuration menu simply ignores any attempts to remap < 2 > to any command; not even back to "ammo swap" again.
 +
 
 +
:* Solution: Edit the "FalloutPrefs.INI" file (located in the "Users" folder).
 +
::* Locate the "[Controls]" section.
 +
::* Find the "Hotkey2" entry; which is called "AmmoSwap" instead.
 +
::* To restore "AmmoSwap" back to using the < 2 > key, change the value to "0003FFFF".
 +
:* There is an optional ability to consolidate the 7 hotkeys to the number key sequence "1-7", and move the "swap ammo" function to the number "8", as follows.  (Everything after a semi-colon is a comment which should not be entered.)  This one won't re-order the icons in the inventory, but it'll still work. In the inventory, if you press the < 2 > key, it'll basically light up slot 8, is all.
 +
<div name="Simulated code box" class="boilerplate metadata" id="Warning Notice"
 +
style="margin:0px 10px 10px 50px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
/* Remove the next four 'white-space' lines to restore default white-space processing. */
 +
white-space: pre-wrap;      /* css-3 */
 +
white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
 +
white-space: -pre-wrap;      /* Opera 4-6 */
 +
white-space: -o-pre-wrap;    /* Opera 7+ */
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">
 +
* Hotkey1=0002FFFF    ; key < 1 >
 +
* Hotkey3=0003FFFF    ; key < 2 >
 +
* Hotkey4=0004FFFF    ; key < 3 >
 +
* Hotkey5=0005FFFF    ; key < 4 >
 +
* Hotkey6=0006FFFF    ; key < 5 >
 +
* Hotkey7=0007FFFF    ; key < 6 >
 +
* Hotkey8=0008FFFF    ; key < 7 >
 +
* Ammo Swap=0009FFFF  ; key < 8 ></div>
 +
 
 +
<span id="Issue - GazingFreeze"></span>
 +
 
 +
=== Issue - Gazing in certain directions causes a ''freeze'' ===
 +
In certain locations the game appears to freeze when looking in certain directions.  Attempting to use the mouse to turn in place takes 10-30 seconds to respond in changing the direction of view.<br>
 +
Known problem locations:
 +
# Looking South of '''Matthews Animal Husbandry Farm'''.
 +
# Looking West from the '''Searchlight Airport''''s Western fence.
 +
# Looking North of '''Guardian Peak'''.
 +
# Looking South from '''The Devil's Throat'''.
 +
 +
* Cause: Mod conflict.
 +
:* Solution: The "Fallout Character Overhaul" (FCO) mod's included "Glowing Ghouls" optional file "FCO - GlowingOne.esp" has been identified as at least one source of this problem.  No reports of any patches to this file correcting the situation.
 +
 
 +
<span id="Issue - GrenadeThrow"></span>
 +
 
 +
=== Issue - Grenade throw always falls at my feet ===
 +
* Cause: The "grenade throw" (thrown explosive) weapon has been separated in FO3 and FNV from other "throwing" weapons and is now based upon "explosives skill".  The "grenade throw" key is not clearly documented in the list of [http://fallout.wikia.com/wiki/Fallout:_New_Vegas_(PC) PC Controls for Mouse and Keyboard].
 +
:* Solution-1: Once a "grenade type"/"thrown explosive" is selected, just press and hold the "attack/fire" key/button for a couple of seconds.  The longer you hold it, the further the distance thrown (depending in part upon your aim and trajectory).
 +
:: NOTE: [http://fallout.wikia.com/wiki/Thrown_explosive thrown explosives] doesn't work as well as expected in VATS mode as explained in that section of the link.
 +
 
 +
:*Solution-2: [http://www.nexusmods.com/newvegas/mods/40040/? Project Nevada] has an option to have the distance thrown based on your Strength (STR) instead of the default of "explosives" skill, in addition to using a "hotkey" to combine the selection and throw.
 +
 
 +
:* Solution-3: There are also two other "grenade key" mods that are intended to make "grenade" (explosive) throwing easier:
 +
::* [http://www.nexusmods.com/newvegas/mods/38808/? Grenade Hotkey] by vivanto
 +
::* [http://www.nexusmods.com/newvegas/mods/58171/? Grenade Key] by svartberg
 +
 
 +
<span id="Issue - KeystrokesPassed"></span>
 +
<span id="Issue: How to determine what keystrokes are being passed"></span>
 +
 
 +
=== Issue - How to determine what keystrokes are being passed ===
 +
Sometimes "strange things happen" when you press a key and you wonder just what keystrokes were being sent.
 +
 
 +
* Cause: Either a mechanical fault in the keyboard or a remapped key function in the software.  Unfortunately there is no universal way to tell just which software has remapped conflicting keys.  These are usually "context specific", meaning they are part of the application and depend upon what it is expecting at that particular moment.  In the case of mods, the last to assign the key mapping "wins".
 +
 
 +
:* Solution: Software has been developed for showing even unprintable keystrokes (i.e. mouse-clicks) in real-time for streaming screencasts.  This can be used for troubleshooting as well.  The following are representative examples of available free programs:
 +
::* [http://github.com/Phaiax/PxKeystrokesForScreencasts PxKeystrokesForScreencasts] by '''Phaiax'''.
 +
::* [http://aalapshah.in/qipress/ QiPress] by '''aalapshah'''.  Lite version is free; Pro version requires a license.
 +
 
 +
<span id="Issue - HUD-UI-MenuCorrupted"></span>
 +
 
 +
=== Issue - HUD-UI-Menu messed up or unreadable or missing ===
 +
* Cause-1: You are using an HUD-UI-Menu mod such as [http://ui.darnified.net/wip/DUIFONV/v1/DUINVv04.7z DarNified UI] (DarnUI) which requires fonts other than the vanilla provided ones to display properly.
 +
 
 +
:* Solution-1: DarNified UI comes with a set of "DarN" fonts which must be added to the INI files, but there are other fonts available such as:
 +
::* [http://www.nexusmods.com/newvegas/mods/40471/? Alternative fonts for DarNified UI]
 +
::* [http://www.nexusmods.com/newvegas/mods/51066/? Alternative Fonts Pack for DarNifiedUI (with cyrillic support)]
 +
::* [http://www.nexusmods.com/newvegas/mods/60847/? HD More Alternate Fonts for DarNified UI] (in double resolution)
 +
:: DarnUI instructions to edit the "Fallout_default.ini" file come from the [http://forums.bethsoft.com/topic/1143482-wipzbeta-darnified-ui-nv/ DarnUI support thread], but it is recommended to edit all three INI files to be sure ("Fallout_default" in the game root folder and the two in the "Users" folder).  The mod [http://www.nexusmods.com/newvegas/mods/54611/? DarnifiedUI Configuration] is a script to automatically make the edits to the default INI file.
 +
:: Manual edit instructions are to replace the existing [Fonts] section with the following:
 +
<pre>
 +
[Fonts]
 +
; sFontFile_1=Textures\Fonts\Glow_Monofonto_Large.fnt
 +
sFontFile_1=Textures\Fonts\DarN_FranKleinBold_14.fnt
 +
; sFontFile_2=Textures\Fonts\Monofonto_Large.fnt
 +
sFontFile_2=Textures\Fonts\DarN_FranKleinBold_16.fnt
 +
sFontFile_3=Textures\Fonts\Glow_Monofonto_Medium.fnt
 +
; sFontFile_4=Textures\Fonts\Monofonto_VeryLarge02_Dialogs2.fnt
 +
sFontFile_4=Textures\Fonts\DarN_Sui_Generis_Otl_10.fnt
 +
sFontFile_5=Textures\Fonts\Fixedsys_Comp_uniform_width.fnt
 +
; sFontFile_6=Textures\Fonts\Glow_Monofonto_VL_dialogs.fnt
 +
sFontFile_6=Textures\Fonts\DarN_Sui_Generis_Otl_13.fnt
 +
; sFontFile_7=Textures\Fonts\Baked-in_Monofonto_Large.fnt
 +
sFontFile_7=Textures\Fonts\DarN_Libel_Suit_Otl_24.fnt
 +
sFontFile_8=Textures\Fonts\Glow_Futura_Caps_Large.fnt
 +
sFontFile_9=Textures\Fonts\NVFont_Test.fnt
 +
</pre>
 +
:: Note a semi-colon (";") at the beginning of a line "comments out" that line so it is not read but remains for reference.  Other alternative fonts can be used in place of the "DarN_<style>_<size>.fnt" entries, but in that instance it is recommended to add them and comment out the DarN fonts as well.  The "<size>" portion of the name is the number of "points tall" for that font. A large number equals a larger character size, so "6" is very small (short) and "24" is quite large (tall).  Either "10" or "12" is normal for most text.
 +
 
 +
* Cause-2: An XML file is missing an expected element.  Usually this is caused by a mod installation overwriting the XML file in question.
 +
 
 +
* Solution-2: It can get complicated.  Read this [http://wiki.nexusmods.com/index.php/HUD-UI-Menu_issues HUD-UI-Menu issues] wiki article.
 +
 
 +
<span id="Issue - MouseAfterFastTravel"></span>
 +
<span id="Issue - MOUSE - not working after fast travel"></span>
 +
 
 +
=== Issue - MOUSE - not working after fast travel ===
 +
* Cause: Unknown
 +
:* Solution-1a: After "fast travel", enter the Pipboy "map" tab (see [[#Issue - MouseMisbehaves|Issue - Mouse Misbehaves]] for hotkeys), move the mouse cursor around a bit and then "<Right-Click>" on the map to enter into the "marker placement" menu to see if it is working again.  It may take more than one attempt at wiggling the mouse cursor around, but once it responds to the mouse click it should work until the next time you "fast travel".
 +
 
 +
:* Solution-1b: Rename the "Fallout.INI" and "FalloutPrefs.ini" files located in the "C:\Users\<UserAccountName>\Documents\My Games\FalloutNV" folder to some different name.  (Just adding a different extension such as ".org" works.)  Then use the game "FalloutNVLauncher.exe" program to cause them to be rebuilt.  Refer to the backed up original version files for your previous changes.
 +
 
 +
<span id="Issue - MouseSensitivity"></span>
 +
 
 +
=== Issue - MOUSE - sensitivity or weapon aiming is off or similar issues ===
 +
Monitor is set to a higher than 1920x1080 resolution.
 +
 
 +
* Cause: FNV was designed for monitor resolutions common prior to 2010. "In 2010, 27-inch LCD monitors with the 2560 × 1440-pixel resolution were released by multiple manufacturers including Apple." - [https://en.wikipedia.org/wiki/Display_resolution Wikipedia on "Display resolution"].  "High Definition" (1920x1080, 16:9 aspect ratio) "FHD standard" was generally considered "high end" for gaming.  Newer monitors may have a higher default resolution.
 +
 
 +
:* Solution: Use a lower, more standard (in 2010) display resolution.  (Note the LED/Plasma monitors have a default resolution according to the screen size and "aspect ratio".  Lower resolutions may not fill the screen, resulting in "black borders" (e.g. "letterbox style").  "Windowed mode" may be a way around this visual problem.)  See the Wikipedia article quoted above for more on the subject, including a table of "resolution standards".
 +
 
 +
<span id="Issue - UnableAddWeaponMods"></span>
 +
<span id="Issue - Unable to add either of two "weapon mods" to a weapon"></span>
 +
 
 +
=== Issue - Unable to add either of two ''weapon mods'' to a weapon ===
 +
* Cause: The mod [http://www.nexusmods.com/newvegas/mods/44515 The Weapon Mod Menu (WMM)] only checks the first of 3 possible mod slots.  If this is blank, it assumes there are no mods available.
 +
 
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 10px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">
 +
: NOTE: This is a '''''very rare''''' issue.  See the entry [[#Issue - WMMBroke|Issue - WMM - "The Weapon Mod Menu" won't let me add a weapon mod in game]] first.  If you do confirm this issue with WMM is the cause, please inform the "current maintainer" listed in the "WIP" notice at the top of this article of the specific weapon with a link to the mod in question so a list of offending plugins can be compiled.
 +
</div>
 +
 
 +
:* Solution: Edit the "Items | Weapon" entry with GECK so the first and second "Mod Info" tab slots under "Game Effects" are not empty.  Typically this will mean moving the second and third slot entries up by one.  Be sure to make the plugin containing the Weapon in question the "active" one, as that is the plugin that will get saved.  Note this edit will only work if there are already weapon mods available for that weapon.  Adding weapon mods that do not already exist is a more involved "customization" process.
 +
 
 +
<span id="Issue - UnableDrawFireCrouch"></span>
 +
<span id="Issue: Unable to draw weapons, fire, or crouch"></span>
 +
 
 +
=== Issue - Unable to draw weapons or fire or crouch ===
 +
Also related: Sunny Smile's initial greeting dialog is actually that from a later stage:
 +
: Initial greeting: "Cheyenne, stay. Don't worry, she won't bite, unless I tell her to."
 +
: Later greeting: "Yeah alright. Let's just get done with this first and we'll talk later. Preferably somewhere I can get a stiff drink and Cheyenne can cool down".
 +
* Cause: Removal of all "tumbleweeds" from the game.  The first "tumbleweed" seen upon exiting Doc Mitchell's house after creating a character is scripted.  It's absence (i.e. a mod to remove all tumbleweeds also removes that script event) breaks the game.
 +
 
 +
* Solution:
 +
** Temporary: Move to somewhere you know you should be able to use all those functions, open the in-game console (<~> key), and enter "EnablePlayerControls" (without the quotes) and hit <Enter>.
 +
** Permanent: Uninstall any mods that remove all tumbleweeds before creating a new character.  Often this functionality is incorporated into "performance" mods, so if it isn't mentioned in the description some testing may be required.  However, once the character has stepped outside of Doc Mitchell's so the scripted "tumbleweed" event occurs, they may be installed.
 +
 
 +
<span id="Issue - WMMBroke"></span>
 +
<span id="Issue - WMM - "The Weapon Mod Menu" won't let me add a weapon mod in game"></span>
 +
 
 +
=== Issue - WMM - '''The Weapon Mod Menu''' will not let me add a weapon mod in game ===
 +
* Cause: There are a number of unspoken assumptions by [http://www.nexusmods.com/newvegas/mods/44515/? The Weapon Mod Menu (WMM)] that, when verified/resolved, are the usual solutions.
 +
 
 +
:* Solution-1: You are trying to "modify" the ''currently equipped weapon'' when you hit the "x" key.
 +
 
 +
:* Solution-2: You have a "weapon mod" that is appropriate for that specific weapon.  Most "weapon mods" only apply to very specific weapons.  There are (to the best of the collective knowledge) none that apply to ALL weapons.  So you have to check the name of the mod very carefully as the differences in the names are subtle.  The easiest way to determine the correct mod for a weapon in game is at the "green vending machines" provided by the additional mod [http://www.nexusmods.com/newvegas/mods/39651/? Weapon Mods Expanded (WMX)], which are generally found at all the "Gun Runners Arsenal" (GRA) storefronts.
 +
 
 +
:: (There are a very few instances where WMM will refuse to add weapon mods.  See [[#Issue - UnableAddWeaponMods|Issue - Unable to add either of two "weapon mods" to a weapon]] entry, but it will require you to look at the mod plugin internals in either [http://www.nexusmods.com/newvegas/mods/34703/? FNVedit] or GECK to verify.)
 +
 
 +
:* Solution-3: You have installed both [http://www.nexusmods.com/newvegas/mods/42507/? Mod Configuration Menu (MCM)] and WMM in the correct order.  (See the wiki article [[HUD-UI-Menu_issues|HUD-UI-Menu issues]].)
 +
 
 +
:* Solution-4: You do NOT have a game controller attached.  If you do, see the [[#Solutions to Control Problems|Solutions to Control Problems]] section.
 +
 
 +
:* Solution-5: If none of the above are the problem, see if you can find anything in the "fallout_nv_error.log" file.  (See [[#Checklist|Checklist item #4]].)
 +
 
 +
<span id="Issue - WMXLosesMods"></span>
 +
<span id="Issue - WMX - loses my existing weapon mods to the 'Weathered 10mm pistol'"></span>
 +
 
 +
=== Issue - WMX - loses my existing weapon mods to the ''Weathered 10mm pistol'' ===
 +
* Cause: This weapon has an unfortunate (seemingly hard-coded) bug that means that any weapon mods applied to it will not be visible on the weapon.
 +
 
 +
:* Solution: [http://www.nexusmods.com/newvegas/mods/39651 Weapon Mods Expanded (WMX)] detects that you have equipped the 'Weathered 10mm Pistol'.  The WMX menu (in the Pip-boy "Inventory" screen for the selected weapon) allows you to swap the defective original Weathered 10mm Pistol for a fully-functional duplicate of it. Doing so will effectively erase any weapon mods already applied to the weapon, so it is recommended to remove them first using [http://www.nexusmods.com/newvegas/mods/44515 The Weapon Mod Menu (WMM)].  When you are ready to proceed, select the 'Swap Weapon' button. Select 'Cancel' if you are not ready to proceed (this menu will appear again when you next equip the bugged Weathered 10mm Pistol).
 +
 
 +
<span id="Issue - ZoomControls"></span>
 +
<span id="Issue: ZoomControls"></span>
 +
 
 +
=== Issue - ZOOM controls ===
 +
Symptoms: Suddenly vision "zoom" features (such as "scoped weapons" and dialog "close-in to observe the speaker's face") and related manual controls are no longer working.
 +
 
 +
* Cause: Likely a "Field of View (FoV)" setting or conflict.
 +
:* Solution: Check FOV related setting in recently added mod INI files, such as (purely for example) "[https://www.nexusmods.com/newvegas/mods/65525 New Vegas Reloaded]" and "[https://www.nexusmods.com/newvegas/mods/55085 FOV Slider]", or enhanced configuration mod tools like [https://www.nexusmods.com/newvegas/mods/66347 lStewieAl's Tweaks].
 +
 
 +
<span id="Solutions to "Garden of Eden Construction Kit" (G.E.C.K.) problems"></span>
 +
 
 +
== Solutions to '''Garden of Eden Construction Kit''' ''aka '''GECK''''' problems ==
 +
{{GECK: Common Problems}}
 +
 
 +
== Solutions to Graphics problems ==
 +
 
 +
<span id="Issue: Aiming - 1st Person View (FPV) Iron Sights"></span>
 +
=== Issue - Aiming - 1st Person View ''aka FPV'' Iron Sights ===
 +
This is a built-in game Main Menu setting, under: "Settings | Game Play | True Iron Sights [ON | OFF]".  It is also accessible from the "Pause Menu" screen during a game session.  It is only visibly in effect in FPV.
 +
 
 +
Only certain weapons have this "feature", though some mods add it to weapons that lack it in vanilla.  When this setting is enabled, those weapons will switch:<br>
 +
* from "the weapon is shifted to the right of the center of the screen so it is not aligned between your 'eyes' and the target, and you aim using the crosshair" mode,<br>
 +
* to "the weapon is centered in the screen between your 'eyes' and the target so you aim by lining up the front and rear 'iron sights' on the weapon (no crosshair) just as in real life";<br>
 +
: when you click using the (default) Right-Mouse button (aka "<RClick>") as if "blocking with a melee weapon" or "zooming in on the target with a scoped weapon".
 +
 
 +
Without the "True Iron Sights" setting to ON, the same "weapon centered in the screen" view is displayed, but the "rear sight" on the weapon is lower down and you cannot "truly" align the front and rear sights.  You use the "crosshair" instead.
 +
 
 +
<span id="Issue: Aiming - 1st Person View (FPV) is off center"></span>
 +
=== Issue - Aiming - 1st Person View ''aka FPV'' is off center ===
 +
The situation is a bit more complex than it appears on the surface.  Apparent weapon position is determined by the animation files.  It is also tied in with whether or not you use the game's "Auto Aim" feature, which is active by default.  In addition there are various "Field of View" (FOV) settings the game switches between under certain circumstances, which affect what is visible of the scene.
 +
 
 +
* Cause-1: This is controlled by a single variable: "fFirstPersonHandFollowMult".  The default value is ".85", so this was a deliberate design decision to impose some inaccuracy by the developers, as a value of "1.0" is "dead center" of the aiming point.
 +
:* Solution-1a: The mod [http://www.nexusmods.com/newvegas/mods/55709/? Gun Follows Crosshairs in First Person] by '''Grasscid''' applies this fix.
 +
:: Note the mod [http://www.nexusmods.com/newvegas/mods/35781/? First Person Gun No Follow] by '''Azrael Dark''' combines nicely with "Gun Follows" so the gun doesn't follow the cross-hairs up out of the "neutral carry position" until you actually fire.
 +
:* Solution-1b: Set "fFirstPersonHandFollowMult" to "1.0".  (Some other mods use this setting as well, so conflicts are possible.)
 +
 
 +
* Cause-2: Your problem might be a result of changing the "Field of View" (FOV).
 +
<blockquote>
 +
From [http://www.tweakguides.com/Fallout3_8.html TweakGuides]:
 +
: fDefaultFOV=75.0000 - Shows the default Field of View in degrees for the game, which is 75 degrees. Changing the Field of View using this variable doesn't seem to work properly as it is not applied when the game starts, so instead you will need to use the FOV console command (See Console Commands section) each time you start them game to set a different field of view.
 +
 
 +
: Update: It has been discovered that by inserting the line fDefaultWorldFOV=75.0 at the bottom of the Display section of the Fallout.ini file, and assigning it a value equal to the FOV you want, you can now permanently change the default Field of View in the game. Remember however that if you change the default FOV, you may also need to change the FOV for other screen elements - see the fRenderedTerminalFOV and fPipboy1stPersonFOV commands below. Note also that you can alter the fDefault1stPersonFOV=55.0000 value to alter how much of your body/weapon is shown in front of you (Fallout.ini).
 +
</blockquote>
 +
 
 +
:* Solution-2a: [http://www.nexusmods.com/newvegas/mods/55085/? FOV Slider] by '''Roy Batty''' is a simple mod that adds an MCM menu that allows for adjusting the Fields of View for all of the game's camera views.  Look into "Weapon FOV scale" (to compensate for larger or smaller Player Fields of View and their affect on aim speed).
 +
 
 +
:* Solution-2b: Other than adjusting the various FOV settings, try tweaking the following default values (which set the camera position relative to the head node in FPV) in the INIs [General] section:
 +
*: Make backups of the INIs before changing them.
 +
<blockquote>
 +
:  fCameraPosX=0.0
 +
:  fCameraPosY=9.5
 +
:  fCameraPosZ=6.0
 +
:  bUseThirdPersonArms=1
 +
:  bTPArmsEnableIronSights=1
 +
</blockquote>
 +
 
 +
* Cause-3: A surprising number of vanilla weapons have misaligned meshes between the projectile nodes and the cross-hair.
 +
:* Solution-3: The [http://www.nexusmods.com/newvegas/mods/65052 Weapon Mesh Improvement Mod (WMIM)] by '''Roy Batty''' is an on-going effort to fix the vanilla weapons wholesale.  Similar issues with mod added weapons have to be taken up with their respective authors in comments on those mod download pages.  There are various individual mods to be found by using the Nexus "search" function on the term "iron sights".
 +
::<span style="color: red;background-color:#fff5f5;">NOTE: While '''WMIM''' is "meshes" and [http://www.nexusmods.com/newvegas/mods/38285 Weapon Retexture Project (WRP)] by '''Millenia''' is "textures", the latter includes modified meshes that are required for his textures to display properly with their own sub-folder, so it's incompatible with any other mods that adjust vanilla weapon meshes. (Notably most "Nifskope Weapon" mods and '''WMIM'''.  '''WRP v1.95''' from 2012 uses vanilla folder paths and is somewhat more compatible.)  The [http://www.nexusmods.com/newvegas/mods/38927 Rifle 1st Person Accuracy Fix] mod by '''joefoxx082''' is an alternative solution to the accuracy issue, though obviously not as comprehensive as '''WMIM'''. As is often the case, you may have to give up one mod or the other.</span>
 +
 
 +
 
 +
<span id="Issue: Aiming - 3rd Person View (TPV) is off center"></span>
 +
 
 +
=== Issue - Aiming - 3rd Person View ''aka TPV'' is off center ===
 +
* Cause: This is a more complex issue than aiming in 1st Person View (FPV).  The player is always viewing the action from the perspective of the camera.  The camera location is independent of the character's eyes, and from the weapon.  It is always "center of the screen".  In FPV, it is positioned to simulate the eye view of the character.  In 3rd Person View (TPV), the camera (and you) are not looking from the perspective of either the character or weapon.  Instead the camera is positioned behind and off to the side so the back of the character and more of the scene to the opposite side of the character is in view.  This camera setting is not generally adjustable, though there are mods that help.  The cross-hair is positioned in the center of the screen.  It is not accurately aligned with the character's eyes or the weapon.  The "Field of View" (FOV) controls how much of the cell scene is visible.  This is adjustable and there are actually a number of inter-related FOV settings.
 +
: Please see the [[#Issue: Aiming - Disable Auto Aim or not?|Issue: Aiming - Disable Auto Aim or not?]] section first to understand the role of Auto Aim on the problem.  As pointed out there, weapon animations are not aligned consistently the same.  In TPV, if Auto Aim is disabled there is no expectation that the alignment of the weapon is with the cross-hair.  As the camera position is behind and offset to the right (by default) from the center of the body so you are looking more or less along the angle of the weapon towards the cross-hair, but you can't even expect the cross-hair to be aligned with the position of the body facing either.
 +
 
 +
: It is important to understand: the game is not designed for accuracy while shooting in TPV.  You are in essence always "shooting from the hip", while situational modifiers ("iron sights", crouching, weapon skill, etc.) affect the "spread" inherent in the weapon.  (See [http://geck.bethsoft.com/index.php?title=Gun_Spread_Formula GECK: Gun Spread Formula].)  If you need accuracy, then by design you need to be in FPV (which is why the game switches you to that mode ''when you use certain weapons or a "Scope"'' and have "True Iron Sights" enabled).  Not all weapons have "Iron Sights" (i.e. some energy weapons) and some "Power Armor" mods are known to "break/replace" the vanilla "True Iron Sights" functionality.  For accuracy, you want a smaller "fOverShoulderFOV" value to more closely align the center of the screen with the cross-hair.
 +
 
 +
:* Solution-1: Use a mod that allows you to adjust the left to right offset of the camera position.  Either of works well combined with Solution-2 options:
 +
::* [http://www.nexusmods.com/newvegas/mods/34744/? Centered 3rd Person Camera] by '''Jahandar'''.
 +
::* [http://www.nexusmods.com/newvegas/mods/57588/? Dynamic Third Person Camera] by '''claustromaniac'''.
 +
 
 +
:* Solution-2: Use a mod that allows you to adjust how far behind the camera is offset from the PC's back.
 +
::* [http://www.nexusmods.com/newvegas/mods/44207/? 3rd-Person-Camera-FIX] by '''humannature66'''.
 +
::* [http://www.nexusmods.com/newvegas/mods/36773/? Further 3rd Person Camera] by '''Silverglade'''.
 +
 
 +
:* Solution-3: [http://www.nexusmods.com/newvegas/mods/55085/? FOV Slider] by '''Roy Batty''' is a simple mod that adds an MCM menu that allows for adjusting the Fields of View for all of the game's camera views.
 +
:: Those interesting in fighting primarily while in TPV should experiment with "fOverShoulderFOV" and "Iron Sight FOV Zoom Time".
 +
 
 +
<span id="Issue: Aiming - Disable Auto Aim or not?"></span>
 +
=== Issue - Aiming - Disable Auto Aim or not ===
 +
* Cause: In Fallout 3 and New Vegas bullets can actually curve or shoot in a direction they shouldn't based on a dice roll (on top of the normal bullet spread).
 +
: If we completely remove the Auto Aim features, the game fires your bullets from your weapon parallel to the 3D model (like it should be physically). The only issue is that every weapon is somehow differently aligned: the .44 Magnum is slightly pointing under the cross-hair, the Hunting Rifle is pointing to its right, etc ..  So without Auto Aim enabled, the cross-hair is not really where you are aiming anymore and it's different for each weapon.
 +
: Basically the Auto Aim feature redirects your bullets toward the center of the screen.  This would be a great feature if it wasn't also used in combat as a targetting aid.  When your cross-hair is near the bounding box of an enemy's limb, Auto Aim instead shifts the bullets towards the nearest limb.
 +
 
 +
:* Solution-1: [http://www.nexusmods.com/newvegas/mods/34723/? No Auto Aim] by '''EddieV223'''.  Rather than completely disabling Auto Aim, this mod uses some settings with values so small the effect is negligible.  Uses the following values (default = FalloutNV):
 +
::* fAutoAimMaxDistance: 50000.000000  (default: 1800.000000)
 +
::* fAutoAimScreenPercentage: 0.000100 (default: 10.000000)
 +
::* fAutoAimMaxDegrees: 0.000100      (default: 3.000000)
 +
 
 +
:* Solution-2: [http://www.nexusmods.com/newvegas/mods/36057/? Advanced VATS and FIXED Autoaim with Improved Binoculars] by '''orgolove'''. Sets the focus of the Auto Aim to the edge of the game engine's rendering distance, and thus ensures that any bullet accurately goes to wherever your crosshair is pointing. Uses the following values (default = FalloutNV):
 +
::* fAutoAimMaxDistance: 1000000.000000 (default: 1800.000000)
 +
::* fAutoAimScreenPercentage: 10.000000 (default: 10.000000)
 +
::* fAutoAimMaxDegrees: 3.000000 (default: 3.000000)
 +
::* fVATSH2HWarpDistanceMult: 0.100000  (default 0.270000)
 +
::* fVATSMeleeWarpDistanceMult: 0.100000 (default:0.320000)
 +
::* fVATSMaxChance: 100.000000 (default: NA, added by mod)
 +
::* fVATSMAXEngageDistance: 10000.000000 (default: NA, added by mod)
 +
::* fVATSMeleeMaxDistance: 1500.000000 (default: NA, added by mod)
 +
 
 +
:* Solution-3: [http://www.nexusmods.com/newvegas/mods/55085/? FOV Slider] by '''Roy Batty''' is a simple mod that adds an MCM menu that allows for adjusting the Fields of View for all of the game's camera views.
 +
:: Those interesting in playing while in 3rd Person View (TPV) should look into "fOverShoulderFOV" (which isn't available in FO3 but is added by the mod [http://www.nexusmods.com/fallout3/mods/15319/? Greatly improved 3rd person aiming] by Peste.)
 +
 
 +
<span id="Issue: Aiming - Full-Auto Iron Sights animation jump"></span>
 +
=== Issue - Aiming - Full-Auto Iron Sights animation jump ===
 +
With "full auto" weapons, when aiming down the "iron sights" in 1st person and firing (even with "JIP Select Fire" set to single shot) the whole weapon seems to jump down so that the iron sights are below the actual aim point. When you stop firing it returns to normal.
 +
 
 +
: Files that modify "iron sight" firing animations always have the word "attack" in them, and end with "is" (for "iron sight").  They begin with the number of hands holding the weapon (1h/2h), followed by the general weapon type ("P"istol, "A"utomatic, "R"ifle, "M"elee, etc.), which combined make up the "weapon category".  Automatic weapons all use one attack animation in their category: '''1hpattackloopis''' ("OneHandPistol" animation type in '''GECK''' or "Pistol - Ballistic" in [http://www.nexusmods.com/newvegas/mods/34703/? FNVedit]); '''2haattackloopis''' ("TwoHandAutomatic" or "Rifle - Automatic"); and '''2hrattackloopis''' ("TwoHandRifle" or "Rifle - Ballistic"). Other "iron sight" weapons have their attacks marked with a number ('''2hrattack''3''is''' for example).
 +
 
 +
: In order to know which animations cause problems, it would be beneficial to have '''FNVEdit''' installed, load all the mods affecting that weapon, and check which attack animation the weapon in question uses. Or if you use '''GECK''', you can discover this in the "Art & Sound" section of the weapon.
 +
 +
* Cause: When you fire it starts the full-auto attack loop and screws up aiming through the scope or iron sights.
 +
:* Solution-1: Mod [http://www.nexusmods.com/newvegas/mods/48509/? Improved Automatic Ironsight animations]
 +
 
 +
:* Solution-2: Mod [http://www.nexusmods.com/newvegas/mods/65052?tab=posts Weapon Mesh Improvement Mod]
 +
: There are other "weapon animation" replacement mods as well that may perform better with a particular weapon.  Now you know enough to "pick and choose" which files to replace between mods.
 +
 
 +
<span id="Issue: Aiming - Weapon stays centered after releasing RMB"></span>
 +
 
 +
=== Issue - Aiming - Weapon stays centered after releasing RMB ===
 +
Basically: when you fire your weapon in TPV and press the (default) "Right Mouse Button (RMB)" (switching to FPV "scope" or "iron sights" aiming) and IMMEDIATELY let go of the RMB, the weapon stays centered for a second or so before it goes back to normal.  This DOES NOT happen if you fire and hold RMB/Aim for those 1-2 seconds; it's almost as if the weapon is stuck in it's FPV firing position for a second or so every time you fire.  The camera zooms back out, but nothing else.
 +
 
 +
* Cause: This is a bug in some animations.  It is particularly noticeable with the "plasma rifle".
 +
:* Solution: Try an alternate source for the animation in question, and replace the vanilla ".kf" file.  Search the Nexus on the keyword "animation".  (There is also the mod [http://www.nexusmods.com/newvegas/mods/64339 Asurah Reanimation Pack] which will not get picked up by that keyword search.)  The mod [http://www.nexusmods.com/newvegas/mods/57561 Animation Resources] by '''Fallout2AM''' includes some, as well as a "AnimTool (AnT)" which allows you to invoke an animation after you choose it from a menu, on you or on a target (NPC or Creature) for testing.
 +
 
 +
<span id="Issue: Animation Clipping"></span>
 +
=== Issue - Animation Clipping ===
 +
A common problem is "clipping" of the hand/fingers gripping a weapon while aiming or reloading.  Sometimes this appears as a gap between the hand and the weapon; sometimes as the weapon cutting into the hand.
 +
 
 +
* Cause-1: IF you are using combinations of mesh/texture and animation replacements, or various "post processor" packages such as "ENB", "Reshade/SweetFX", or "NewVegasReloaded/NVGE" then there may be conflicts just as with other mods.
 +
:* Solution-1: Engage in [[# Mod_Conflict_Isolation|Mod Conflict Isolation]] to identify where the conflicts reside.  Identify a consistent, readily determined example of the conflict.  In  general, removing the most sweeping, broadly affecting "overhaul" addition first will be more efficient.  It may even be necessary start from a bare-bones vanilla load order without any enhancements of any kind to determine the issue does not occur without any modifications.  Then, gradually add and test.
 +
 
 +
* Cause-2: It's simply how the game handles weapon animations.  Weapon animation is shared between weapons of the same type (e.g "two handed weapons"). For example, both the "Hunting rifle" and the "Varmint rifle" use the same animation set, based upon the vanilla meshes. Some weapon mesh used by a given mod might be thicker or thinner, resulting in clipping.
 +
:* Solution-2: Not much can be done about it.  As most of the time these are "transient" temporary issues, it's best to just ignore them.  If it really bothers you, then you will have to give up whichever mod is providing the altered mesh causing the clipping. 
 +
:: Note that mods considered purely one thing or another (such as "texture replacers") still might include their own meshes. Every mesh has embedded in it the path to the texture file it uses.  If the mod uses a unique folder structure, then it HAS to have altered the mesh as well in order to find the correct textures.  Case in point: version 2.x of [http://www.nexusmods.com/newvegas/mods/38285 Weapon Retexture Project (WRP)] by '''millenia'''.  Version 1 used a vanilla folder structure; version 2 has a unique one making it incompatible with some other popular mods (e.g. '''WMX''') and animation replacements.  Always check both the general mod description and that of the individual files.
 +
 
 +
<span id="Issue: AuthorityGlasses"></span>
 +
=== Issue - Authority Glasses worn weirdly ===
 +
Symptoms: When worn, the Authority Glasses don't "sit right"; as in dangle off the face incorrectly hanging down the side as if from one ear.
 +
 
 +
* Cause:  Conflict between "[http://www.nexusmods.com/newvegas/mods/51664/? Yukichigai Unofficial Patch - YUP]" and any mod that replaces the mesh for the Authority Glasses.
 +
:* Solution:  Let YUP overwrite those mods (somewhat difficult with just the "load order" as YUP should be loaded early/"low numbered" in the sequence) or resolve the conflict with a "Bashed/Merge Patch" file.  Please see the '[[FNV_General_Mod_Use_Advice#Third_Rule:_The_Rule_of_One Third Rule:|The Rule of One]]' and '[[FNV_General_Mod_Use_Advice#Merge_Patch_File|Merge Patch File]]' sections of the wiki "[[FNV_General_Mod_Use_Advice|FNV General Mod Use Advice]]" article.  When in doubt, create a "Merge Patch" file for your overall "load order" anyway.
 +
 
 +
<span id="Issue: Blood Decal Duration"></span>
 +
 
 +
=== Issue - Blood Decal Duration ===
 +
Adjust how long the "decals" of blood spatter remain on things when they take damage.
 +
* Cause: This is controlled by several settings in the game INI files.  Change in all three files: see the [[FNV General Mod Use Advice#Game INI files|Game INI files]] section for the location and names of each.
 +
:* Solution: The following information is collected from several sources.  Just enter the numeric values given.  The "[def: nn]" notation is the game default value for reference.  The remainder of each entry is informational only and should not be entered.
 +
:: Mod: [http://www.nexusmods.com/newvegas/mods/212/? Enhanced Blood textures(EBT)] by '''dDefinder'''.
 +
:: See also: [http://forum.step-project.com/topic/8963-fallout-new-vegas-default-values-for-all-valid-ini-settings/ Fallout New Vegas Default Values for All Valid INI Settings]
 +
<div style="margin:0px 10px 10px 50px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;">
 +
[Display]<br>
 +
''fDecalLifetime=''[def: 10.0000] ; the lifetime of all decals. The number can be changed to further increase or decrease the duration.  EBT increases this to 800.000.<br>
 +
''iMaxDecalsPerFrame=''[def: 10] ; maximum number of decals (mainly blood splatters on the ground) visible on screen at any time (FalloutPrefs.ini).<br>
 +
''fDecalLOD0=''[def: NA] ; increases the distance that blood decals appear.  EBT adds & sets to 70000.<br>
 +
''fDecalLOD1=''[def: 1000.0000] ; undefined functionality but FNV default setting.<br>
 +
''fDecalLOD2=''[def: 1500.0000] ; undefined functionality but FNV default setting.<br>
 +
''iMaxDecalsPerFrame=''[def: 10]<br>
 +
''iMaxSkinDecalsPerFrame=''[def: 3]<br>
 +
 
 +
[Decals]<br>
 +
''uMaxDecalCount=''[def:100]      ; This variable seems to determine how many decals will remain on screen for longer than a few seconds. It won't prevent multiple decals from being shown, but if you lower the number, additional decals above the value you set for this variable will fade out very quickly (FalloutPrefs.ini).
 +
</div>
 +
 
 +
<span id="Issue: Blood, Gore, Limb Explosions & Dismemberment"></span>
 +
=== Issue - Blood-Gore-Limb Explosions and Dismemberment ===
 +
The Fallout series is known for being "bloody" and "gory" with dismembered limbs, exploding heads, and chunks of viscera ("gore globs") and splashes of blood lying about.  The game does have a generally undocumented setting to turn ALL the blood and gore off, which is apparently enabled by default in the German regional "no gore" version; but no finer control over the chances of such occurring when sufficient damage is applied.
 +
* Cause: This is by design.  The points of dismemberment are defined in the mesh file as "animation nodes", and are called "meat caps".  These "meat caps" are the visible stumps remaining on each end when the limb is dismembered or exploded.  A detached limb can then be further dismembered into "gore chunks".
 +
:* Solution-1: To completely disable all gore and blood effects:
 +
:: Open Fallout "INI" files (located in both the game root folder and the "Users" folder).
 +
:: Add under the "[General]" section of all three:
 +
:: <pre>bDisableALLGore=1</pre>
 +
:: Save the file.
 +
 
 +
:* Solution-2: To adjust the chance of Limb Dismemberment and Explosion in finer detail, the mod  [http://rd.nexusmods.com/newvegas/mods/59147 Ragdolls] by '''MadAce''', under it's '''MCM''' menu has settings affecting:
 +
::* "Limb Explosion chance"
 +
::* "Limb Dismemberment Chance"
 +
::* "Limb Dismemberment Chance"
 +
::* "Explosion Strength"
 +
::* "Projectile Strength"
 +
:: which can be set all the way down to zero percent (pt).  Please note this does not distinguish between the damage inflicted by "projectile" and "energy" weapons.
 +
 
 +
<span id="Issue: BobbingNPCs"></span>
 +
=== Issue - Bobbing NPCs ===
 +
Symptoms: All NPCs start to bob up and down whenever looked at from close range. Zooming in on them causes it from any distance, even with a vanilla game.
 +
 
 +
* Cause: Framerate higher than 60FPS. The more your framerate is above 60 fps, the more likely you'll see this problem.
 +
:* Solution-1a: Make sure that your in-game framerate is capped below 120 FPS. Use some FPS counter within the game to double check if it really is below 120.
 +
:* Solution-1b: There is a trade off between ''player foot dynamic placement'' efficiency and the absence of foot bouncing glitches for NPCs.  It eliminates NPCs bouncing glitches almost entirely, but also makes ''player dynamic foot placement'' work slightly worse.
 +
:: Set these lines in either "FalloutPrefs.ini" or "FalloutCustom.ini" to the following:
 +
<div style="margin:0px 10px 10px 50px; border:1px solid #DAA520; color:#FF9933; background-color:#000000; padding:3px;">
 +
[FootIK]<br>
 +
fOnOffGain=0.01<br>
 +
bFootPlacementOn=0<br>
 +
fPelvisUpDownBias=0<br>
 +
fPelvisOffsetDamping=0<br>
 +
fOriginalGroundHeightMS=0
 +
</div>
 +
:* Solution-1c: Disable ''FootIK'' completely.
 +
<div style="margin:0px 10px 10px 50px; border:1px solid #DAA520; color:#FF9933; background-color:#000000; padding:3px;">
 +
[RagdollAnim]<br>
 +
bFootIK = 0
 +
</div>
 +
 
 +
<span id="Issue: Body Replacer - Big Head / Hair bug"></span>
 +
 
 +
=== Issue - Body Replacer - Big Head or Hair bug ===
 +
When you unpack the BSA's to do modding for Fallout NV, the Actor's grow abnormally large foreheads which make people look half-bald, and make it so hair sticks out of hats, or hats become embedded in the heads.
 +
 
 +
Cause: EGM files don't work outside of BSA archives in '''Fallout New Vegas'''.
 +
: Meaning, you have to have the head / hairs / character files for the mod in a BSA file (named after the mod).  The problem occurs when any of the files (even original vanilla ones) are "loose" outside of a BSA.  It's a quirk of the game engine.
 +
:* Solution: Package the modded loose files into a BSA when done.
 +
:: The rules for naming a BSA are simple: the first significant portion (enough to distinguish it from any other similar but different mod name) must match that of the mod plugin ESP file, and have the ".BSA" extension.  There can be more than one such BSA plugin, but usually this "matching significant portion of the ESP filename" is up to any embedded space (e.g. "Fallout - Textures.bsa").  It must be packaged as a "Bethesda Software Archive" (BSA) using a tool like "[http://www.nexusmods.com/newvegas/mods/64745 BSArch]", and containing the same folder paths as the loose files used by the mod in question.
 +
:: See also the other "Issue: Body Replacer -" entries under 'Solutions to Graphics problems' section in the wiki "[http://wiki.nexusmods.com/index.php/Fallout_NV_Mod_Conflict_Troubleshooting Fallout NV Mod Conflict Troubleshooting]" guide.
 +
 
 +
<span id="Issue: Body Replacer - Custom Body Types"></span>
 +
=== Issue - Body Replacer - Custom Body Types ===
 +
Problems getting various custom body replacements, such as "Type 3" and "Type 6", to work correctly.  (Since most of these are classified as "Adult" mods, you may need to change your Nexus Profile "Content Blocking" setting to access them.)
 +
 
 +
* Cause: Install failures, usually from not understanding what is involved.
 +
:* Solution: This is a general guide to what is involved in replacing the vanilla body of one gender with a "Custom Race" one for the Player Character Only. Mods for NPCs are separate.  There are separate mods for Males and Females or other Custom Races.  Refer to the specific body mod install instructions for specific details appropriate to that mod.  But understanding what is involved will make it easier to understand those options.  For another detailed explanation, see the [http://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice#Body_Replacement_Basics Body Replacement Basics] section of the "FNV General Mod USE Advice" article.
 +
 
 +
:: Replacing the vanilla body 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 (proportions) in some regards to those used for the vanilla body. They are generally going to be found in the Nexus site [http://www.nexusmods.com/newvegas/mods/searchresults/?src_cat=66 New Vegas Models and Textures] category.
 +
 
 +
:: Body replacement only affects the "unclothed" body. "Clothing" and "armor" (collectively: "garments") 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 clothing/armor for body type "B", what you see is type "B".  So the "nude" body type does not appear at all; even the "bare skin" elements are part of the garment.  ALL "garment" mods are based around some body type (assume "vanilla" if not specified).  FNV does not have separate "slots" for different parts of the body: only distinguishing between the head, hands, and the remainder of the body (misleadingly called "upper body slot" as there is no "lower body" nor "legs" slot). Further on the consequences of this below.
 +
 
 +
:: The vanilla body "texture" has underwear included, so it is not removable.  Custom body textures may have both a "nude" option and an "underwear" option texture.  These are "all-or-nothing" choices: everyone is nude underneath their armor and clothing, or everyone wears underwear.  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.  There is now at least one "nude body" texture mod for vanilla meshes: ''Simple Vanilla Nude Body Replacers'' by '''Jokerine''' (linked below under "NPC overhauls").  Toggling "ArchiveInvalidation" off-and-then-on again as with other texture replacements may be necessary.
 +
 
 +
:: As a consequence of these custom meshes, vanilla clothing and armor will have "clipping" issues where 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 clothing and armor that are made specifically for that body type.  Note that armor usually has it's own "body mesh" included, avoiding this clipping.  (This is not true for "accessories" that go on sub-sets of the body: such as gloves, bracers, and shoes.)  This means armor ignores the underlying "body" shape and instead that you can choose among those using the same texture '''UVmapping''' based upon the same base model (i.e. Type 6M, Type 6, Type 4, Type 3M, Type 3F, and Type 3).  As a consequence, your Type 6 naked body can "wear" a Type 3 armor, but will appear to be Type 3 in proportions until it is taken off.
 +
 
 +
:: "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.  (These different bones and weights are also the case with some "Havok" and "Power Armor" mods.)  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) or otherwise appear "weird".  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 clothing and armors, 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.  There are three "universal compatibility skeleton" mods for FNV on '''Nexus''' designed to overcome this compatibility problem:
 +
::* [http://www.nexusmods.com/newvegas/mods/68776 NV Compatibility Skeleton] by '''Kicho666, Xilandro, Fallout2AM'''.  A skeleton with compatibility for the latest mods (such as "Ragdolls", Xilandro's various B42 mods (Head Tracking, Quickthrow, Inertia etc.), and "Titans of the West").
 +
::* [http://www.nexusmods.com/newvegas/mods/45229 Compatability Skeleton - BnB BodyExtender FAFF NVG] by '''Astymma'''.
 +
::* [http://www.nexusmods.com/newvegas/mods/56657 The Skeleton] by '''Deedes'''.
 +
::: Read their descriptions carefully.
 +
 
 +
:: Because the head is separate from the body, that means it too can have custom versions of it's mesh and textures.  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 (though some come very close).  There are "seam concealer" mods that provide necklaces and similar to hide this seam.
 +
 
 +
:: "Face mods" are yet another category subject to preference.  You might want to look at the [http://www.nexusmods.com/newvegas/mods/67268/? Loose Comparison of Face Mods (Document)] PDF which compares 3 female NPCs (Cass, Sunny, and Veronica) among a number of separate mod treatments and combinations to get an idea of their differences.
 +
 
 +
:: Some features, such as scars and tattoos, are part of the texture and not a separate addition.  Others have to use specific [http://geck.bethsoft.com/index.php?title=Race 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.
 +
 
 +
:: FAQs:<br>
 +
:: Q: What are the common male body replacers?  Female ones?<br>
 +
:: A: This is subject to change, but as of this writing these "meshes" are often mentioned and can be found in the "New Vegas: Models and Textures" category unless otherwise indicated.  As they are often in the gated "Adult" section of the site and feature nudity, the links are provided but may not be accessible without changing your site access permissions.  With the full name AND authors you should easily find their descriptions using the "search" feature:
 +
::: Males:
 +
:::* [http://www.nexusmods.com/newvegas/mods/35451 Breezes New Vegas Males] by '''sesom'''.
 +
:::* [https://www.nexusmods.com/newvegas/mods/70160 Improved Vanilla Male Body - Seamless - 4k] by '''zzjay and 7thNighthawk'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/54731 Roberts Male Body FNV] by '''Nivea and Favoredsoul'''.
 +
:::* [https://www.nexusmods.com/newvegas/mods/70530 Robert N - Male Body Replacer] by '''Robert, Nivea, AlienSlof, and Allnarta'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/64001 Roberts and Brawler Body Complementary Resource for FNV and TTW] by '''Good0593''' and '''Nivea''' and '''Favoredsoul''' and '''RocketLombax'''.
 +
::: Females:
 +
:::* [http://www.nexusmods.com/newvegas/mods/67311 Beloved Girls Race Type4 body] by '''pr4ch'''.  (Note the screenshots are taken using ENB.)
 +
:::* [http://www.nexusmods.com/newvegas/mods/34702 BEWARE OF GIRL Type 3 HiRez HiDetailed Replacer] by '''BlackBlossom'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/54438 DIMONIZED TYPE3 female body] by '''dimon99''' (Copied from FO3 section unmodified. Not ported, so clothing portion doesn't work.  See FO3 version for full description.)
 +
:::* [http://www.nexusmods.com/newvegas/mods/40401 Lings Playable Races] by '''Volek'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/34825 Type3 Body and Armor replacer] by '''Exeter'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/50612 Type3 Narrowed Shoulder BerryHD Acup body] by '''ChunchunMARU'''.
 +
:::* [http://www.nexusmods.com/fallout3/mods/14359 Type3 F Body Replacer] by '''Exeter'''.  (FO3 version) Not ported to FNV.
 +
:::* [http://www.nexusmods.com/newvegas/mods/57627 Type3BG] by '''digimonkey'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/44709 Type3M Body Replacer] by '''MAK'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/66903 Type4 Female Body and Armors] by '''unkacc11'''.  No neckseams and much improved arms and upperbody. Complete set of armor and clothing with support for all DLCs, TTW, and Impact.
 +
:::* [http://www.nexusmods.com/newvegas/mods/67017 Berry and Aliceberry Type4 compatible Body] by '''ChunchunMARU'''.  This is a Replacer mod for Type4 Female Body! Slim and breasts smaller than Type4.  And, Type4 head file for Shojo race is also in the optional file.
 +
:::* [http://www.nexusmods.com/fallout3/mods/5326 Type V Female Body and Armor Replacer] by '''Luchaire'''.  ('Dimonized' FO3 version) Not ported to FNV.
 +
:::* [http://www.nexusmods.com/newvegas/mods/65627? Type6 Sexy outfits with nude body (Replacer (T6) and Non-Replacer)] by '''munnibhai'''.  The "replacer" version includes the original Type 6 Body (by '''Necroscope''', now hidden) for the Player character only.
 +
:::* [http://www.nexusmods.com/newvegas/mods/67073 Type6 Nude Body Mod (BNB) Edition3] by '''munnibhai'''.  This edition in the series adds BNB to the body and contains new outfits including denims, sexy frocks and a bonus Pakistani Lehenga.  African Skin tone is working.
 +
:::* [http://www.nexusmods.com/newvegas/mods/67104 Type(6) Sexy Outfits Merged BNB Compatible] by '''munnibhai'''.  Type6 Sexy Outfits Edition 1 & 2 merged into 1 and made BNB compatible.  43 Outfits.
 +
:::* [http://rd.nexusmods.com/newvegas/mods/45162 Type 6 Modification Body NV] (T6M) by '''Izumiko'''.  This is often (incorrectly) called just "Type 6" by some mods.  If it refers to '''Izumiko''''s version, then it means "Type 6M".
 +
:::* [http://www.nexusmods.com/newvegas/mods/66839 Type6-P (T6P) nude body BNB Replacer] by '''munnibhai''' is a more "petite" version of the Type-6 body.
 +
:::* [http://www.nexusmods.com/newvegas/mods/65697 Type C Body Replacer] by '''Cytiene/AusAllerWelt'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/37820 Athletic Female Body] by '''skims'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/47986 Athletic Body Type Bouncing BNB] by '''Tattooedillusions via Skims'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/60731 Female bodybuilder race and companion] by '''Bernt '''.  "Brenda" Race and NCCS companion. Together with a variety of outfits and a pose pack.  Requires [http://www.nexusmods.com/newvegas/mods/38059/? NCCS companion system] and [http://www.nexusmods.com/newvegas/mods/38853/? ACM companion wheel for NCCS].
 +
:::* <del>[http://www.nexusmods.com/newvegas/mods/42569 Muscle Girl Project - NV] by '''zomb_killer and Tigersan'''.</del>  (No longer available.  See "Female bodybuilder race and companion" by '''Bernt ''' instead.)
 +
:::* [http://www.nexusmods.com/newvegas/mods/47277 SKINNY 6 Body BNB] by '''tattooedillusions via Humannature66'''
 +
:::* [http://www.nexusmods.com/newvegas/mods/67079 Wasteland Gals - Body Textures and Playable Races Type 3 4 6] is a retexture of type 3, 4 and 6 female bodies and faces that makes raiders, ghouls and old people playable.
 +
::: NPC overhauls:
 +
:::* [http://www.nexusmods.com/newvegas/mods/64014 Simple Vanilla Nude Body Replacers] by '''Jokerine'''.
 +
::::* [http://jokerineborealis.tumblr.com/tagged/fnv Jokerine's Website with additional resources including apparel mod patches for vanilla bodies] such as "Spice of Life - Variety Armor and Clothing" for Vanilla/Default Body.
 +
:::* [http://www.nexusmods.com/newvegas/mods/39325 NVCE - New Vegas Character Expansions] by '''Machienzo'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/54460 Fallout Character Overhaul] by '''Drumber'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/39218 Fallout New Vegas Redesigned 2] by '''Dracomies'''.
 +
:::* [http://www.nexusmods.com/newvegas/mods/56312 Fallout New Vegas Redesigned 3] by '''Dracomies and Weijiesen'''.
 +
 
 +
:: Q: What is the difference between Body Type 3 and Body Type 6M, etc?<br>
 +
:: A: It's a matter of personal preference in "shape": breast, hip and/or butt size.  All are potentially weighted differently ("bounce" effect).  Type 6 has an "apple bottom", Type 3 are thinner "waifs".  Apparently T3 originated in Fallout 3 along with Type V; Type 6 (another variant of Type 3) by '''Necroscope''' came along when NV came out, but has since been hidden by the author.  Type 6M (by '''Izumiko''') is a "rounder" modification of the basic Type 6 model.  Why do they have numbers? Your guess is as good as any. Any that have T3 in the name are derivatives of the original Dimonized Type 3 set from Fallout 3 (variants: Alice, Berry, Cali = A Cup, B Cup, C Cup).
 +
:::* HD versions have more polygons, which place a heavier demand on the video memory.
 +
:::* Hentai versions have puffy nipples and are based on T3F.
 +
:::* It's best to use clothing and armor specific to the particular body type or they won't render properly.  And it's not simple to "fix".
 +
 
 +
:: Q: Can Body Type6M (or T6, Type V/T5, T3BG, or T3M) can be used with textures for Body Type3?<br>
 +
:: A: Yes, if they have the same '''UVmapping''' (part of the texture "*.dds" file).  However, the dimensions of the armor will not change from the Type3 to the others.  The armor contains it's own body mesh.  (See the next question.)  The mod [http://www.nexusmods.com/newvegas/mods/67079 Wasteland Gals - Body Textures and Playable Races Type 3 4 6] is a retexture of type 3, 4 and 6 female bodies and faces that makes raiders, ghouls and old people playable.  (Note the caveats near the bottom of the description carefully.)
 +
 
 +
:: Q: What about clothing and armor compatibility between body types?<br>
 +
:: A: Compatibility is a problematic term to use in this case.  Generally, the only thing that is needed for the body types and associated armors to work together is for them to share the same '''UVmap'''.  Any mesh that shares a '''UVmap''' can also share textures.  And generally the ones that are variations on Type3 do.  There are more choices for Type3 bodies than any others.  Remember: the "garment" completely replaces the body supposedly underneath it.  You are seeing the shape of the garment mesh, not that of the naked body.
 +
::: "BnB" is a little more complicated.  Basically, in order to use BnB you have to have the skeleton.  So you can't just take an individual BnB outfit and have it work unless you've downloaded the skeleton from the main file.  The reason is because the outfit will have two reference bones (left breast and right breast) that aren't in the normal skeleton, and that causes glitches or crashes.  But you can have the BnB stuff installed and still use other non-bounce outfits, because those outfits don't need the extra bones.
 +
::: Now, if your idea of compatibility is for your character's body to stay the same size no matter the outfits, then you're generally out of luck.  For the time you're wearing an outfit, your body will be that size, for most things.  This is because virtually all major outfits include their own body meshes as part of the outfit.  The exception are accessory-type items like individual shirts or shorts or whatever.  Those are usually fitted to a particular body that is NOT included in the mesh file, and in this case if you're not using the right body then the clothing will clip badly.  As always, read the documentation carefully.
 +
::: However, with that said, there was a tool called [http://kgtools.wordpress.com/clothing-converter/ KGTools Clothing Converter].  This would automatically convert Armor, Clothing, or Equipment from one body style to another!  Unfortunately the KGTools web site containing the downloads is no longer accessible.  Use the links [http://www.loverslab.com/topic/27557-new-clothing-body-style-converter-beta-v089f-10-26-2014/ on this site (adults 18+ only)] instead.  The documentation is still available on the first link provided.
 +
 
 +
:: Q: Can I use a different body type for my companions (and NPCs) than for my character?<br>
 +
:: A: Yes, as long as they have their own ''male/femaleupperbody.nif'' file.
 +
 
 +
: 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.
 +
 
 +
<span id="Issue: Body Replacer - Custom Hair, Eyes, Heads, and/or Races"></span>
 +
 
 +
=== Issue - Body Replacer - Custom Hair-Eyes-Heads and-or Races ===
 +
Problems getting custom heads or head elements (e.g. Hair and Eyes) to work correctly with a specific body replacement mod.
 +
 
 +
* Cause-1: As pointed out in [[#Issue:_Body_Replacer_-_Custom_Body_Types|Issue: Body Replacer - Custom Body Types]] you can't just assume every mod affecting the head will work with every other, or even with the body mod you have chosen.  They are not "mix-n-match" and you can only use one such mod at a time for each race.  For example, if it says it's for "Head03", then it won't work with the vanilla game heads.  The popular mod [http://www.nexusmods.com/newvegas/mods/44312/? Mojave Delight for Type3] by '''Glosshouse''' is for '''Type3''' bodies only, while [http://www.nexusmods.com/newvegas/mods/35878/? Beauty Pack PLUS -Project Mikoto- Hair - Eyes - Presets] by '''Matteius''' is not intended to work with any [[custom race]] body mods like '''Type3'''.  Read the description and installation instructions carefully to determine what the mod is designed to work with.  Most known issues are noted either on the description page or under the "comments" page.  Note that some require MANUAL installation.
 +
 
 +
: The following is taken from the description on the "Mojave Delight for Type3" download page:
 +
<blockquote>
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 0px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">
 +
There is a long standing issue with custom races, hair and eye incompatibility causing CTD. Be forewarned that you WILL experience CTD when using the Character Generator IF you do this:<br>
 +
1) Put on a Custom Hair (that means ANY of the Cool Hairs included in the mod)<br>
 +
2) Then Put on a Custom Eye Color (THAT means ANY of the custom eyes included in this mod)<br>
 +
<br>
 +
YOUR GAME WILL CRASH - THERE IS NO SOLUTION FOR THIS AT THIS TIME THAT WE ARE AWARE OF.<br>
 +
<br>
 +
Therefore, in order to change eye colors without CTD you MUST:<br>
 +
1) PUT ON A VANILLA HAIR STYLE FIRST then<br>
 +
2) change eye color.<br>
 +
<br>
 +
As long as you do this in this order your game will NOT crash.</div>
 +
</blockquote>
 +
: Once you have successfully changed eye color, then you can safely change to your custom hair style.  But any time later that you wish to change any of these features you must repeat the process: vanilla hair, custom eyes, custom hair.
 +
:* Solution-1: Hair and Eyes are "slots" on the head.  This mean such mods are either replacement textures for the head model (either vanilla or some custom head), or have to edit the mesh and texture files to point to the mod's elements using the GECK.  The solution depends upon the mod.
 +
::* [http://www.nexusmods.com/newvegas/mods/62744 Megaton Hairs - Vegas Edition] by '''zzjay''' is for the vanilla game races only, but includes a tutorial on how to add it MANUALLY to your custom race.
 +
::* [http://www.nexusmods.com/newvegas/mods/35878/? Beauty Pack PLUS -Project Mikoto- Hair - Eyes - Presets] by '''Matteius'''
 +
::* [http://forums.nexusmods.com/index.php?/topic/5184015-guide-replacing-vanilla-hair-with-modded-hair/ GUIDE: Replacing Vanilla Hair with Modded Hair] Forum Thread outlines the basic procedure using the GECK.
 +
::* [http://www.nexusmods.com/newvegas/mods/61538/? Hairs - Eyes - Races Auto - Patcher] mod by '''Fallout 2AM''' attempts to automate this "patching" process for custom races.
 +
::* [http://www.nexusmods.com/newvegas/mods/68016/? Hair Patcher Two] mod by '''Fallout 2AM''' adds a few differences to '''Hairs - Eyes - Races Auto - Patcher''' (by the same author).
 +
::* [http://www.moddb.com/mods/lings-coiffure-nv/downloads/lings-coiffure-nv-v42 Lings Coiffure NV] by '''earache42'''.
 +
::* [http://www.nexusmods.com/newvegas/mods/44312/? Mojave Delight for Type3] by '''Glosshouse'''
 +
 
 +
* Cause-2: Unsuccessfully trying to switch between race or hair mods.  The character becoming invisible, getting stuck in the ground and unable to even use the console to toggle the "clipping" command (''TCL''), or unable to access the Pip-boy, usually happens if you uninstall/disable the race that your character is set to.  Trying to use the console command "''ShowRaceMenu''" here will probably crash the game.
 +
:* Solution-2: Instead reinstall and enable whatever mod contains the race you were playing, then use the console ''ShowRaceMenu'' command to switch to something else vanilla before removing it again.  Then perform a "Clean Save" as laid out in the 'Clean Saves' section of the wiki "FNV General Mod Use Advice" article before attempting to install a replacement.
 +
* A guide on custom race creation that covers adding hairs to races is: [http://www.nexusmods.com/newvegas/images/102834 How to Create a Custom Race] by '''jim_uk''' in the "Images" section of the Nexus.  There is also a [http://www.nexusmods.com/newvegas/mods/62261/? How to Create a Custom Race PDF] version in the Mods section.
 +
 
 +
<span id="Issue: Body Replacer - Custom Race skin mismatch"></span>
 +
 
 +
=== Issue - Body Replacer - Custom Race skin mismatch ===
 +
This is most commonly seen as a difference between the skin color of the head and the body.  This is a "texture" problem.  Adjusting the tone sliders in the racemenu does not change anything.
 +
* Cause: This generally occurs when the plugin is an ESP rather than an ESM file.
 +
:* Solution: Note that the Player and NPCs are distinct and what is a problem for one may not be for the other.
 +
:: A custom race defined in an ESP will work properly for the player, even though the head and body will be mismatched for NPCs.
 +
:: Defining the NPC in an ESM is the only solution that works for everyone.
 +
:: If you are using this on an NPC, make sure the NPC is defined in an ESM and not in an ESP. There are some tweaks to your INI files that can kinda fix it for ESP files, but they don't work for everyone.
 +
::* In both the "Fallout.INI" and "FalloutPrefs.INI" files in the "C:\Users\<AccountName>\Documents\My Games\FalloutNV" folder, and the "Fallout_default.INI" in the game root folder, set:
 +
<div name="Simulated code box" class="boilerplate metadata" id="Warning Notice"
 +
style="margin:0px 10px 10px 70px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
/* Remove the next four 'white-space' lines to restore default white-space processing. */
 +
white-space: pre-wrap;      /* css-3 */
 +
white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
 +
white-space: -pre-wrap;      /* Opera 4-6 */
 +
white-space: -o-pre-wrap;    /* Opera 7+ */
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">bLoadFaceGenHeadEGTFiles=1</div>
 +
::* Toggling "ArchiveInvalidation" sometimes works, as does repeatedly reloading the save game again and toggling it until the head and body match skin tones.
 +
 
 +
:: It is also possible that the shader type and shader flags are set wrong in the race's body mesh. Skin parts need the shader type to be ''SHADER_SKIN'', and the ''SF_Specular'', ''SF_Skinned'', ''SF_FaceGen'', ''SF_Remappable_Textures'', and ''SF_ZBuffer_Test'' flags need to be set. You can check and modify these using '''NifSkope'''. If these are not set properly, then the custom race body and skin won't work properly for both NPCs and for the player, if the player uses that race.
 +
 
 +
:: Another thing to check is that the skin textures are all there and are all named properly. If the body texture for the race is named '''UpperBody.dds''', then the normal map needs to be named '''UpperBody_n.dds''' and the skin needs to be '''UpperBody_sk.dds''', and all of those files need to be in the same folder. You only define the base texture ('''UpperBody.dds''') for the race in the '''GECK''''. The '''GECK''' just assumes that the other files will be in the same place and will have the same name.
 +
 
 +
:: And finally, keep in mind that whatever '''clothes''' or '''armor''' you use will have body parts defined, and those skin textures will show instead of whatever body you have defined in the '''GECK'''. In other words, if your character is wearing overalls and bare arms are visible, those bare arms are part of the overalls mesh and are not the bare arms from the race's body mesh. If the clothing wasn't created especially for your custom race, the bare skin parts of the outfits might not match the rest of your custom body type.
 +
 
 +
:: See also the following in the wiki [[Getting_started_creating_mods_using_GECK|Getting started creating mods using GECK]] article:
 +
::* [[#Tip-ESMOnly|TIP: When can you use an ESM only mod?]]  This contains the "rules" of making an ESM.
 +
::* [[#Tip-CustomRaceFaces | TIP: Custom Race & Faces.]]
 +
::* [[#Tip-CustomSkinTextures | TIP: Custom Race & Skin Textures.]]
 +
 
 +
<span id="Issue: Body Replacer - Default/Vanilla"></span>
 +
=== Issue - Body Replacer - Default ''aka Vanilla'' ===
 +
No matter your opinion of the matter, one of the most common reasons for installing a "body replacer" is to enable a "nude body" when clothing and armor are removed.  (Since these are classified as "Adult" mods, you may need to change your Nexus Profile "Content Blocking" setting to access them.)  Some would prefer to not have to get into the complexities of resorting to "custom races" to get this feature.
 +
 
 +
* Cause: The provided default (vanilla) bodies in the game have "underwear" as an integral part of the body texture.  This cannot be "removed" along with other clothing or armor.  There are some mods which provide alternative "underwear", but these are also integrated into the texture.
 +
 
 +
:* Solution: The mod "[https://www.nexusmods.com/newvegas/mods/64014 Simple Vanilla Nude Body Replacers] by '''Ghostwalker71''' and '''Jokerine''' is a simple mesh and texture replacer that gives the default bodies anatomically correct appendages.  They are the same resolution (1024x1024) as the vanilla "race" files they replace.
 +
 
 +
:* Related:
 +
::* [http://www.nexusmods.com/newvegas/mods/40724/? DIMONIZED presets for Vanilla races for FNV] by '''dimon99'''.  Female FaceGen presets only.
 +
::* [http://www.nexusmods.com/newvegas/mods/55174 zzjay's body and face textures workshop - Type 3 and 6] by '''zzjay'''.  Includes optional "face texture" files for vanilla "race" heads as well as Type 3 and Type 6 races.
 +
::* [https://www.nexusmods.com/newvegas/mods/70160 Improved Vanilla Male Body - Seamless - 4k] by '''zzjay''' and '''7thNighthawk'''.  '''High poly''', improved and SEAMLESS version of the male body.  Compatible with VANILLA outfits and comes with actual feet instead of blocks, thanks to Robert's.  Underwear, nude and "erect" versions.
 +
 
 +
<span id="Issue: Body Replacer - FCO ("Fallout Character Overhaul") not working or conflicting"></span>
 +
 
 +
=== Issue - Body Replacer - Fallout Character Overhaul ''aka FCO'' not working or conflicting ===
 +
* Cause-1: Usually the problem is not understanding or following the installation instructions.
 +
: Note that FCO is a "high resolution" texture replacement of characters and NPCs.  These will place additional demands upon your video system.  Not all older systems will be able to handle the challenge.
 +
: The extensive [http://forums.nexusmods.com/index.php?showtopic=1257503 FCO "comments" forum thread] on the subject has the answers to pretty much every conceivable question not answered here.  Use the forum search function.
 +
:* Solution-1: Make sure you have complied with the following requirements:
 +
::* Install the latest version of [http://nvse.silverlock.org/ NVSE] (original version from the Silverlock site has been at 5.1b4 for many years.  The current version known as "xNVSE" from [https://github.com/xNVSE/NVSE GitHub] is in version 6.x).
 +
::* Install [http://www.nexusmods.com/newvegas/mods/57174/? User Interface Organizer] (UIO).
 +
::* Have the official "Old World Blues (OWB)" DLC installed and active.
 +
::* Use one of the mod managers recommended by the author, or understand enough to be able to manually install it yourself.  If you can't or have to make a choice then use of [http://www.nexusmods.com/newvegas/mods/54991/ Fallout Mod Manager - Forked (FOMM-Forked)] is recommended as FCO has an install wizard written for it.
 +
::* Only install optional components of FCO you actually need.  When in doubt, don't.  You can add them later.
 +
::* Toggle your "ArchiveInvalidation" off-and-on again after installing FCO, as it is replacing texture files.
 +
::* Start a new game either upon installing or uninstalling FCO.  The changes it makes to characters are such the effects upon a game in progress are not supported.
 +
 
 +
* Cause-2: "Fallout Character Overhaul" (FCO) v3.01 has some bugs that can make it unplayable if you don't understand how to correct them yourself.
 +
:* Solution-2a: The author recommends the authorized patch [http://www.nexusmods.com/newvegas/mods/61357/? FCO Bugfixes] by Lunarion Silver to correct these issues.
 +
:* Solution-2b: [http://www.nexusmods.com/newvegas/mods/64012/? Fallout Character Overhaul - Pink Hands Fix] by Vainlash.
 +
:* Solution-2c: Other mods may also have their own patches for FCO.  Be sure to check the download pages for any mods already installed for "compatibility patches" for FCO.  Be careful as to which version of FCO each patch is designed to work with.
 +
 
 +
<span id="Issue: Body Replacer - FCO or FNV Redesigned3 Characters have pink faces or clean bodies with dirty faces"></span>
 +
 
 +
=== Issue - Body Replacer - FCO or FNV Redesigned3 Characters have pink faces or clean bodies with dirty faces ===
 +
* Cause: While FCO and FNV Redesigned3 (FNVR3) can work together, there are often difficulties such as pink/magenta faces or fiends/raiders who normally are "dirty" looking suddenly having "clean" bodies with dirty faces depending upon the options chosen for each mod.
 +
:* Solution: While the FNVR3 recommendation is to install it after FCO, the proper solution is a "compatibility patch file" between the two mods.  Finally there is one specifically to address this issue.  Make sure you have all patch files provided by either mod installed first.  Then install the mod [http://www.nexusmods.com/newvegas/mods/63230/? Fallout Character Overhaul Pink Faces fix] by '''Fheese'''.  See the comments for additional information.
 +
 
 +
<span id="Issue: Body Replacer - FCO or FNV Redesigned3 Eyes rolled to the side"></span>
 +
=== Issue - Body Replacer - FCO or FNV Redesigned3 Eyes rolled to the side ===
 +
Commonly seen with [http://www.nexusmods.com/newvegas/mods/54460/?tab=2&navtag=http%3A%2F%2Fwww.nexusmods.com%2Fnewvegas%2Fajax%2Fmodfiles%2F%3Fid%3D54460&pUp=1 Fallout Character Overhaul (FCO)] (designed to remodel NPC faces) in combination with various other character mods and mods that affect appearance, especially eyes.  This often is related to attempts to use both FCO and "Fallout New Vegas Redesigned" (FNVR; similar goal) in combination.
 +
 
 +
* Cause-1: Mod conflict with FCO.  Note the older version (v2.3.1) is available on the same download page under "Old Versions".
 +
:* Solution-1: The current version of FCO is v3.01, which has new eye textures.
 +
 
 +
* Cause-2: According to the author of all FNVR versions, with FNVR3 the correct approach in conjunction with FCO3 is to use one or the other.  'Although FCO will "technically" work with New Vegas Redesigned 3, it's best not to. It's best to use one or the other. But not both. This makes it so that you will get New Vegas Redesigned 3's faces instead of the ones in FCO and it leaves the characters I left alone (ie. Lt. Monroe), etc. alone.'  A more detailed expanaition can be found in [https://forums.nexusmods.com/index.php?/topic/1876875-new-vegas-redesigned-3/page-96#entry16892164 the FNVR3 forum thread].
 +
: Note there are separate mod download pages for [http://www.nexusmods.com/newvegas/mods/39218/? FNV Redesigned 2 (FNVR2)] and [http://www.nexusmods.com/newvegas/mods/56312/? FNV Redesigned 3 (FNVR3)].
 +
 
 +
:* Solutions-2: As FCO3 does not work well with "Fallout New Vegas Redesigned" (FNVR), despite the author's advice people have had some success (with the same caveats as listed in the post above) using FCO2 instead of FCO3 in combination with FNVR2.  Any one of the following may also be required to resolve the "eye roll" problem.
 +
::* [http://www.nexusmods.com/newvegas/mods/37537/? Hi-Res Eyes Replacer by Zenl] for FCO2.
 +
::* Try reinstalling and not using the "child eye fix".
 +
::* Do you use a Bashed Patch and tag "FCOMaster.esm" with "Eyes"?
 +
::* Possible conflict with another mod that affects eyes, such as "Beauty Pack PLUS -Project Mikoto- Hair - Eyes - Presets by Matteius" or various "Project Mikoto for <specific companion>" mods.
 +
 
 +
<span id="Issue: Body Replacer - FNV Redesigned 3 (FNVR3) and Qwinn's Refined FNV Redesigned 3 (QRNVR3)"></span>
 +
=== Issue - Body Replacer - FNV Redesigned 3 ''aka FNVR3'' and Qwinns Refined FNV Redesigned 3 ''aka QRNVR3'' ===
 +
'''Dracomie''''s "Fallout New Vegas Redesigned 3 (FNVR3)" mod is often combined with '''Drumber''''s "Fallout Character Overhaul (FCO)" mod.  This can be done successfully, but requires close adherence to the '''FNVR3''' install instructions.  Even so, many people have had problems with crashes and performance in heavily modded games.
 +
 
 +
* Cause: The mod has been in production since '''FNV''' was released in 2010, and it's never had a thorough cleaning.  Over the near-decade that '''Dracomies''' has spent working on it, the '''GECK''' added tons of wild edits (it does that), and there were even some obsolete values from before the '''Fallout Official Patches''' were applied back in 2010/2011 still lurking in the plugins.
 +
: In addition, '''FNVR3''' relied on both an ESM and an ESP plugin.  The main reason for the ESP is that when "NPC Actor" records are stored only in an ESM, you can get visual glitches such as what some call "whiteface", generally intense bright discoloration.  '''FNVR3''' also suggests setting ''bLoadFaceGenHeadEGTFiles=1'' in the various INI files to further help with this problem, but that setting is an intense resource hog (it generates textures for every character on the fly while in game), which is a lot to ask of your modded setup on what is already a fairly unstable engine.  There is a better way to resolve this though, using the "Export Face Textures" feature in the '''GECK''', eliminating the need for an ESP file.
 +
 
 +
:* Solution: The mod [http://www.nexusmods.com/newvegas/mods/65865 Qwinn's Refined FNV Redesigned 3 (QRNVR3)] by '''Qwinn''' is an authorized overhaul of FNVR3 to cleanup all the old issues.  The mod is currently a "beta test" of the cleanup which, if successful, will be rolled into the official '''FNVR3''' release.  It is applied as a "patch" to an existing '''FCO+FNVR3''' installation, and takes care of the question about disabling the '''FCO''' ESM file by replacing it with an empty "dummy" version.
 +
:: Qwinn has authored two articles to supplement QRNVR3:
 +
::* [http://www.nexusmods.com/newvegas/articles/55232 Complete NVR3 Installation Instructions] This should help every NVSR3 user, even if they don't use Qwinn's mod.
 +
::* [http://www.nexusmods.com/newvegas/articles/55233 How to Export NPC Face Textures for ESMs]
 +
 
 +
<span id="Issue: Body Replacer - In-game doesn't look quite like the author's images"></span>
 +
=== Issue - Body Replacer - In-game does not look quite like the authors images ===
 +
* Cause: Mod authors usually choose 3rd Person "poses" available from other mods to show off their results.  Those poses accentuate the figure in a way that the normal in-game animation does not.  Also, the game has a horrible "fisheye lens" effect with the default of 75 or higher "Field of View" (FoV).  The problem lies with the way the game is displaying the image. For screenshots modders and imageshare users tend to greatly reduce the FoV to correct the problem, sometimes going as low as 30 or even 20.  The game is unplayable with the FoV this low; but it makes for better character screenshots.
 +
:* Solution: Ignore it, or play around with the FoV using a mod such as [http://www.nexusmods.com/newvegas/mods/55085 FOV Slider].  However, note there are several different FoV settings and they have some impact upon each other.  The mod [http://www.nexusmods.com/newvegas/mods/36773 Further 3rd Person Camera] for normal game play may also help.
 +
 
 +
<span id="Issue: Body Replacer - Installing "Beware of Girl" (BoG) FOMOD with "Mod Organizer" (MO)"></span>
 +
 
 +
=== Issue - Body Replacer - Installing '''Beware of Girl''' ''aka BoG'' FOMOD with '''Mod Organizer''' ''aka MO'' ===
 +
Many people have had problems getting this to install.  The following needs to be understood.
 +
 
 +
* There is more than just the body to consider when replacing appearance.  Please see the [[#Issue:_Body_Replacer_-_Custom_Body_Types|Issue: Body Replacer - Custom Body Types]] section of this article.
 +
* BoG is a high resolution ''texture'' FOR Type3 bodies, not vanilla bodies.
 +
* BoG is not itself a "body replacer" mesh.
 +
* BoG is designed for Type3 bodies, NOT vanilla bodies.  (Yes, this is almost the same thing as the first point, but it bears repeating.)
 +
* If you only install this BoG ''texture'' replacer on vanilla bodies, there will be ugly underwear seams on a naked body. Like two textures/meshes are conflicting.
 +
 
 +
* To use this body mod (BoG), you should install a Type 3 Body & Armor ''mesh''  Replacer.  An example would be [http://www.nexusmods.com/newvegas/mods/34825/? Type3 Body and Armor replacer] by '''Exeter'''.  It is not the only one.
 +
 +
# Download & Install your chosen "Type3 body and armor replacer" main file and their respective updates/patches.
 +
#: Remember to '''Merge''' instead of "replace" them when installing.
 +
# Download & Install "Type 3 Armors" for the DLC's and their respective updates/patches in this order if applicable.  Examples by '''Exeter''':
 +
## [http://www.nexusmods.com/newvegas/mods/40595/? Dead Money Type3 Outfits]
 +
## [http://www.nexusmods.com/newvegas/mods/41884/? Honest Hearts Type3 Tribal Armors]
 +
## [http://www.nexusmods.com/newvegas/mods/41884/? Old World Blues Armors for Type3]
 +
## [http://www.nexusmods.com/newvegas/mods/44034/? Lonesome Road Armors for Type3]
 +
#: Remember to '''Merge''' updates/patches, not "replace".
 +
# Download the [http://www.nexusmods.com/newvegas/mods/34702/? "Beware of Girl Type 3 HiRez HiDetailed Replacer] (BoG) FOMOD.
 +
# Double click the "BOG Body Replacer FOMOD" from your downloads. Click Next.
 +
# Check "I have installed Invalidation myself and it works perfectly."
 +
# Click through the FOMOD installation and choose your options. Click Install.
 +
# After install, it will give you errors like these:
 +
#:: Unable to install default meshes.
 +
#:: Unable to install (Selected) Body Mesh.
 +
#:: Unable to install default textures.
 +
#:: Unable to install textures for (Selected private parts).
 +
#:: Unable to install (Selected Raider) textures.
 +
#:: Unable to install Sleepwear meshes.
 +
#:: Unable to install default textures for Sleepwear.
 +
#:: Unable to install (Selected) texture for Sleepwear.
 +
#: Just click "OK", ignoring them.
 +
# Activate the plugin (check marking it).
 +
# Post install:
 +
## Go to profiles -- > click "Profile Name" -- > uncheck 'Automatic archive invalidation' .
 +
## Close and reopen profiles.
 +
## Now go back to "Profile Name" -----> recheck 'Automatic archive invalidation'. Close.
 +
# Verify the Install Order (on the left MO pane):
 +
## Type3 Body and Armor replacer
 +
## Dead Money Type3 Outfits
 +
## Type 3 Honest Heaart Tribal Armors
 +
## Old world Blues Armors for Type 3
 +
## Lonesome Road Armors for Type 3
 +
## BEWARE OF GIRL Type 3 HiRez HiDetailed replacer
 +
#: Notice how BoG is last, so it overwrites Type3 Body and Armor replacer.
 +
: You should now see the BoG textures when you launch the game.
 +
 
 +
<span id="Issue: Body Replacer - Type 6M?"></span>
 +
 
 +
=== Issue - Body Replacer - Type 6M ===
 +
Problems getting this body replacer to work correctly.
 +
 
 +
* Cause: You need, in addition to a Type 6 body replacer, the correct body ''texture'' and "clothing and armor" mods.  Such mods usually need to be installed MANUALLY.  Read their documentation carefully.
 +
:* Solution: Type 6 bodies are based upon Type 3 bodies.  This makes many Type 3 based mods compatible with Type 6.  (An "M" suffix just means it is slightly modified from the base Type body in some dimension.  This is usually not enough to make it sufficiently different to cause problems.)  Keep in mind the ''meshes'' are separate from the ''textures'', but the ''meshes'' contain the path to the ''texture'' files they use.  Common choices that work are:
 +
::* [http://www.nexusmods.com/newvegas/mods/34702/? BEWARE OF GIRL Type 3 HiRez HiDetailed Replacer] by '''BlackBlossom'''.  Note that SOME FO3 body textures MAY generally work as well but must MANUALLY install only the texture files.
 +
::* [http://www.nexusmods.com/newvegas/mods/54438/? DIMONIZED TYPE3 female body] by '''dimon99'''. Straight copy from FO3 (not ported).  Use textures only; as a "lower" resolution alternative to other body texture replacements.
 +
::* [http://www.nexusmods.com/newvegas/mods/45505/? T6M Equipment Replacer NV] by '''Izumiko'''. Type 6M Clothing and Armor.
 +
:: Don't forget to toggle "ArchiveInvalidation" off-and-then-on again after installing new textures.
 +
 
 +
<span id="Issue: BrokenHitIndicator"></span>
 +
=== Issue - Broken Square/Hit Indicator ===
 +
Basically every time you get shot or hit, a very broken square pops up in the direct middle of the screen with no idea what exactly is causing it.
 +
 
 +
* Cause: According to the author "Just Mods: The Hit Indicator" textures from [http://www.nexusmods.com/newvegas/mods/66666 Just Mods Assorted] (2.6d) only support high texture size.
 +
:* Solution: Go to "settings" [SIC] and change your texture size to "High".
 +
:: NOTE: The comments page indicates that some individual "Just" mod components work fine when installed separately; but not when installed as part of the umbrella "Just Assorted" package.  YMMV.
 +
 
 +
<span id="Issue: Character is suddenly invisible in both 1st and 3rd person views"></span>
 +
 
 +
===Issue - Character is suddenly invisible in both 1st and 3rd person views===
 +
Upon opening a save, the player character is suddenly invisible except for their shadow.  NPCs act like the character is present.  Loading an earlier save doesn't have the problem.
 +
 
 +
* Cause: Unknown, but might be related to use of the game "Auto-Save" feature.
 +
 
 +
:* Solution:  In the game console (default toggle key "~") enter the following commands (where "14" is the [http://fallout.wikia.com/wiki/Fallout:_New_Vegas_characters RefID of the player]):
 +
::<pre>
 +
::: prid 14
 +
::: enable
 +
</pre>
 +
:: and close the console.
 +
 
 +
<span id="Issue-WonkyTextures"></span>
 +
=== Issue - Chinese Assault Rifle Textures are '''''wonky''''' ===
 +
: Thanks to '''XP47JSuperbolt''' of the Nexus Fallout "Mod Troubleshooting" forum for the basis of the following:
 +
* Cause: "Project Nevada" appears to cause a texture problem with the "Chinese Assault Rifle".
 +
:* Solution: Strangely, installing one of the [http://www.nexusmods.com/newvegas/mods/64339?tab=files Asurah Reanimation Pack] "Iron Sight Fix" files resolves the conflict.
 +
 
 +
<span id="Issue: Disable Map Markers?"></span>
 +
 
 +
===Issue - Disable Map Markers===
 +
Desire to remove visible map markers in a mod that appear before the site has actually been visited.
 +
* Cause: The map marker in '''GECK''' (an "M" in a box with a large circle around an area in the Render window) has been flagged as "visible".
 +
:* Solution-1: This is much easier with [http://www.nexusmods.com/newvegas/mods/34703/? FNVedit] if you apply a filter to only show "map markers".
 +
::* Start '''FNVEdit''' and load your current load order (selected by default).
 +
::* When it's done loading, right-click somewhere in the left panel and select "Apply Filter".
 +
::* In the "Filter" dialog, check the option titled "Base Record EditorID contains" and in the field below it type "MapMarker".
 +
::* Confirm by pressing "Filter" and wait for a minute or two while the program is working.
 +
::* Find the map marker you want to disable.
 +
::* Find the "Record Flags" sub-record (in the right panel, almost at the top). Right-click the sub-record and select "Edit".
 +
::* At this point you may be introduced to a warning. Accept it.
 +
::* When the "Edit Value" dialog pops up, check the "Initially disabled" option and press "OK".
 +
::: The sub-record is now shown with a bold font, indicating that it has been modified.
 +
:: If the map marker is in "FalloutNV.esm" or one of the official DLC, you need to save your change as an "override" in a '''new plugin'''. It may also be prudent to avoid modifying mod plugin files directly unless you fully grasp the consequences of the changes you're making. Saving your change to a '''new plugin''' makes it easy to revert.
 +
::* Right-click the record and select "Copy as override into...".
 +
::* In the dialog that opens, select "<new file>" and enter a name for your new plugin.
 +
::: Selecting the record will now also list the override from your new plugin in the right panel.
 +
::* Proceed from step 6 (Find the "Record Flags" sub-record ...) in the previous set of instructions, but apply them to the record in your new plugin.
 +
::* When you're all done, close the '''FNVEdit''' program. You will see a list of all the plugins that has been modified in your current session. If a plugin is listed that you did not intentionally modify, deselect it. Press OK to save your changes and close '''FNVEdit'''.
 +
 
 +
:* Solution-2: Click on the marker in '''GECK''' to bring up it's "reference" interface window (see [http://geck.bethsoft.com/index.php?title=Reference GECK: Reference] page), and then check it as "initially disabled" so the marker will only appear when you actually discover the location.  Then click the "OK" button, and save the file.
 +
 
 +
:* Solution-3: If you wish to unset the "visible" flag (in the "Marker Data" section of the [http://geck.bethsoft.com/index.php?title=Reference GECK: Reference] window) instead of disabling the marker, that can be done in "FNAM - Flags" (near where the name and location type is also defined.)  If the visible flag is set, it'll be listed below and you can right-click the entry and select "remove" to unset it.
 +
 
 +
<span id="Issue: Distant terrain/LOD flickers rapidly"></span>
 +
 
 +
=== Issue - Distant terrain or LOD flickers rapidly ===
 +
This problem seems to occur more frequently with high-end systems, but across all sorts of platforms and video cards.
 +
* Cause: Known as "Z-fighting" or "stitching", this is a complex problem in 3D rendering where two or more "primatives" such as "layers" have similar or identical values in the "z-buffer", so they essentially occupy the same space.  The result is the pixels from each layer "fight" to be the one displayed on screen, especially when the point of view changes.  This causes a flickering, noisy display of first one then another color pixel.  See the "[https://en.wikipedia.org/wiki/Z-fighting Z-fighting]" article from Wikipedia for the full technical description.
 +
 
 +
* Solution: There is no single solution that applies to every system, and some of these effects cannot be resolved by the player.  See the S.T.E.P. Project Guide [http://wiki.step-project.com/Guide:Z-Fighting Z-Fighting] for examples of the issue and some INI tweaks that may help.  An FNV user tried some similar suggested in [https://www.youtube.com/watch?v=XjHt-4Z6PwI Gopher's "Mountain Flicker and Z-Fighting" video] and had the most success with adjusting the "fNearDistance=" value under [Display] in the "FalloutPrefs.INI" file.  He reports that anything above "10" results in clipping with arms and weapons in first person mode, but a balance can be reached with some testing.
 +
: Tweaks to create "Fog" in the distance to mask Z-Fighting: The following are derived from the [http://www.tweakguides.com/Fallout3_7.html TweakGuides for Fallout].  Page numbers refer to that document.
 +
:* [GRAPHICS] (Page 9)
 +
::* "BlockLoadDistanceLow=" (default: 50000; corresponds to [Distant LOD] "Object LOD Fade" in INI /In-Game settings (page 7), but more extreme.)
 +
::* "fTreeLoadDistance=" (default: 40000; corresponds to [Distant LOD] "Tree LOD Fade" in INI /In-Game settings (page 7), but more extreme.)
 +
::* See also "fSplitDistanceMult=" in this section, though this is less likely to be effective if you are trying to increase the "fog" effect.
 +
 
 +
<span id="Issue: Entering an Interior spawns the player in a huge ball of items and NPCs (junkado)"></span>
 +
=== Issue - Entering an Interior spawns the player in a huge ball of items and NPCs ''aka '''junkado''''' or '''''junknado''''' ===
 +
Also sometimes referred to as a "vortex on junk" or "compacting of cell contents".
 +
 
 +
* Cause-1: This has been traced to a corrupt ESM plugin from the mod [http://www.nexusmods.com/newvegas/mods/50817/? CAM - Chems Alcohol and Meds] by '''SenterPat'''.
 +
:* Solution-1: The problem has been fixed in version 9 of the mod.  Apparently it was resolved by removing the internal file header "ESM" flag from the ESP file.
 +
* Cause-2: File "FINAL Searchlight Airport NCR.esm" in mod [http://www.nexusmods.com/newvegas/mods/40324 Searchlight Airport NCR or Legion].  To put it simply, this mod makes a few minor adjustments in the "Camp Forlorn Hope Messhall" cell, which wouldn't be an issue except it moves one of the decals to something like (-3000) under the cell. No idea why the game responds this way, but the result is that the decal inexplicably pulls everything not nailed down along with it. Its like a powerful electromagnet dragging everything along the ground.
 +
:* Solution-2a: Thanks for '''Merik2013''' for diagnosing the source and solution to the problem.  He simply reset that decal back to its default settings and everything went back to normal. You probably could also just delete it from that ESM as well.  As always, make backups of the mods before editing.
 +
::* The cell is '''CampForlornHope01''' and the decal is ''NVNCRDecalCLeg''. You'll want to right click the decal and click the "edit" option.
 +
::* Its the Z Position that needs to be changed. He changed it to its default value, which is 671.1060. Also disabled (unchecked) all the miscellaneous changes made to it just to be sure it took, but that might not be necessary. The changes the mod made were enabling the "Persistent Reference" and "Initially Disabled" options as well as the "Flags: Set Enable State to Opposite of Parent " option under the "Enable Parent" tab.  (The last has also been suggested as a possible general fix to the problem on it's own.)
 +
 
 +
:* Solution-2b: Thanks to '''Roy Batty''' for the following:
 +
::* Go into [http://www.nexusmods.com/newvegas/mods/34703/? FNVedit] and change the cleaning setting "set z -<some high number>" (ex: -3000) and TURN IT OFF.
 +
::* Reclean your mod.
 +
::: (Note this solution predates v4.x of '''FNVEdit''' which has replaced such settings with the "AutoClean" function.  Presumably this is implemented in that function but we lack reports on how effective it is for this purpose, which is why it is not the primary solution.)
 +
 
 +
:* Solution-2c: Thanks to '''user826''' for experiments based upon the above "Solutions" leading to the following theory for mod creators:
 +
:: Placing (either deliberately or accidentally) "objects" (to include '''GECK''' things with "collision": like "trigger box activators") outside the "havok range boundary" of a cell seems to cause the "junknado".  (While this seems to occur in the "z-axis" most commonly, there is nothing to suggest so far this cannot occur when exceeding that boundary along any axis.)  The following warning about "accidental placement" is found in the [http://geckwiki.com/index.php?title=Bethsoft_Tutorial_Optimization Bethsoft Tutorial Optimization] article on '''GECKWiki''':
 +
<blockquote>
 +
    WARNING: Havok physics and the [http://geckwiki.com/index.php?title=Markers room markers] do not play well together. Avoid placing Havokable objects [to include [http://geckwiki.com/index.php?title=Movable_Static movable statics]] near [http://geckwiki.com/index.php?title=Room_Bounds_and_Portal_Basics portals] that they might be knocked through. [If an object is in, say, room A, then drawing of that object is restricted to people who are in room A, or who can see the object through a '''portal''' to room A. If the Havok engine causes the object to move (because the player picked it up with the Z key, or an explosion threw it) then the object will continue to be drawn so long as the object is in the motion under the control of the Havok system. However, once the object comes to rest, it is passed back to the normal renderer, and is once again drawn only for people in room A... even if it is now in room B. If you are in room B, with the object, it will be invisible to you.]
 +
</blockquote>
 +
 
 +
* Cause-3: Some Weather mods cause this problem as a conflict in the interior cells of some mods.
 +
:* Solution-3:  If applying the "Solution-2a/2b" fixes above to either or both of the mod plugins in question fails to resolve the issue, try switching to a different Weather mod.
 +
 
 +
<span id="Issue: Female Character strafing left modelling glitch"></span>
 +
 
 +
=== Issue - Female Character strafing left modelling glitch ===
 +
The left arm appears totally mangled.  Only seems to affect female models, and persists even if the entire FNV game and "Users\<acct>\documents\My Games\FalloutNV" folders are deleted and re-installed with only vanilla files (no mods).
 +
 
 +
* Cause: Why the problem persists through a re-install is unknown.  However, the cause appears to be related to the "left movement" animations used.
 +
:* Solution: For at least one user this was "mitigated" (though not actually resolved) by downloading a "BnB" (Bouncing Natural Breasts) skeleton and copying the "left movement" animations located in that mod's "meshes\characters\_male\female" folder to that of the "Data" folder tree.
 +
 
 +
<span id="Issue: FPVCameraBug"></span>
 +
=== Issue - First Person camera bug wearing Riot Armor family of gear ===
 +
There can be a problem with the mod [https://www.nexusmods.com/newvegas/mods/55334 New Vegas - Enhanced Camera] by '''LogicDragon''' when drawing a weapon (even bare hands) in "First Person View" while wearing Power Armor or Elite Riot Armor in which half of the view is blocked by the left shoulder pauldron.
 +
 
 +
* Cause: This is due to a bug in the mod [http://www.nexusmods.com/newvegas/mods/51664 Yukichigai Unofficial Patch - YUP] that makes it so the Riot Armor family has its left shoulder appear in first person.  The source of the problem seems to be from YUP version 11.3 onwards (and possibly earlier versions.)  The YUP team is aware of the problem, but it has not been fixed as of version 11.7.  The same problem has also been referenced in the "Enhanced Camera" comments without attributing it to YUP.
 +
 
 +
:* Solution: Remove YUP from the load order.  As YUP provides many, many other bug fixes this is less than ideal and not recommended, but does resolve this particular problem.
 +
 
 +
:* Partial Workaround:  The mod [http://www.nexusmods.com/newvegas/mods/65496 Elite Desert Combat Gear] offers a Desert Ranger Combat armor and helmet with the same stats as Elite Riot gear. The helmet is however still light armor to reflect the changes made by YUP.
 +
 
 +
<span id="Issue: Fisheye"></span>
 +
 
 +
=== Issue - Fisheye lens effect in 3rd Person ===
 +
Both FO3 and FNV have a horrible "fisheye lens" effect with the default of 75 or higher in 3rd Person "Field of View" (FoV).  This affects what can be seen in the HUD, especially distorting items at the edges.
 +
 
 +
* Cause: The problem lies with the way the game is displaying the image. For screenshots modders and imageshare users tend to greatly reduce the FoV to correct the problem, sometimes going as low as 30 or even 20.  The game is unplayable with the FoV this low; but it makes for better character screenshots.
 +
:* Solution: Use the "mouse wheel" to zoom the "chase camera" in or out as needed, or play around with the FoV using a mod such as [http://www.nexusmods.com/newvegas/mods/55085 FOV Slider].  However, note there are several different FoV settings and they have some impact upon each other.  The mods [http://www.nexusmods.com/newvegas/mods/36773 Further 3rd Person Camera] or [http://www.nexusmods.com/newvegas/mods/65521 Definitive Camera Hotkeys - a PHW Module] for normal game play may also help.
 +
 
 +
<span id="Issue: Flickering Shadows on grass"></span>
 +
 
 +
=== Issue - Flickering Shadows on grass ===
 +
* Cause: Video settings issue.
 +
:* Solution: Any one or combination of the following may work:
 +
:# Switch between "HDR", "Bloom", and "No Lighting Effect" (NLE) settings in the game video panel.  HDR is the default and increase the "glow" of the lighting accents, at some (varying) cost in FPS.  Some feel Bloom makes the sky seem overly bright but doesn't have the FPS hit.  NLE really tones down the glare and is more subdued.
 +
:# Set ''Ambient Occlusion'' to "Quality" in the video adapter card control panel.
 +
:# Set ''Negative LOD Bias'' to "Clamp" in the video adapter card control panel.
 +
:# Disable ''Anti Aliasing '' in the video adapter card control panel.
 +
:# In all three INI files, try setting "bShadowsOnGrass=0" under "[Display]" section.  However, reportedly this only affects the shadows of Actors.
 +
:# Use the [http://www.lagom.nl/lcd-test/ Lagom LCD Monitor Test Site] to check if you need to adjust the color controls (e.g. "brightness or contrast") on your physical display monitor.
 +
 
 +
<span id="Issue: Floating objects"></span>
 +
===Issue - Floating objects===
 +
Some objects in a cell "float" above ground level.
 +
* Cause: More than one plugin is changing the same thing, causing a record level conflict.
 +
* Solution-1: Use a "compatibility patch" file to resolve the record conflict.  See the [http://tesalliance.org/forums/index.php?/tutorials/article/28-oblivion-creating-compatibility-patches/ Oblivion: Creating Compatibility Patches - Worldbuilding - TES Alliance] article for basic guidance on creating one.
 +
* Solution-2: Edit each floating object in the "console window" (typically toggled with the "~" key), and then save the game.  The result would persist from that save game point onwards.  However it will re-appear if an earlier save were loaded, or a new game started, or a new mod added which also conflicts: so it is only a temporary solution to that specific conflict.  The edit would consist of:
 +
:* Click on the floating object.
 +
::* Use the "getpos [x|y|z]" commands, where "x"= is the '''horizontal''', "y" is the '''vertical''', and "z" is 'the '''height''' above the water table (AKA "ground level")' axis location in the cell.  Each axis must be retrieved individually, i.e. "getpos x", "getpos y", and "getpos z".  Record each result.
 +
::* Use the "getangle [x|y|z]" commands in the same manner.  Record each result.
 +
::* Use the "setpos z 0.00" command to reset the height of the object to "ground level".  Note the floating decimal number value.
 +
:: The record of "getpos" and "getangle" entries will enable you to restore things with the appropriate "setpos" or "setangle" commands if anything goes wrong.
 +
:* Repeat the above steps for each floating object as needed.
 +
:* Make a "full save" to a new "save game" slot.
 +
 
 +
<span id="Issue: Fog effect around the Vegas Strip"></span>
 +
=== Issue - Fog effect around the Vegas Strip ===
 +
* Cause: The area around New Vegas (outside the strip itself) uses the "NVWastelandHazy" weather type which includes the same effect that the distance fog does, but it's set as if the distance is nothing (-10) causing it to be present right where you are. Apparently it's there to give everything a sort of dirty/dusty appearance, as if lots of sand and dirt has been kicked up by the amount of human activity around Vegas.  The weather that does that nasty looking fog is "NVUrbanClear [WTHR:00173564]".
 +
:* Solution: Forcing the weather from "NVUrbanClear [WTHR:00173564]" to "NVWastelandHazy [WTHR:00100A4E]" will remove the fog.  "NVWastelandClear [WTHR:000FFC88]" doesn't "fog".
 +
:: Looking at NVUrbanClear, it has '''FNAM - Fog Distance''' Day & Night "- Near fog" set to "-10". ("NVWastelandClear" does as well), although during the night time it doesn't fog your eyes.
 +
:: So essentially to get rid of the fog using '''xEdit/'''[http://www.nexusmods.com/newvegas/mods/34703/? FNVedit], you would expand the "Weather" '''Object''' category, select "NVUrbanClear", and then scroll down to "FNAM - Fog Distance" and change "Night - Near" from "-10" to "2000"; and also for "NVWastelandClear" change both "Night - Near" and "Day - Near" from "-10" to "2000". Any Fog setting that is "-10" should be set to "2000" if "Near", and "200000" if "Far", to get rid of the foggy effect.
 +
 
 +
<span id="Issue: Head clipping through hair"></span>
 +
 
 +
=== Issue - Head clipping through hair ===
 +
* Cause: FNV requires the vanilla hair meshes to be located in BSA archives to display properly. If you need to edit one of them, unpack it somewhere other than your Data directory.  If the problem is with custom hair styles, it is most likely that they were not made properly.
 +
:* Solution: If you have "Data\Meshes\Characters\Hair" and "Head" folders, delete them and toggle "ArchiveInvalidation" so the game uses the files in the "Fallout - Meshes.BSA".
 +
 
 +
<span id="Issue: Interior cell portions not visible"></span>
 +
=== Issue - Interior cell portions not visible ===
 +
You may find some things invisible, not rendered, or apparently "transparent walls" in some interior cells; without ENB or other "post processor" installed or active.
 +
 
 +
*Cause: Mod conflict with more than one attempting to modify the same interior cell.  Often this is done by an author "copying" the interior cell and making changes without taking proper precautions regarding optimizations.  See the '''GECK''' [[#TIP: Enable "MultiBounds"|TIP: Enable "MultiBounds"]] for details.
 +
:* Solution-1: You may want to experiment with changes to the "interior buffer size" setting.  Start small, as the memory has to come from that used elsewhere.  Please see the "[http://www.tweakguides.com/Fallout3_10.html Memory, Loading & Multi-threading]" entry in the TweakGuides.com "Fallout 3 Tweak Guide".
 +
 
 +
:* Solution-2: The problem in the offending plugin has to be resolved by the author.  In the meantime, you have to identify the offending plugin(s) and remove from your "load order".  Please see the '[http://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice#Clean_Saves Clean Saves]' section of the wiki "[http://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice FNV General Mod Use Advice]" article.
 +
 
 +
:: See also [[#Issue_-_Followers_not_moving_or_Navmesh_Problems|Issue - Followers not moving or Navmesh Problems]] entry under the "Miscellaneous Solutions" section.
 +
 
 +
<span id="Issue: Invisible Companion"></span>
 +
 
 +
=== Issue - Invisible Companion ===
 +
A companion has suddenly gone "invisible" in the game, and nothing seems to make them visible again.  Their marker appears on the Pipboy map, but they do not seem to physically be there upon traveling to that location.
 +
 
 +
* Cause: Unknown, but the situation has been reported to occur before.
 +
:* Solution-1a: Load an earlier save from before they disappeared to obtain the companion's "Ref-ID".
 +
::* Travel to the companion's location so your character is near them.
 +
::* Open the in-game console (default is the < ~ > key).
 +
:::* < Click > on the companion. This is all that is needed. Note this will display an 8 character "Ref-ID" above them, which you will need to remember.
 +
::* Enter the console command: "prid <Ref-ID>" and < Enter >, but without the quotes (where "Ref-ID" is what you noted for the companion in the previous step).
 +
::* Now enter: "disable" and < Enter >.
 +
::* Follow with "enable" and < Enter >.
 +
:: This sequence should make the companion visible again.
 +
 
 +
:* Solution-1b: Revert to using the earlier save from prior to their disappearance.
 +
 
 +
:* Solution-1c: If "Solution-1a" doesn't work and "Solution-1b" is not really feasible and you prefer to live with the consequences, try "resurrecting" the companion.  They may end up without their current inventory: losing everything you gave them to carry and reverting to their starting equipment.  It might also interfere with some of their quests as well, which is why it's the least preferred solution.  Follow the same basic process with the commands:
 +
::* "prid <Ref-ID>"
 +
::* "kill"
 +
::* "resurrect"
 +
::* "disable"
 +
::* "enable"
 +
:: This may require you to "re-hire" the companion and reset it's "companion command options".
 +
 
 +
<span id="Issue: InvisibleCorpses"></span>
 +
=== Issue - Invisible Corpses ===
 +
Symptoms: Any type of preplaced corpses in game (regardless if it's from primary ESMs for the game, edited ones, or even entirely new preplaced corpses from mods) turn entirely invisible and have no physical form to interact with, but can still be opened/searched as a container.
 +
 
 +
* Cause: The mod [https://www.nexusmods.com/newvegas/mods/66514?tab=description Slow Death] (file "(Animation)_Slow_Death.esp") has been confirmed to be at least one cause.
 +
:* Solution:  Remove the mod.  (It has been suggested the likely culprit for this issue is the 'SlowDeathBEScript' script, but not confirmed.)  This mod is based upon another ([http://www.nexusmods.com/newvegas/mods/60201 Near Death]) which might serve as an alternative.
 +
 
 +
<span id="Issue: LightingExteriors"></span>
 +
 
 +
=== Issue - Lighting - Exteriors at night ===
 +
Symptoms: Walls and ground textures seem to strangely disappear and re-appear from close view at night.  This might appear to be due to a missing or fading texture.
 +
 
 +
* Cause: FNV has a known "lighting problem " due to the game engine being limited to a maximum of 4 lights per exterior cell.  This causes lights suddenly disappearing, terrain not lighting properly, random polygons going unlit, etc..
 +
:* Solution: The mod [https://www.nexusmods.com/newvegas/mods/69833 Improved Lighting Shaders] fixes the shading code to work with up to 13 light slots, and also includes 28 re-assembled shaders that make full use of them.<br>
 +
:: In other words this pretty much gets rid of the lighting bug, and your Pip-Light can shine brightly without interfering with other lights!<br>
 +
:: Lights besides the Pip-Light are also improved: no more lights disappearing/reappearing depending on your camera position, or lines appearing when a light crosses cells - lights will now almost always remain lit if they're active!<br>
 +
:: ENB Users: Please note the "sticky" at the top of the comments page.
 +
 
 +
<span id="Issue: LightingGlow"></span>
 +
=== Issue - Lighting - Faces and surfaces glow ===
 +
Symptoms: After installing mods, actors' ''faces'' and some surfaces have an excessively bright glow or shine in both interiors and exteriors.
 +
 
 +
* Cause: This has been noted for some users of the mod "[https://www.nexusmods.com/newvegas/mods/35998 Nevada Skies - Weather Effects]".
 +
:* Solution:  Simply disabling the plugin is not sufficient.  The report indicated it was necessary to run the "quick auto cleanup" function of [https://www.nexusmods.com/newvegas/mods/34703 FNVEdit] to completely remove the effects and restore things to "vanilla".
 +
 
 +
=== Issue - Lighting - Mod makes the Sun too bright off surfaces ===
 +
[Formerly "Issue - Mod makes the Sun too bright off surfaces".]
 +
 
 +
Symptom: Note this is not "sun glare", which is when you look directly at the sun in game.
 +
Be aware that there is a "light dome effect" around the New Vegas strip which is quite visible from a distance at night.  Daylight surfaces within this dome area are blindingly bright from some angles on default settings.  This appears to be by design.
 +
 
 +
* Cause-1: Lighting mods make adjustments to various lighting values, resulting in uncomfortably bright reflections off some surfaces.  Sometime these are by way of tweaks to the INI file, and sometimes controlled "in-game".
 +
 
 +
:* Solution-1a: Only use one lighting mod for exteriors, and one for interiors.  Read their documentation carefully for recommendations on where to position them in your load order.
 +
:: Some mods intend you to use hats and sunglasses to mitigate the effect.  Changing the facing direction may also have an effect.
 +
:: INI tweaks depend upon which surfaces and where they are located.  See the [https://web.archive.org/web/20161025065631/http://www.tweakguides.com/Fallout3_1.html Tweakguide's General Fallout game guide] (specifically for FO3 and FNV) for the effects of particular settings.
 +
 
 +
:* Solution-1b: The mod [http://www.nexusmods.com/newvegas/mods/51577/? Dynavision 3] incorporates (saving a plugin slot) [http://www.nexusmods.com/newvegas/mods/39619/? The Imaginator] which "allows you to separately control visual elements like Brightness, Contrast, Saturation, Light Output, Depth-of-Field, Focus, Motion Blur and Tint all from within an easy-to-navigate PIP-BOY menu". Dynavision 3 now works with UIO instead of requiring it's own installer.
 +
:: This is a recommended alternative to ENB and other "post-processors".  However, Dynavision has a persistent and annoying bug which frequently causes NPCs to go invisible.  Some people recommend using the older "Dynavision 2" + "Imaginator" instead, but the same "invisible NPCs" bug was reported with it.  A patch file to fix this issue in "Dynavision 3" was posted in mid 2016, but there are no comments regarding how effective it is.
 +
 
 +
:* Solution-1c: INI Lighting tweaks.  The following is derived from the [https://web.archive.org/web/20161025065631/http://www.tweakguides.com/Fallout3_7.html TweakGuides for Fallout].  Page numbers refer to that document.
 +
::* [View Distance] (Page 7)
 +
::: Specularity Fade: This slider controls how shiny reflective surfaces appear to be. In practice the only obvious impact of changing this setting is that some metallic objects will lose their shine.  However you can also manually adjust the value of this setting by editing the INI "fSpecularLODStartFade" variable, and if you want to disable specularity altogether, either to further boost performance, or if you believe the game world is too shiny, then see the "bDoSpecularPass" variable covered on page 9.
 +
::* [Display] (Page 7)
 +
::: Brightness: This gamma slider controls how bright or dark the overall screen image will be. Adjust it so that at night the image is visible but not washed out. It has no impact on performance, so set to suit your taste. If you need to increase gamma to be much brighter than the maximum on the slider allows (e.g. on very old monitors), see the "fGamma"-related variables on page 9.
 +
 
 +
:* Solution-1d: Sometimes "post-processors" like the ENB Series can compensate, though remember that these often impose a penalty upon your "frames per second" (FPS).  The first resort in these cases is often choosing a different "preset", but if you want to adjust settings yourself, see the S.T.E.P. Project [http://wiki.step-project.com/Guide:ENBseries_INI ENBSeries INI Guide] page which "is intended as THE comprehensive reference to the functionality of all parameters found within enbseries.ini as it evolves."  Suggest you start with the "[BLOOM]" and "[REFLECTION]" sections.
 +
:: The [http://www.overclock.net/t/1386086/guides-to-creating-and-customizing-your-enbs Guides to Creating and Customizing Your ENB's] thread is another ENB settings resource.
 +
 
 +
* Cause-2: Your monitor brightness/gamma is too high.
 +
 
 +
:* Solution-2: Use the [http://www.lagom.nl/lcd-test/ LCD monitor test images] web site as reference to adjust your monitor calibration to what you desire.
 +
 
 +
<span id="Issue: Main or DLC missing elements"></span>
 +
=== Issue - Main/DLC - missing elements ===
 +
Symptoms: A "vanilla" (from the publisher) component of the game (Main or any DLC) is missing or has "messed up" components such as missing the buildings or objects in the distance, meshes, textures, etc..
 +
 
 +
* Cause:  Cleaning the ESM file.
 +
:* Solution: Despite what any "generalized" tool (such as LOOT) or elsewhere for any other Bethesda games may advise as a general practice, DO NOT clean any of the publisher's game files.  If you have done so, use the "verify local files" procedure or your backed up copies to restore the vanilla files.  You may possibly need to rebuild any "merged patch" and FNVLODGen files if simply restoring the ESMs is not enough.
 +
 
 +
:: Even with mods, such cleaning should be performed by the mod author: who is the only one who really knows if an ITM is needed in their mod.  FNV came along after the usual problems that required cleaning were well known, and most authors have taken on that responsibility.  Inform them of any such problems you encounter.
 +
 
 +
<span id="Issue: Missing textures/walls"></span>
 +
 
 +
=== Issue - Missing textures or walls ===
 +
Entering some locations (e.g. "Hidden valley bunker", "Kings school", and "Camp Golf") the walls appear to be transparent or missing, allowing a view of some elements of the adjacent interior rooms.  Collision still seems to be functioning (the character doesn't fall through the "gray areas" if they are entered).
 +
 
 +
* Cause: Mod conflict
 +
:* Solution: The plugin "PrnOut.esp" (apparently a component of the "Sexout" mod) seems to be at least one culprit.  Deactivating it has been reported to correct the issue.
 +
 
 +
<span id="Issue: Mod makes the Sun too bright off surfaces"></span>
 +
 
 +
<span id="Issue: Naked NPCs (missing armor or inventory)"></span>
 +
 
 +
=== Issue: Naked NPCs ''aka missing armor or inventory'' ===
 +
* Cause: Vanilla Bug - Some NPCS are naked/have a weird inventory: An engine bug will sometimes not correctly refresh named and unnamed NPCs.  The problem seems most often when they are supposed to be wearing leather armor.  (This appears to be a problem with "leveled lists".)
 +
:* Solution-1: As always with any texture bug, try toggling "ArchiveInvalidation" off-and-on again.
 +
 
 +
:* Solution-2: Use/rebuild your "merged patch" file.  Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki [http://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice FNV General Mod Use Advice] article.  Note that mods adding armor/clothing that is not appearing in-game may need to have the "bash tags" "Delev" and "Relev" added.
 +
 
 +
:* Solution-3: Just open the console (default "<~>" key), click on the NPC and note it's displayed "Base-ID". Then type "resurrect <Base-ID>" (replacing "<Base-ID>" with the value noted when you clicked on the NPC). The NPC will be correctly refreshed with its gear.  If that doesn't work, try "resetinventory <Base-ID>".
 +
 
 +
<span id="Issue: NPCs making annoying SHHHH sound and hand gesture"></span>
 +
=== Issue - NPCs making annoying SHHHH sound and hand gesture ===
 +
Some NPCs in the game, such as General Oliver & the Holograms & Dean Domino (when you meet him in the theater in Dead Money DLC), make that annoying SHHHH sound & hand gesture.
 +
 
 +
* Cause: This has been traced to the mod [http://www.nexusmods.com/newvegas/mods/43386 Axepriests Face Aches for FNV] by '''SariDecember''', which is a port of the FO3 mod [http://www.nexusmods.com/fallout3/mods/6709 FAFF - Face Aches For Fallout] by '''Axepriest''' (who hasn't been active on Nexus since Feb 2016).  This adds facial expressions to idle animations ("*.kf" files).
 +
:* Solution: The mod is designed only to work with vanilla head meshes and textures, adding "morphs" which reference the data built into the FaceGen TRI files.  (See the "[[Getting_started_creating_mods_using_GECK#FaceGen:_Heads.2C_Faces.2C_Hairs.2C_and_Helmets|FaceGen: Heads, Faces, Hairs, and Helmets]]" section of the wiki "[[Getting_started_creating_mods_using_GECK|Getting started creating mods using GECK]]" article.)  Either remove the mod, or refer to the FNV and FO3 mod descriptions to attempt to change the morphs associated with the idle animation in question.
 +
 
 +
<span id="Issue: PermanentLimp"></span>
 +
=== Issue - Permanent Limp ===
 +
Symptoms: the Player displays a limp even after having been healed of damage.<br>
 +
If it's an animation, then it's a 'feature' of the game (or some mod); not a bug.  It indicates the Actor has broken a limb.  If it "heals" without the proper treatment, it becomes "permanent".
 +
 
 +
* Cause: With the legs, it's typically from a fall from a height or critical hit to the leg.
 +
 
 +
:* Solution: You need to heal the limb with a "doctor's bag" (which contains a "splint") or by an actual doctor before saving.  (Just healing damage with Stimpacks, etc. won't "set the break".)  Once it has gotten in your "save game" files, it has (for some people) been fixable by reloading the save file during the same "game session" (i.e. not exiting to the desktop).  Others found it necessary to go back to a save prior to the injury.
 +
 
 +
<span id="Issue: Pink teeth/tongue/mouth"></span>
 +
 
 +
=== Issue - Pink teeth or tongue or mouth ===
 +
* Cause: This is another "missing texture file" problem, usually because of failing to allow overwrite of a file during installation of the mod in question; sometimes by not actually making a choice of options.
 +
:* Solution: Uninstall the mod entirely from your mod manager (or the "Data" folder), close the manager and re-open, and re-install the mod.  This time always make a choice to "overwrite" when offered unless you have very good reason to not do so (knowing it may cause problems with the mod).
 +
 
 +
<span id="Issue: Player hands are either stubs, too large, or the fingers are missing"></span>
 +
=== Issue - Player hands are either stubs or too large or the fingers are missing ''AKA Fingers glitch'' ===
 +
* Cause: Fallout 3 and New Vegas have a bug when using ''iFPSClamp'' (in the game INI file), causing the hands of NPCs and the player to either become massive, or collapse into themselves.
 +
: This problem seems to also be linked to the "64Hz bug" fix for "microstutter" included in "New Vegas Stutter Remover" (NVSR) and "New Vegas Tick Fix" (NVTF).  The reason why the "64Hz bug" occurs is because the renderer uses ''GetTickCount'' which returns a variable frequency that jumps between 13-16ms, whereas ''TimeGetTime'' will consistently return a frequency of 1ms.  This is an "Unreal Engine" bug which persisted into 2015 (at least).
 +
: As both NVSR and NVTF use the same code for the "64Hz bug", the end result is that you can choose between having a microstutter and no "fingers glitch" or having no microstutter and fingers glitching out. 
 +
: There is no one reliable solution to the problem.  The following "mitigations" have helped people to different extents.
 +
 
 +
:* Mitigation-1: See also the related [[#Issue_-_Vsync_aka_V-Sync_ON_or_OFF|Issue - Vsync aka V-Sync ON or OFF]] regarding "frame rate synchronization", "screen-tearing", and "lag".
 +
::* The various "Borderless Window" or "Fake Fullscreen Window" mods (such as "[http://www.nexusmods.com/newvegas/mods/59266/? OneTweak for NVSE]" by virusek) may prevent Vsync issues if you don't have a triple buffered video card. 
 +
:* Mitigation-2: Setting "bManageFPS=0" in NVSR.INI, the "finger glitch" problem is gone, but then stuttering is back.
 +
:* Mitigation-3: Limit your FPS to 60.  If that doesn't help, try using a setting just below that (ie. 57-59).
 +
:* Mitigation-4: Manage your FPS setting in only one location (e.g. NVSR or the INI file, but not both).  If you do have to manage it in more than one location, then ensure you have the same cap in all setting locations.  (There are suggestions about this in the "Causes" under the [[#Issue_-_Game_in_slow_motion|Issue - Game in slow motion]] entry.) 
 +
:: Note there may be different settings for "maximum" and "minimum" FPS.  Setting a "minimum" below 30 causes the render engine into a "slow display mode".
 +
:* Mitigation-5: Others have reported that "drawing a two-handed weapon" or exiting to the desktop and re-loading the game save file have temporarily resolved the "fingers glitch" problem.
 +
:* Mitigation-6: Try a different video driver.
 +
::* Or, an alternative solution to a driver update: Grab [http://www.entechtaiwan.com/ps.htm Powerstrip] and follow simple instructions in [http://gfycat.com/MinorSilentArgusfish this GFY].
 +
 
 +
<span id="Issue: Pip-boy and Terminal screens are all white/blank"></span>
 +
 
 +
=== Issue - Pip-boy and Terminal screens are all white or blank ===
 +
* Cause-1: This is a known game bug.
 +
:* Solution-1: Try toggling the Pip-boy light on and off a few times (hold down the < Tab > key for a few seconds) to see if it resolves the problem.
 +
 
 +
* Cause-2: A mod for the Pip-boy 3000 or attempts to optimize texture files have installed texture files causing the problem.
 +
:* Solution-2: Check the "Data\Textures" folder for a "Pip-boy 3000" sub-folder and if it exists, delete the sub-folder.  The game will then use the default files in the BSA.
 +
 
 +
<span id="Issue: Playing at greater than 1920x1080 resolution"></span>
 +
=== Issue - Playing at greater than 1920x1080 resolution ===
 +
* Cause: By default the game hardware setup options only permit a maximum of 1920x1080 resolution.  This is a factor due to it's age.  It simply didn't know what later advances in screen sizes would establish as standards.
 +
:* Solution-1: In the "FalloutPrefs.ini" file under the "[Display]" section (near the bottom) are two entries where you should specify your desired game screen size to match your default/native monitor resolution:
 +
<div name="Simulated code box" class="boilerplate metadata" id="Warning Notice"
 +
style="margin:0px 10px 10px 50px; border:1px dashed #DAA520; color: lightgray; background-color:#424242; padding:3px;
 +
/* Remove the next four 'white-space' lines to restore default white-space processing. */
 +
white-space: pre-wrap;      /* css-3 */
 +
white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
 +
white-space: -pre-wrap;      /* Opera 4-6 */
 +
white-space: -o-pre-wrap;    /* Opera 7+ */
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">
 +
iSize W=<width in pixels> (i.e. 2560)
 +
iSize H=<height in pixels> (i.e. 1440)
 +
</div>
 +
:: However, these only work if you have the "bFullScreen=1" setting enabled so the game starts in "full screen" mode.  In "windowed mode", the game will revert back the maximum of 1920x1080 that it knows about.
 +
 
 +
:* Solution-2: If you prefer to run the game in "fake fullscreen windowed mode" so you can get to other programs or screens, then you need to use a setting of "bFullScreen=0" (windowed mode), along with the above "iSize" settings, AND a '''NVSE''' mod which handles the "fake fullscreen" effect while recognizing the larger screen resolutions.  NVSE knows and can read the INI setting and override the game.  These are reported to do so:
 +
::* [http://www.nexusmods.com/skyrim/mods/40706/? OneTweak] by '''virusek''' (from the Nexus Skyrim Catelog, but works with FNV.)
 +
::* [http://www.nexusmods.com/newvegas/mods/57843/? FullScreenWindowedMode] by '''TimThompson89'''.
 +
 
 +
:* Solution-3: If you are using a "post processor" such as ENB, make sure it is not adding some feature like "cinematic bars" to create an effect similar to "letter-boxing" of your display.
 +
 
 +
:* You will probably want to see the [[#Issue: Scope zoom distortion problems|Issue: Scope zoom distortion problems]] entry as well.
 +
 
 +
<span id="Issue: Scope zoom distortion problems"></span>
 +
 
 +
=== Issue - Scope zoom distortion problems ===
 
Playing with widescreen (16:9) and high resolution (1920x1080 or higher) and have a problem with scope zooms (white square edges or just edges in the reticle and the scopes have an outstretched circle).
 
Playing with widescreen (16:9) and high resolution (1920x1080 or higher) and have a problem with scope zooms (white square edges or just edges in the reticle and the scopes have an outstretched circle).
 
* Cause: Game masking that is automatically applied to scopes.
 
* Cause: Game masking that is automatically applied to scopes.
Line 275: Line 2,966:
 
* Solution:  add the line "fScopeScissorAmount=0", in the "[Display]" section of all 3 INIs.
 
* Solution:  add the line "fScopeScissorAmount=0", in the "[Display]" section of all 3 INIs.
 
*: Make backups of the INIs before changing them.
 
*: Make backups of the INIs before changing them.
 +
:: When you make any changes to the game INI file, remember to change it in all three files: the "Fallout_default.ini" in the game root folder (which only gets used to recreate the other two when they are not found), and the two in "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder ("FALLOUT.ini" and "FalloutPrefs.ini").  Otherwise you tend to lose track of which you actually changed if you have to "verify files", and they may not appear to "take".<br>
  
=== Issue: Screen brightness gets darker as the game progresses ===
+
<span id="Issue: Screen brightness gets darker as the game progresses"></span>
 +
=== Issue - Screen brightness gets darker as the game progresses ===
 
* Cause-1: Conflict between ENB and SweetFX settings.
 
* Cause-1: Conflict between ENB and SweetFX settings.
  
Line 296: Line 2,989:
 
:* Amelioration: A mod that gives you more control over lighting in-game: [http://www.nexusmods.com/newvegas/mods/39619/? The IMAGINATOR].  This might be useful to confirm some mod is the culprit, by loading it near the end/bottom of the LO.
 
:* Amelioration: A mod that gives you more control over lighting in-game: [http://www.nexusmods.com/newvegas/mods/39619/? The IMAGINATOR].  This might be useful to confirm some mod is the culprit, by loading it near the end/bottom of the LO.
  
=== Issue: Full-Auto Iron Sights animation jump ===
+
<span id="Issue: Somehow, without changing anything, my character is "glitched" oddly"></span>
With "full auto" weapons, when aiming down the "iron sights" in 1st person and firing (even with "JIP Select Fire" set to single shot) the whole weapon seems to jump down so that the iron sights are below the actual aim point. When you stop firing it returns to normal.
+
=== Issue - Somehow ''without changing anything'' my character is ''glitched'' oddly ===
* Cause: When you fire it starts the full-auto attack loop and screws up aiming through the scope or iron sights.
+
* Cause: Unknown.
 +
:* Workaround: Something that's always worth trying is blowing yourself up or otherwise get killed: i.e. throw a grenade against a wall so it bounces back and kills you.  Then let the game reload.  Sometimes that can clear oddities.  However, it doesn't address any underlying cause, so it's only useful as a temporary solution.  Try to see if you can reproduce a reliable set of circumstances to re-create the problem.
 +
 
 +
<span id="Issue: Textures randomly change only on particular items"></span>
 +
=== Issue - Textures randomly change only on particular items ===
 +
* Cause: There is more than one BSA containing the named texture file, but they have different content.  The game does not have any mechanism to deal with this situation, so it randomly grabs the texture from one or the other BSA file.
 +
:* Solution-1: Try the simple solution of toggling "ArchiveInvalidation" off-and-then-on again.  This should cause any loose file to be used instead of one in a BSA.
 +
 
 +
:* Solution-2: Determine which mods have the different textures.  See [[#Issue:_Find_the_source_mod-index_of_an_object_in-game|Issue: Find the source mod-index of an object in-game]].  Once you have identified the one with your preferred texture, either remove the other offending plugin or extract the preferred texture from the BSA as a "loose file", and toggle "ArchiveInvalidation".
 +
 
 +
<span id="Issue - TTW Centaur Face distortion"></span>
 +
=== Issue - TTW Centaur Face distortion ===
 +
When playing "Tale of Two Wastelands" (TTW) the Centaur face may appear to stretch off into the distance.
 +
 
 +
Note: this is very similar to the problem with "B-n-B" bodies discussed under the [[#Issue_-_Body_Replacer_-_Custom_Body_Types|Issue - Body Replacer - Custom Body Types]] entry: having the same issue of differences in "bone attachment points" and "bone weighting".
 +
 
 +
* Cause: The TTW version 4.1 of the [http://www.nexusmods.com/newvegas/mods/59147? Ragdolls] mod version of the '''Evolved Centaur''' is missing modifications to the skeleton (armature) and mesh needed to fix dismemberments.  The author is aware of the problem, which will be fixed in releases after 4.1.  In the meantime he suggests the following "workaround".
 +
 
 +
:* Workaround "fix" for v4.1 (TTW): Install or unpack the Ragdolls TTW mod as usual, goto under the "meshes | creatures | centaur" folder, and delete "skeletonevolved.nif" file.  (You may want to repackage the "Ragdolls TTW" archive so that file is not later re-installed by accident.) Then toggle "ArchiveInvaliation" off-and-then-on again.
 +
 
 +
<span id="Issue: StuckIMOD"></span>
 +
=== Issue - Visual special effect (IMOD) stuck ===
 +
Some visual effect (such as "Cateye", "HUD Shudder", or "chem" induced blur) won't wear off or go away.
 +
 
 +
* Cause: An "[http://geckwiki.com/index.php?title=ImageSpace_Modifier imagespace modifier]" (IMOD) remains in effect.
 +
:* Solution: The console command "[http://geckwiki.com/index.php?title=RemoveImageSpaceModifier rimod <imodID>]" will remove the specified IMOD.  The mod "[http://www.nexusmods.com/newvegas/mods/69096 Clear Imagespace Modifiers BAT file]" is a console "bat" file containing that command for all of the vanilla IMOD effects to clear them all at once.
 +
 
 +
<span id="Issue: Weapons/Fists are displayed off-center in 1st Person"></span>
 +
 
 +
===Issue - Weapons or Fists are displayed off-center in 1st Person===
 +
3rd Person view displays correctly.
 +
* Cause: This is the result of a bug with the mod "A Familiar Friend", or with "Readius PipBoy" mods.
 +
 
 +
* Solution: Uninstall and start a new game.  It's hard to get the bug out of an existing game.  If you still wish to attempt this, be sure to follow the specific mod's uninstall instructions carefully.
 +
 
 +
<span id="Issue: Win10 Blurry/small text/icons"></span>
 +
=== Issue - Win10 Blurry or small text or icons ===
 +
The problem may be particularly apparent with "install programs".
 +
* Cause: This problem occurs on high-PPI resolution monitors and TVs (such as "Full HD" 1920x1080 and 4K-UHD 3840x2160 or higher resolutions).  Windows 10 introduced a solution called "High DPI Scaling", but earlier versions of the OS do not have the same capability because such displays were not in common use at the time.
 +
: (The terms "DPI" and "PPI" are often used interchangeably but actually have different technical meanings: DPI (Dots Per Inch) is correctly used for "scan" output in "dots" such as printers and analog displays, while PPI (Pixels Per Inch) is used for output in very small fixed sized "picture elements" ''aka "[http://en.wikipedia.org/wiki/Pixel_density pixels]"''.)
 +
 
 +
:* Solution-1a: See the [http://www.digitaltrends.com/computing/how-to-adjust-high-dpi-scaling-in-windows-10/ How to adjust high-DPI scaling in Windows 10] article for the explanation of how Windows 10 deals with this issue for both modern and older programs.  You may need to temporarily turn off the "Settings | System | Display | Advanced scaling settings | Fix scaling for apps | Let Windows try to fix apps so they're not blurry" setting and use a "Custom scaling" of "100%" when running "install programs".
 +
 
 +
:* Solution-1b: If you have a multiple monitor setup, then you want to use "individual display scaling".  Also see the [http://www.pcworld.com/article/2953978/displays/use-windows-10s-individual-display-scaling-to-perfect-your-multi-monitor-setup.html Use Windows 10's individual display scaling to perfect your multi-monitor setup] article in that instance.
 +
 
 +
:* Solution-1c: There are other built-in Win10 tools you can use to "fine tune" your display.  See the [http://www.cnet.com/how-to/6-display-settings-you-should-be-using-in-windows-10/ 6 display settings you should be using in Windows 10] article if the above is not sufficient to your needs or you want the best possible results.
 +
 
 +
<span id="Issue: Win10 Screen tearing in "Borderless Windowed Mode""></span>
 +
 
 +
===Issue - Win10 Screen tearing in ''Borderless Windowed Mode''===
 +
Based upon this [http://www.reddit.com/r/pcgaming/comments/6ukc1z/tip_disable_full_screen_optimizations/ Reddit thread]
 +
* Cause:  Apparently, Win10 "Full Screen Optimizations" setting is enabled by default in Win10 since the Anniversary Update.  It basically forces a game to run in "borderless fullscreen mode" (even if you selected "fullscreen mode" in the game's options) making the game stutter more, frametimes more variable, and there may be some performance loss.
 +
: It is not putting games into standard "Fullscreen Windowed/Borderless Mode". It's a new presentation mode that is intended to combine the best of both "Windowed" and "Fullscreen Exclusive Mode".  Before the Windows 10 Creator's Update, it was exclusive to DX12 UWP apps. Now there are 80+ non-UWP, non-DX12 games which support it.
 +
: "Standard Fullscreen Windowed Mode" passes everything through the ''desktop compositor'' which forces "triple-buffered V-Sync" to be used, and adds a frame of latency. This new presentation mode can bypass the ''compositor'', reducing latency and allowing you to disable "V-Sync". At the same time, it enables fast <Alt+Tab>ing if there's no display mode switching.
 +
: "Fullscreen Windowed Mode" games are also handled slightly differently with this enabled. So long as there are no other windows overlaying the game, they can also bypass the ''compositor'' and disable "V-Sync".
 +
: It's supposed to perform as well as "Fullscreen Exclusive Mode", and in one demo, it outperformed FSE Mode by a small amount.
 +
:* Solution-1: Disable Win10 "Full Screen Optimizations".
 +
:: Here's how to disable it by default: '''Windows Settings | Gaming | Game Bar'''.  The settings: "show game bar when I play full screen games Microsoft has verified" and "record clips, screenshots..." should both be OFF.
 +
:: Either that or you can do it individually in each game's properties.
 +
:* Related commentary:
 +
:: It also resets the "International Colour Consortium" (ICC) profile of the monitor(s) to default every time you start a ''fullscreen'' game or <Alt+Tab> to one or switch to "fullscreen mode". You would think that in trying to apply the advantages of ''borderless'' to ''fullscreen'' that they'd also make ICC profiles work in ''fullscreen''. But no, they make it even worse in that aspect.
 +
:: This setting, along with 4k, causes all kinds of scaling issues. Only 1/4 the game on screen, or green tint across the screen with wrong refresh rate.
 +
 
 +
<span id="Issue: Wounds don't appear on Actors"></span>
 +
=== Issue - Wounds do not appear on Actors ===
 +
After installing a Body, Armor, or Skin replacement mod, wound decals no longer appear on most enemies. When they do appear, it's only on the legs. This happens with non-humanoid NPCs like Bighorners as well.  The wound decals are supposed to come from mods like [http://www.nexusmods.com/newvegas/mods/57113/ IMPACT] and [http://www.nexusmods.com/newvegas/mods/34917/ Enhanced Blood Textures].
 +
 
 +
* Cause: The problem lies within NIF files for armors/outfits and creatures.  Each NIF has to be modified so that the main armor/creature ''NiTriStrips'' (or shapes) appear above all other ''NiTriStrips'' (like ''gore caps'' ) in the tree. Only then will decals appear correctly.
  
* Solution: Mod [http://www.nexusmods.com/newvegas/mods/48509/? "Improved Automatic Ironsight animations"]
+
: It's a HUGE amount of work because of the number of faulty armors (just vanilla; not including modded ones like "Type3" and "Roberts"), because sometimes you'll need to join meshes via a texture editor such as '''Blender''' in order to reduce the number of ''NiTri''s as only the FIRST 2-3 mesh shapes are used for decal placement.  By default, ''gore cap'' meshes are placed above main outfit meshes and are cut into multiple parts. Consequently wounds are not appearing.
  
=== Issue: First person camera is off center ===
+
:* Solution-1a: [http://forums.nexusmods.com/index.php?/topic/6044613-wounds-not-appearing-on-npcs/#entry54108463 Example] of corrected NIF files, explained by '''KiCHo666''':
* Cause: Your problem might be a result of changing the "Field of View" (FOV).
 
 
<blockquote>
 
<blockquote>
From [http://www.tweakguides.com/Fallout3_8.html TweakGuides]:
+
I joined all gore caps into one mesh (1 for torso caps, 1 for limb caps), joined all possible armor parts into one via Blender ('''Outfit1''' and '''Outfit2''' were separated because they use different texture paths.) and then reordered them via [http://niftools.sourceforge.net/wiki/NifSkope Nifskope].
:   fDefaultFOV=75.0000 - Shows the default Field of View in degrees for the game, which is 75 degrees. Changing the Field of View using this variable doesn't seem to work properly as it is not applied when the game starts, so instead you will need to use the FOV console command (See Console Commands section) each time you start them game to set a different field of view.
+
"Arms" mesh need to be separated for arms to appear in first person view.
 +
PipboyOn/Off are replacement meshes used when NPC has Pipboy equipped.<br>
 +
 
 +
After all that, wounds appear correctly in the game.<br>
 +
 
 +
However, for any addon body part, like heads, arms, other armor parts ... wounds won't appear no matter what.<br>
 +
 
 +
A friend here on '''Nexus''', '''VWgolfR1''', told me about that. So give kudos to him!</blockquote>
 +
 
 +
:* Solution-1b: ''No gore'' was a problem that was reported in the [http://www.nexusmods.com/newvegas/mods/35047/ Bouncing Natural Breasts] mod comments.  One solution is to use a "gore compatible" texture replacer like [http://www.nexusmods.com/newvegas/mods/34702/? Beware of Girl Type 3 HiRez HiDetailed Replacer].
 +
 
 +
<span id="Solutions to Mesh (Red "!" icon) or Texture (solid color) problems"></span>
 +
==Solutions to Mesh -Red Kite- icon or Texture -solid or off color- problems==
 +
 
 +
<span id="Issue: What are these ''Red "!" kite '' icons in the game?"></span>
 +
=== Issue - What are these -Red Kite- icons in the game ===
 +
This Red irregular "kite shaped" hexagon with a white "!" icon is the "missing mesh" indicator.
 +
 
 +
* Cause-1: You added meshes as "loose files" that replace the vanilla versions in the BSA files, but the game engine doesn't realize it needs to use them instead.
 +
:* Solution-1: Toggle "ArchiveInvalidation" off-and-on again in your mod manager.  This is discussed in detail in the[[#ArchiveInvalidation (by Manager)|ArchiveInvalidation (by Manager)]] sub-topic.
 +
 
 +
* Cause-2: Your load order is not sorted correctly.
 +
:* Solution-2a: Check that you have the vanilla game and Official DLC ESM files in the correct sequence.  Please see the "Vanilla "Load Order" section of the [[FNV_General_Mod_Use_Advice|FNV General Mod Use Advice]] article.
 +
 
 +
:* Solution-2b: Use [http://loot.github.io/ LOOT] to sort your "load order".  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 [http://www.nexusmods.com/newvegas/mods/34703/? 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 a 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. For the beginning mod user, it is essential to resolve most fatal mod conflict problems. 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.
 +
{{xEdit Exclusivity}}
 +
 
 +
* Cause-3: Different texture/mesh replacement mods can conflict with each other.  The "install order" can be the cause of the "missing mesh" indicator suddenly appearing, especially where things had been fine before adding the new mod.
 +
:* Solution-3a: Be sure you are using compatible meshes and textures.  See "Body Replacement Basics" in the wiki [http://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice FNV General Mod Use Advice] article.
 +
 
 +
:* Solution-3b: As a general rule, install replacement mods that predominately affect the "background" on the horizon or mountains first, then those that affect the mid-ground (like billboards and trees/flora), with those affecting things you normally don't see well until in the mid- to foreground (like creatures) last.  Some experimentation with the "install order" may be necessary.
 +
:: Remember that "view while distant" (VWD) ''objects'' require "_far.nif" files and rebuilding of the ".lod" quadrants for ''landscapes'' with [http://www.nexusmods.com/newvegas/mods/58562/? FNVLODGen] after updating the "load order".  See the [http://web.archive.org/web/20170713081056/http://www.darkcreations.org/testg/wiki/Category:VWD-OB "TESTG: VWD/LOD Overview"] page to understand the issues and for details on resolving them.
 +
 
 +
* Cause-4: The path to the mesh and/or texture file must be in "relative" format to the "Data" folder (i.e. "textures\<SpecificSubFolderPath>" rather than "absolute" format (i.e. "C:\<PathToGameFolder>\Data\textures\<SpecificSubFolderPath>").
 +
:* Solution-4: See the wiki article [[How_to_fix_hard-coded_texture_paths_in_NIF_files|How to fix hard-coded texture paths in NIF files]].
 +
 
 +
<span id="Issue: What's with these ''Solid Green'' billboard signs in the distance (LOD)?"></span>
 +
 
 +
=== Issue - What is with these ''Solid Green'' billboard signs in the distance ''aka LOD'' ===
 +
* Cause:  The underlying problem is how the game handles distant 2D objects generally called "trees" or "billboards".<br>
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 30px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">LOD in general is what you see in the distance, beyond the '''uGridsToLoad''' setting value. Bethesda uses static LOD which means that LOD information is prebuilt and doesn't change when mods modify objects in game. Some mods include updated LOD files to address this issue, but they are rare and usually incompatible with each other and require compatibility patches of their own. Those LOD files are generated with GECK which is quite complex procedure unaccessible by majority of users. [http://www.nexusmods.com/skyrim/mods/62698/? TES5LODGen/xLODGen] (the latest version just needs to be renamed to what your game is expecting) tries to address this issue by providing a simple one-click automated LOD files generation for the current load order of user, taking in account all mods that have content visible from distance.<br>-(Source: xLODGen description.)</div>
 +
 
 +
:: The game engine treats distant 2D "vegetation trees" and "sign billboards" identically beyond the immediate foreground as "level of detail"(LOD) distant "tree" objects.  The resulting "images" collectively make up "billboards" which are combined into an "atlas".  '''xLODGen''' can combine billboards from different mods into new atlases when you select the "Trees LOD" option.  When you run '''xLODGen''' after updating the "load order", it will replace any missing "billboard" LOD textures to this "solid green" color during LOD generation.  It also lists these "missing" textures in the xLODGen log file.
 +
 
 +
<div name="Note Box" class="boilerplate metadata" id="Notice Box"
 +
style="margin:0px 10px 10px 30px;border:1px dashed #DAA520;color: lightgray;
 +
background-color:#333333;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">"Atlas" means that there are several separate images located inside a single image. Trees in the distance are just flat images of trees displayed from atlas texture. The usage of single texture in [game] for all trees is performance friendly, but unfortunately very problematic for mods that change tree models or add new ones. To update LOD images, even if it is only a single tree, the mod must include the whole atlas texture along with images for all other trees even if they are unchanged. The other problem of trees LOD is that a single atlas texture is used for all worldspaces [in the Gamebryo engine].<br>-(Source: xLODGen description, edited from game specific for more generic purposes.  See the game specific version download pages of '''xLODGen''' as to specific differences.)</div>
 +
 
 +
:: (For more details about this, please see the article [http://www.reddit.com/r/skyrimmods/comments/466vss/the_difference_between_lods_and_billboards/ The difference between LODs and Billboards explained] on Reddit's Skyrim forum.  Note there are some technical differences in how this works between Skyrim (Creation) and Oblivion/Fallout (Gamebryo) as they use different game engines.<br>
 +
:: See this [http://afkmods.iguanadons.net/index.php?/topic/4051-wipz-tes5lodgen-for-trees-lod/ TES5LODGen for Trees LOD] thread for information on how billboards work in TES5LODGen.)
 +
 
 +
:* Solution-1a: The mods with LOD additions (such as [http://www.nexusmods.com/newvegas/mods/61206/? LOD additions and improvements] by '''tomzik''') are highly recommended to be installed before LOD generation as they provide extra distance models missing in the vanilla game.
 +
 
 +
:* Solution-1b: Re-run '''xLODGen''', enabling the "Trees LOD" option.  You may also find that adjusting the game INI files '''uGridsToLoad''' setting value to a larger "odd number" (e.g. 7, 9, 11) may help with the issue of "pop-in" (where objects such as "sign billboards" appear "green" until you are much closer to them).  However, note that you may want to also increase the '''uExterior Cell Buffer''' value to accommodate the greater cell data and prevent crashes and stuttering. <span style="margin:0px 10px 10px 0px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Larger values have an impact upon performance.  And once you save the game with a higher setting, you cannot lower it again except by starting a new game.</span>  (See the related entries in the [http://www.tweakguides.com/Fallout3_9.html Fallout TweakGuides] for details.)
 +
 
 +
:* Solution-1c: The tool [http://www.nexusmods.com/skyrim/mods/60733/? Tree LOD billboard creator for xLODGen] by '''zilav''' can be used to "grab an image of a tree directly from preview/render window of official editor (Creation Kit, GECK and Construction Set) or NifScope, calculate alpha mask, scale, adjust brightness and contrast, generate mipmaps and save ready to use DDS billboard image in a single click."  Please read the "usage guide" on the download page carefully.
 +
 
 +
<span id="Issue: Find the source mod-index of an object in-game"></span>
 +
 
 +
=== Issue - Find the source mod-index of an object in-game ===
 +
This is often desired to determine the source of a missing texture (solid color) or mesh (the White "!" on a Red background symbol in game), or when the file for one has been overwritten producing the "wrong texture".
 +
* Cause: The only way to identify a "Reference Object" (one that has been placed into the game world and begins with the "mod-index" of "FF") is to use the console to identify an object in-game.  "Usable objects" that can be picked up must have the object in a container's inventory ("the Player" {your character}, another Actor such as a NPC or creature, or a container such as a cabinet or chest) in order to obtain their "Base-ID".  "Static objects" like signs or billboards that are not movable can be targeted directly to obtain their "Ref-ID", which you will need to turn into a "Base-ID".
 +
: For more on the distinctions between the various terms associated with "Reference Objects" and "Form-IDs", please see the 'GECK Form-ID, Base-ID, Ref-ID, and Editor-ID' section in the wiki [http://wiki.nexusmods.com/index.php/Getting_started_creating_mods_using_GECK Getting started creating mods using GECK] article.  These distinctions are VERY important to understand.
 +
 
 +
:* Solution:
 +
:# Open the in-game console (default is the <~> key).
 +
:#* For "static objects", < Click > on the target.  This is all that is needed. Note this will be a "Ref-ID".
 +
:#* For "usable objects", < Click > on the PC, NPC, or container and enter "showinventory" in the game console.  Note this will be a "Base-ID".
 +
:# The Form-ID (e.g. "001735E4") will be displayed at the top of the screen.  See this article [http://fallout.wikia.com/wiki/Help:Form_IDs Help:Form IDs] for an explanation of how to interpret the Form-ID.  In short, the first two characters are the "load order index" (aka ''mod index'') (in [http://en.wikipedia.org/wiki/Hexadecimal hexadecimal], starting with "00").  The ''mod index'' tells you the source mod's position within the "load order".
 +
:#* If you have '''NVSE''' installed and the '''plugin file name''', then you can use the console command ''GetModIndex "<pluginname>.ES<M|P>"'' (double quotes required) to get the "load order" ''mod index'' while in-game (i.e. ''GetModIndex "DeadMoney.esm"'' should return "01").
 +
:#* The '''NVSE''' console command "''GBO''" (GetBaseObject) after selecting the item will return the "base object id" (Base-ID).  The Form-IDs listed in the Object window of GECK are "Base-IDs". A "Base-ID" is only associated with an object template ''in the editor'', never with an instanced object in-game.  Note: Will return the ''leveled'' character/creature form if called on references spawned by a "leveled list". Use "''GBF''" (GetBaseForm) to return the NPC/creature "Base-ID" instead. Source: [http://geck.bethsoft.com/index.php?title=Glossary GECK Wiki].
 +
:#* If you have the '''"Lutana"''' or '''"JIP LN" NVSE Plugin''' installed, you can use it's console command `'''''search "<item name>"'''''' (double quotes required), which will show you a list of matching items with Form-IDs.
 +
:#* Note that a "00" ''mod index'' means it's from the game master file (i.e. FalloutNV.ESM).
 +
:#* DLC masters follow the game master, and should be in order of release.  (See [[FNV_General_Mod_Use_Advice#Vanilla_.22Load_Order.22|Vanilla Load Order]].)
 +
:#* The ''mod index'' for other plugins may change as their position on the "load order" changes due to the addition or removal of others. 
 +
:#* The "FF" index means it is a "spawned" character or item, which happens when you place or drop the item to the ground in the game-world.  This ''mod index'' is never that of the "source mod".  It's a "Ref-ID".  (These get included in the save game file.)  You will need to use the NVSE "GBO" or "GBF" command to get it's "Base-ID" which should contain the "mod-index" of the "source mod".
 +
:# To determine the source of conflicts:
 +
:#:* Once you have the Base-ID, load your entire "load order" into [http://www.nexusmods.com/newvegas/mods/34703/? FNVedit], enter the Base-ID you found (e.g. "001735E4") in that field (upper left corner of FNVEdit), press < Enter >, and in the right-hand pane select the "View" tab.  (Note that a "Ref-ID" beginning with "FF" will not work for searching purposes.  You need to determine the "Base-ID" using NVSE "GBO" or "GBF" first.)
 +
:#:* This will now show you ALL the plugins which touch that record, in the order in which they do so.  The last (right-most) is the one that "wins" the conflicts (red backgrounds) for that record.  All you really need is to see which plugin (column) is the winner.
 +
:#:* Note that you cannot use a "Ref-ID" with the "player.additem" console command.  It requires a "Base-ID".
 +
:#:* "Ref-IDs" will be located in the left-hand pane under the "World" category, and once found their record information in the right-hand pane will tell you the "Base-ID" they are a reference back to.
 +
{{Lutana NVSE Plugin Status}}
 +
 
 +
<span id="Issue: Fix a "missing/solid color" texture problem"></span>
 +
 
 +
=== Issue - Fix a ''missing or solid color'' texture problem ===
 +
* Cause-1: the texture (DDS) file is missing, incorrect, can't be located, or corrupt.
 +
:* Solution-1a: This is a multi-part procedure presented in increasing level of difficulty.  Details in other articles or sections of this guide cover those aspects in more depth, so read everything first before attempting.
 +
 
 +
:# Identify the load order "mod index" of the plugin the object in question belongs to using the procedure laid out in [[#Issue:_Find_the_source_mod-index_of_an_object_in-game|Issue: Find the source mod-index of an object in-game]] entry in this guide.
 +
:# Make sure you have installed all the "art assets" of that plugin (that is: any ESM and BSA files required).  Check the mod "requirements" carefully.  Sometimes these are a separate "mod" or file download.
 +
:# Toggle "ArchiveInvalidation" off-and-on again.
  
:   Update: It has been discovered that by inserting the line fDefaultWorldFOV=75.0 at the bottom of the Display section of the Fallout.ini file, and assigning it a value equal to the FOV you want, you can now permanently change the default Field of View in the game. Remember however that if you change the default FOV, you may also need to change the FOV for other screen elements - see the fRenderedTerminalFOV and fPipboy1stPersonFOV commands below. Note also that you can alter the fDefault1stPersonFOV=55.0000 value to alter how much of your body/weapon is shown in front of you (Fallout.ini).
+
:* Solution-1b: You have a mod conflict that is overwriting that object's record, which requires a change in the "load order" sequence or a "merge/bash patch file" to correct; though this is much less likely for a "missing texture only" problem.  (Please see the [[FNV_General_Mod_Use_Advice#Third Rule: The Rule of One|Third Rule: The Rule of One]] and [[FNV_General_Mod_Use_Advice#Merge_Patch_File|Merge Patch File]] sections of the wiki [[FNV_General_Mod_Use_Advice|FNV General Mod Use Advice]] article.)
</blockquote>
 
  
* Solution: Other than adjusting the various FOV settings, try tweaking the following default values (which set the camera position relative to the head node in 1st person view) in the INIs [General] section:
+
:* Solution-1c: If neither of those solutions is enough to fix the problem, then you have to determine if the texture (DDS) file is missing or corrupt.
*: Make backups of the INIs before changing them.
+
:# Examine the mod archive package to check if the folder where it got placed is somewhere the engine isn't looking for it.  You can manually drag the folders to the correct locations, or repackage the archive to avoid that problem against the next time you need to install it.
<blockquote>
+
:#; For example: In the case of "Weapon Retexture Project" (WRP) v1.95, 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; with folder names such as "Textures" or "Meshes" (etc.), 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 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.  Sometimes it's "Data" so you end up with "Data\Data" which is also unexpected.)  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 folders into the game "Data" folder.<br>
:   fCameraPosX=0.0
+
:#: BTW: 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.  Recommend renaming such to "<mod_name>_ReadMe.txt" so you know which package they came from, and place them all in a "Docs" folder for easy access, but it's not a requirement.  (Many authors 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 (i.e. "Readme.txt"), so consequently only the last installed exists.)
:   fCameraPosY=9.5
+
:# Examine the plugin in [http://www.nexusmods.com/newvegas/mods/34703/? FNVEdit].  (Note that the "mod index" will be different because you probably won't be loading all of the plugins from your "load order".)
:   fCameraPosZ=6.0
+
:# Locate the object, using the "Form-ID" that was returned when you identified the object in ''Solution-1a''.
:   bUseThirdPersonArms=1
+
:# Find the "model" (MODL/NIF) filename and path of the object in question.  (The "texture file" name and path is located within the model/mesh "NIF" file.)
:   bTPArmsEnableIronSights=1
+
:# Use [http://niftools.sourceforge.net/wiki/NifSkope NifSkope] to open that NIF file.
</blockquote>
+
:# See the wiki article [http://wiki.nexusmods.com/index.php/How_to_fix_hard-coded_texture_paths_in_NIF_files How to fix hard-coded texture paths in NIF files] for the procedure to locate the texture file entry within '''NifSkope'''.  (The path needs to be "relative" instead of "absolute"/"hard-coded" in order to be found, which is what that article covers.)  But in short form the procedure is:
 +
:#* Open the NIF file in '''NifSkope'''.
 +
:#* Click on the part you want the texture for; it will highlight it in the ''Block'' list.
 +
:#* Expand it and highlight ''BSShaderPPLightingProperty''. Expand that.
 +
:#* Highlight ''BSShaderTextureSet''.
 +
:#* In ''Block Details'' you will see textures (DDS files). Expand it.
 +
:#* There you will see the paths to the textures used by that mesh.
 +
:# Once you have identified the texture (DDS) file in question, first ensure it is present.  If it is, then you want to replace it as it might be corrupt.  Either way, install or replace by extracting that file from the plugin archive (or extract the DDS file from the appropriate BSA with [http://www.nexusmods.com/newvegas/mods/54991/ FOMM]) and overwrite the file (if any) in that location.
 +
:# Toggle "ArchiveInvalidation" off-and-on again.
 +
:# Test the result.
  
=== Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed ===
+
:: If nothing changes, then you most likely identified the wrong object and need to start over.
* Cause-1: Companions impose heavy script processing penalties.  More than two companions, while possible, will definitely cause lag according to the game developers.  The game is unable to tell if a vanilla companion is "actually with you" or merely "befriended" but sitting elsewhere (such as in the Lucky 38 suite).
 
  
:* Solution-1: Release ("part ways" from) unused companions to return to where they were recruited. If you are not informed you have lost the Perk granted by that companion, you have not actually "released" themThere are "companion dismissal terminals" found in the game to help with this for companions, even those not currently with you.  One is found in the Lucky 38 Casino by the Casino floor elevator and another in front of the Gun Runners HQ shack outside Freeside's East gate.
+
* Cause-2: Sometimes installing a mod can replace a vanilla "normal map" (aka "bump map") or fail to include one, which in turn causes some strange effects such as "transparency" and problems with texture Alpha channels (brightness).
 +
:* Solution-2: Removing the mod should restore things, but you have to toggle "ArchiveInvalidation" off-and-on-again once it is uninstalledIf a loose file was actually overwritten, you will need to "verify local files" or re-install the other mod to restore it.
  
* Cause-2: The stutters come from the game looking for control inputs from the attached game controller device first, then the keyboard/mouse though both are enabled.
+
* Cause-3: Failure of the mod to include a "mipmap" (which includes the same image at various resolution sizes) so it's default size fails to match that of your game settings.
 +
:* Solution-3a: Try changing the "Texture Size" to "LARGE" in the main game "Settings | Display" menu and "exit to the desktop" to restart the game session.  If that doesn't resolve the problem, try gradually lowering the "Texture Size" settings.  While this will eventually match the size of the mod image allowing to appear correctly, it is likely to causes problems with other mods which don't have mipmaps either and use a different default size.  It's best to bring the matter to the attention of the mod author.
 +
:* Solution-3b: Mipmap generation is a "properties setting" in the "Mesh Editor" (e.g. '''Blender''') when creating the NIF file.  You can try to rebuild the NIF file to also produce a "mipmap" file, but that process is beyond the scope of this article.
  
:* Solution-2: Disconnect the controller if you are not using it.  Regardless, in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV\Fallout_Prefs.INI" file look for "bGamePadRumble=" and ensure it is set to "0".
+
<span id="Issue: Pink Screen or textures (VRAM limitation)"></span>
  
=== Issue: Pink Screen or textures ===
+
=== Issue - Pink Screen or textures ''aka VRAM limitation'' ===
 
* Cause-1: Usually this means you are running out of graphics VRAM (the physical memory on your video card); typically from too many High Resolution Texture replacement packs.  These pink textures can show on faces, hands, and hairs, but also can happen with entire loading screens.  When you start seeing this "pink stuff", a CTD is just around the corner.
 
* Cause-1: Usually this means you are running out of graphics VRAM (the physical memory on your video card); typically from too many High Resolution Texture replacement packs.  These pink textures can show on faces, hands, and hairs, but also can happen with entire loading screens.  When you start seeing this "pink stuff", a CTD is just around the corner.
  
* Cause-2: If you are on Windows 10 the game can handle less "High Quality" / "High Definition" textures than in Windows 7 due to how Win10 handles DirectX 9 games.  The video RAM gets locked at 4GB maximum (even if you have a TitanZ card with 12 GB on board), thanks to Microsoft's implementation of DirectX 9 games in their latest OS (Win10 at the time of this writing).  So in short, if your game ran fine in Win7, it will and cannot handle as many textures as it could before upgrading.  This can cause your symptoms of pink textures or worse a CTD if you had more than 4GB total of video memory loaded under Win7.
+
* Cause-2: If you are on any version later than Windows 7, the game can handle less "High Quality" / "High Definition" textures due to how the Direct3D API reports available VRAM''"The API in question simply reports to the app an estimation of how much memory remains available to allocate. On Windows 7, when more than 4GB are available, this API will not report accurate information. For example, if 4.1GB of memory are available, the app will see 0.1GB available. […] On Windows 8 and newer, this API will only report 4GB. Up until the change in this Fall Creator’s [sic] Update, once the counter reports 0 you can expect future memory allocation requests to fail."'' - '''Jesse Natalie''', Senior Software Engineer in the Direct3D team at Microsoft as reported to [http://www.neowin.net/news/windows-10-fall-creators-update-fixes-the-directx-9-memory-allocation-bug Neowin.net].  So in short, if your game ran fine in Win7, it will and cannot handle as many textures as it could before upgrading to later versions of Windows or video cards with more than 4GB of VRAM.  This can cause your symptoms of pink textures or worse a CTD if you had more than 4GB total of video memory use loaded under Win7.<span style="margin:0px 10px 10px 10px;border:1px solid #00C600;color: green;
 +
background-color:#fff5f5;padding:3px;
 +
word-wrap: break-word;      /* Internet Explorer 5.5+ */
 +
">Note this VRAM limitation is fixed in Windows 10 Version 1709 (aka the Win10 "Fall Creator's Update") which started it's release rollout on 17 Oct 2017.</span>
  
:* Diagnostic: You can see if reducing the in-game "texture quality" setting from "High" to "Low" makes a difference, or if reducing your screen resolution down to 800x600, or both, makes any difference to confirm the above are the cause.
+
:* Diagnostic: You can see if reducing the in-game "texture quality" setting from "High" to "Low", or if reducing your screen resolution down to 800x600, or both, makes any difference to confirm the above are the cause.
  
:* Solution: There are several things you can try:
+
:* Solution 1-2: There are several things you can try, individually or in combination, in order of effectiveness:
 +
::* Implement "ENBoost" (which is NOT the "ENB Series" graphics post-processor with it's attendant FPS hit) if you have more than 4GB of system RAM.  See the [http://wiki.step-project.com/Guide:ENB#ENBoost S.T.E.P. ENB Guide] and [http://wiki.step-project.com/ENBoost#Recommendations S.T.E.P. ENBoost QuickStart] pages.
 
::* Uninstall some HD texture replacement packs.
 
::* Uninstall some HD texture replacement packs.
 
::* Run the game at a lower screen resolution.
 
::* Run the game at a lower screen resolution.
::* Reduce the texture resolution down by half each time (i.e. from 4096x4096 to 2048x2048, 1024x1024, or 512x512).  See the Utilities "DDSOpt" and "Optimizer Textures" on the [http://www.darkcreations.org/testg/wiki/Utilities TESTG Utilities] page.
+
::* Reduce the texture resolution down by half each time (i.e. from 4096x4096 to 2048x2048, 1024x1024, or 512x512).  See the Utilities "DDSOpt" and "Optimizer Textures" on the [http://web.archive.org/web/20170713081056/http://www.darkcreations.org/testg/wiki/Utilities TESTG Utilities] page.
 
::* Upgrade your video card.  However, note the limitation in Windows 10 in "Cause-2" above.
 
::* Upgrade your video card.  However, note the limitation in Windows 10 in "Cause-2" above.
  
 
::* For advanced users: If you have a Windows 10 Education, Professional, or Enterprise edition you can use the included Win10 Hyper-V system and try running the game in a Win7 "virtual machine".  See [https://msdn.microsoft.com/virtualization/hyperv_on_windows/quick_start/walkthrough_compatibility HyperV on Windows compatibility] for the hardware requirements and a walk-through of the installation process.  Note this requires you to have or obtain an ".iso" file of the desired OS install media.  (If none of this option makes sense, you probably don't want to mess with it.  Otherwise, educate yourself as it is beyond the scope of this wiki.)
 
::* For advanced users: If you have a Windows 10 Education, Professional, or Enterprise edition you can use the included Win10 Hyper-V system and try running the game in a Win7 "virtual machine".  See [https://msdn.microsoft.com/virtualization/hyperv_on_windows/quick_start/walkthrough_compatibility HyperV on Windows compatibility] for the hardware requirements and a walk-through of the installation process.  Note this requires you to have or obtain an ".iso" file of the desired OS install media.  (If none of this option makes sense, you probably don't want to mess with it.  Otherwise, educate yourself as it is beyond the scope of this wiki.)
  
=== Issue: Black Screen on startup ===
+
* Cause-3: When this occurs with faces, you may need to adjust profile settings in ''Fallout.INI'', ''FalloutPrefs.INI'', and ''Fallout_default.INI''.  Note some Character overhaul mods change the mesh for faces as well and may require additional setting adjustments.  Read their documentation carefully.
* Cause-1: Usually if the game "freezes" but doesn't CTD during the loading screens, it's due to a missing or incorrectly referenced "master file".  Usually this is a file with an ESM extension, but less commonly might be one with an ESP extension.  (It is a "flag" internally in the file header that makes a file a "master"; not the extension.)
+
:* Solution-3: Set
 +
<pre> [General]
 +
bLoadFaceGenHeadEGTFiles=1</pre>
 +
 
 +
<span id="Issue: "ShowRaceMenu" / Changing Character / Uninstalling a "custom race" problems"></span>
 +
 
 +
=== Issue - '''ShowRaceMenu''' or Changing Character or Uninstalling a ''custom race'' problems ===
 +
Example: Uninstalled "Fallout Character Overhaul" (FCO) in mid game, but forgot to switch to a vanilla race first and got stuck in the ground and constantly have to use the "tcl" console command to rise up vertically.  Tried re-installing FCO and using the "ShowRaceMenu" console command but it CTDs upon loading.
 +
 
 +
* Cause-1: Failure to provide a "replacement" for fundamental features the game is expecting (such as switching to a vanilla "race" prior to removing a "custom race" mod) will cause a CTD, similar to a "missing master" problem.
 +
 
 +
:* Solution-1a: Basic troubleshooting on the "CTD upon loading" symptom in the example case identified that the re-installed plugin was not enabled as an active plugin.  (This permitted the use of the "ShowRaceMenu" command.)
 +
::* In general, uninstalling any mod from an active game is going to cause problems.  Many will not be fully resolveable by simply re-installing the mod.  Anything that has a "FormID" with the plugin index of the removed mod will be purged when the save game is loaded (the "missing content" message), but some elements such as scripts might not.  Understand what yo