Difference between revisions of "Template:NVSE Configuration"

From Nexus Mods Wiki
Jump to: navigation, search
(Detail: update)
m (Detail)
Line 37: Line 37:
 
Note that writing a file to disk is one of the slowest things a program will do.  Having "logging" enabled will have some impact on performance, the degree of which will depend upon your system.  It is recommended to leave "EnableGameErrorLog=0" and set it to "=1" only when and as long as you need logging enabled.
 
Note that writing a file to disk is one of the slowest things a program will do.  Having "logging" enabled will have some impact on performance, the degree of which will depend upon your system.  It is recommended to leave "EnableGameErrorLog=0" and set it to "=1" only when and as long as you need logging enabled.
 
</div>
 
</div>
::: See also "Solution-2a" 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]] entry in the "Fallout NV Mod Conflict Troubleshooting" guide.
+
::: 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]] entry in the "Fallout NV Mod Conflict Troubleshooting" guide.
 
</onlyinclude>
 
</onlyinclude>
  

Revision as of 05:57, 20 April 2017


Overview

This procedure a template so it may be included in several instances in the article "Fallout NV Mod Conflict Troubleshooting".

Programs and Tools

  • A plain text editor like Windows Notepad.

Detail

When installing New Vegas Script Extender (NVSE), the nvse_loader.exe file should be in the game root folder: i.e. "<Steam install path>\steamapps\common\Fallout New Vegas"), so it's along with the FalloutNV.exe file. However, just unpacking the NVSE archive package to the "Fallout New Vegas" folder may not create a "Data\NVSE" folder or the "Data\NVSE\Plugins" sub-folder upon installation unless you tell it to include sub-folders when doing so. If not, you will have to do so manually. It definitely does not create a configuration file or automatically enable it's log files (which will be found in the game's root folder). You need to do so yourself, using any plaintext editor such as Windows NotePad. Supplemental NVSE Plugins such as JIP, Lutana, MCM, NVAC, or NVSR should go into the "Data\NVSE\Plugins" folder.
  • If not present, manually create folder "NVSE" under the game "Data" folder (at the same level as the "Meshes" and "Textures" folders), and then "Plugins" under the "NVSE" folder.
  • Make sure "hide known file types" is disabled in Windows Explorer's "Folder" options, or your new INI file in the next step will have a hidden ".txt" extension which you don't want.
  • In the folder "Data\NVSE" create a new text file and name it "nvse_config.ini".
  • Copy and paste the following into "nvse_config.ini":
[Logging]
EnableGameErrorLog=1
[RELEASE]
LogLevel=1
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 at least three files: "falloutnv_error.log", "falloutnv_havok.log", and "nvse.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. The "nvse.log" is helpful to identify problems with NVSE itself, and plugins that rely upon it.
The warnings are supposed to be found in "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV\warnings.txt", but this may be dependent upon the "log level" in the "nvse_config.ini". The default is level "1" and there is no "warnings.txt" file created; but it goes up to level "5" (debugging) with increasing verbosity.
See also entirety of the Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu entry in the "Fallout NV Mod Conflict Troubleshooting" guide.


References

Nexus wiki articles referred to by this article:

Nexus wiki articles that refer to this article: