Jump to content

Crashing after 1-2 minutes. Black Guns


Prenihility

Recommended Posts

"Nevada Skies - TTW Edition" is listed in your very first post. Supposedly that was your "load order" of "active mods" for that profile. We can only go by what you tell us, and using more than one of those three "Nevada Skies" files would be a serious problem. (A list of "installed mods" does not mean they are all "active" with MO. Only the ones listed in the "profile" you are using are currently "active". If you do not understand this, read / view a tutorial on your manager. It is important to know how it works.)

 

"TTW" stands for "Tales of the Two Wastelands", which is an overhaul / conversion that allows FO3 (i.e. "the East Coast") to run on the FNV game engine.

 

* Move any "inactive" plugins out of the game "Data" folder. They count against the "plugin cap" because they get loaded by the game engine if found, and can cause "Missing Master" problems. Please see the wiki "Missing Masters" article if you get that error message. If those plugins without the "mod index" numbers are "deactivated by the "Bash Patch", then you failed to have them "ghosted" by "Wrye Bash/Flash" when you built your "Bashed Patch". Please see the wiki "Bashed Patch file with Marked Mergeables" article.

* Don't install every optional file for a mod. Read the install instructions carefully. Optional files need to be selected on a "case by case" basis. For example: with any mod you usually only need one ESP (and possibly one ESM) "base" file depending upon whether you have all the DLCs active or not. Only if you don't have them all active do you need to install any specific DLC versions if there is an "Ultimate Edition/All/Merged DLC" version.

Our current understanding is that if you have a plugin (active or not) installed in the "Data" folder, the game engine loads it up into memory when it starts. This can cause problems such as conflicts, even though the plugin is not "actively" used by the game; and it does count against the "plugin cap". However, the plugin cap is mostly a guideline as to "more than this the game starts to have memory issues" and it really depends upon the mix of plugins and textures involved and how much memory they collectively consume as to when that occurs. You have a limited amount (4GB when patched; 2GB by default) of memory available to the game and every plugin of any nature consumes some of that memory. Add to this that the game can be shown to have "memory leaks" which eventually cause it to CTD.

Additionally, any time you remove a plugin from your current play-through you risk corrupting your save game files. This is because they typically store information there as to the state of their variables and quests. If you picked up a unique (non-vanilla) item added by a mod, that item (like any item you pick up) is stored in the save game, but also requires the plugin it came from to be available as that item's "source records". Hence the general advice to never remove a plugin from your current game.

So, convenient or not, uninstall those inactive plugins. Once you do play them (as "active" in your "profile"), leave them in your game or start a "new" one. At the very least, if you think they are "completed" and you have not kept any of their "unique" items, make sure you know which was the last save game prior to removing the mod and are prepared to have to revert back to it when things go wrong later on (no matter how many hours later that may be). Perform a "Clean Save" (see the 'Clean Saves' section of the wiki "FNV General Mod Use Advice" article) after removing the plugin and before resuming play, even once you go back to a previous save.

Once that is done, if you are still having problems, see the 'Solutions to Starting the game problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...