Crash game and texture bug

[savanah007]

Hello, i have installed mod gameplay and graphic but i have a lot of crash every where and when i exit a house for exemple. i have texture bug to, like vegetation or some objet or wall become back, it fix when i get a fresh load with get out of house ( if i don't get crash ^^ )

 

this is my mod pluggins :

 

falloutnv.esm
DeadMoney.esm
HonestHearts.esm
OldWorldBlues.esm
LonesomeRoad.esm
GunRunnersArsenal.esm
ClassicPack.esm
MercenaryPack.esm
TribalPack.esm
CaravanPack.esm
Interior Lighting Overhaul - Core.esm
Interior Lighting Overhaul - L38PS.esm
Project Nevada - Core.esm
Project Nevada - Equipment.esm
Project Nevada - Extra Options.esm
FCOMaster.esm
Project Nevada - Rebalance.esp
Project Nevada - Cyberware.esp
Project Nevada - Cyberware Additions.esp
Project Nevada - Rebalance Complete.esp
Project Nevada - All DLC.esp
EVE FNV - ALL DLC.esp
vault22FloralOverhaul.esp
Interior Lighting Overhaul - Ultimate Edition.esp
ILO - GS Shack.esp
ILO - PipBoy Light.esp
FCO - NPC Changes.esp
FCO - OHSB NPC Edits.esp
TLD_Travelers.esp
NukaCola-Ojo.esp
Vurt's WFO.esp

I use Boss for load order

i use nvac anti crash

i use nvse

 

If yoiu can help me i will be grattfull to you :)

 

Sorry for my english if i miss the language ^^

 

 

[dubiousintent]

BOSS is not publicly maintained for FNV. (I am aware of one person who is maintaining a private master file, but they do not generally make that public that I know of; and I don't presume to offer their services without their permission.) You need to use LOOT with FO3 and FNV (and generally later Bethesda games) instead.

 

Please read the wiki "FNV General Mod Use Advice" article. It covers all of that, including links to LOOT.

 

All of the following may not apply to your specific situation, but are worth repeating anyway. I've highlighted things to which I think you need to pay particular attention.

* Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so.

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

* Are you running Win10? Did you get the "Fall Creator's Update" (FCU aka "RedStone 3")? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (and other "heap size") entries in the 'Solutions to Performance problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

The FCU update was released in mid-November 2017, so a "brand new" system probably did not come with it installed. However, the default configuration is usually to have OS updates automatically installed. (Those usually start being distributed on the second Tuesday of each month, but may take a week or more to get to everyone.) See the MS "Get the Windows 10 Fall Creators Update" article for how to check your version release and manually pull down the update if necessary. It is important to keep your OS always "up to date" to prevent malware infections.

* If you are suddenly having a "slowdown" or lag; or a lack of sound; or problems getting NVSE to load, or really anything new unexpectedly, please see the 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. This may be due to a Windows Update for the "Meltdown and Spectre Vulnerabilities".

* Are you using the 4GB Patcher? If not, please see the 'Maximizing use of memory' section of the wiki "FNV General Mod Use Advice" article.

* If you are using the full 4GB of memory, most likely your CTD problem (now or in the future) is the default "heap size" is too small. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* 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.

* "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than both of the plugins they are designed to make compatible. ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. "LOOT" does a good job of determining those basic orders. Getting the "load order" incorrect will cause "Missing Master" errors as well.

* Don't install compatibility patches for mods you do not have installed/active (e.g. get rid of any "TTW" patches if you aren't running TTW).

* 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.

* Do not use an "Auto-purge" mod for game play. (That was old advice from before we knew better.) They are designed for debugging by mod creator's only, according to the author of the JIP extensions to NVSE. See the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu', "Cause-2", "Solution-3" entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for the game settings that do the same job.

* Please see the paragraph about "auto-saves" under the 'Essentials for Getting Started' section of the wiki "FNV General Mod Use Advice" article. If you have been using the built-in "auto-save" feature and you get the endless "roulette wheel" when loading a save game, then your current save game file is corrupted and you will have to either go back to a save before the corruption occurred (hard to tell) or start over.

* You really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.

* Because "Texture/Mesh" replacement mods replace vanilla versions of those files, you absolutely have to toggle "ArchiveInvalidation" off-and-then-on again after installing or removing one of them so it recognizes that there are loose files (added by the mod) which have to be used in place of the vanilla files in the BSA files or are no longer there and the BSA files should be used instead. That failure to toggle is the most common reason behind most "not working problems". This is usually evidenced by red "!" icon for missing meshes, and solid colors for missing textures. Please see the 'ArchiveInvalidation (by Manager)' section and also see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

[Edit: Added "ArchiveInvalidation" info.]

 

-Dubious-

[savanah007]

Thx you for the good guide you are :)

 

I make a fnve clean and a wyrebash patch but that was dosent work, actualy my game was corrupt so i make a clean reinstal and now it work good with lot of other mod.

 

Thx you again.

 

Have a nice day.