Crashing/Infinite loading screen coming out of doc's house on new game. Have mods/bashed patch via wyre flash

[TheHoneyDipper]

0 0 FalloutNV.esm

1 1 DeadMoney.esm

2 2 HonestHearts.esm

3 3 OldWorldBlues.esm

4 4 LonesomeRoad.esm

5 5 GunRunnersArsenal.esm

6 6 ClassicPack.esm

7 7 MercenaryPack.esm

8 8 TribalPack.esm

9 9 CaravanPack.esm

10 a YUP - Base Game + All DLC.esm

11 b SomeguySeries.esm

12 c New Vegas Redesigned 3.esm

FCOMaster.esm

13 d AWorldOfPain(Preview).esm

14 e AWOPDeadMoney.esm

15 f Gomorrah Redesigned v2.esp

YUP - NPC Fixes (Base Game + All DLC).esp

16 10 New Vegas Redesigned 3.esp

17 11 M0rk's Lighting.esp

18 12 AWOPDeadMoneyVendorPatch.esp

19 13 Companion Sandbox Mode3.esp

20 14 NewVegasBounties.esp

21 15 NewVegasBountiesII.esp

22 16 populatedcasino-light.esp

realistic headshots.esp

23 17 Immersive Karma.esp

GRA-WRP-Patch-Two_Unofficial.esp

24 18 ELECTRO-CITY - Imaginator.esp

25 19 AWOP Interim Fixes.esp

26 1a Goodsprings Shack.esp

27 1b Improved Throwing1.esp

28 1c CASM.esp

29 1d Bashed Patch, 0.esp

FCO master is deactivated because of confliction with redesigned 3. GRA and YUP and Headshots were merged with the bashed patch. Trying to follow directions and can't even get out of doc's house. Supremely frustrating. I have 4gb patch and nvse as well. What else can I do?

[dubiousintent]

Those "inactive" plugins need to be moved out of the game "Data" folder (or at least made "unrecognized"). The game is still loading them, and that can be causing a "missing master" error, AND they count against the plugin cap. (If LOOT is showing them, then they are present in the folder. "Ghosting" adds a ".ghost" end to the extension so LOOT and the game ignore them.) If they were "deactivated" by the "Bashed Patch", then you should have enabled "auto-ghosting" in the "Mods" Tab of Wrye Flash by right-clicking on the column header and choosing the option from the context menu BEFORE running "Mark Mergeable" and "Rebuild Patch". Please see the wiki "Bashed Patch file with Marked Mergeables" article.

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.

Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article.

-Dubious-

[TheHoneyDipper]

I have done what you described regarding the auto ghosting before merge and bash with WF. I was showing 4 more total plugins than what were active in loot and NMM. It now shows 30 of 30 active.

 

I was able to escape docs house. I saved and exited the game to attempt to load a saved game. I either get the loading screen loop, white screen and HUD with sound but no input. Or just CTD where I have to exit via signing out because task manager gets stuck behind the game window. I was able to enter once to horrendous fps with a crash following.

 

I do have NVAC. I am running the game on ultra high graphics and I do have antialiasing on. I have read through your troubleshooting FAQ. I'm fairly new to modding so I'm assuming most of the nitty gritty is not being readily absorbed by my brain. Any additional help is welcome.

 

My specs(or what I think may be important):

 

AMD RYZEN 5 1600 6-Core 3.2 GHz (3.6 GHz Turbo) Socket AM4 65W YD1600BBAEBOX Desktop Processor

 

EVGA 06G-P4-6163-KR GeForce GTX 1060 6GB SC GAMING Video Card

 

Patriot Viper 4 8GB (2 x 4GB) 288-Pin DDR4 SDRAM DDR4 3000 (PC4 24000) Extreme Performance Memory, Black Sides ...

Crucial MX300 2.5" 525GB SATA III 3D NAND Internal Solid State Drive (SSD) CT525MX300SSD1

Edited September 15, 2018 by TheHoneyDipper

[dubiousintent]

Your hardware is perhaps "too good" for this game. Certainly it's more than the game was designed for. Which means your problems are inherent in the game design, such as pushing too hard for "better graphics quality". Try the following first, but you may need to reduce the graphics quality down from "ultra high". Please see the wiki "Display resolution versus Image Size" article.

 

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

* Related to the NVSR problem, for problems AFTER a save game is loaded see also "Issue: Incomplete save game load" in the "Troubleshooting" guide.

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

Please see the 'Essentials for Getting Started' and 'Vanilla "Load Order"' entries in the 'First Timer Advice' section; and 'Common Game Problems' section, of the wiki "FNV General Mod Use Advice" article.

If the problem persists, then see either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

I recommend you read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with.

-Dubious-

[TheHoneyDipper]

I appreciate the help dubious. Do not think it's the graphics setting. I am moving my files out of the program filesx86 folder at this moment. Hopefully this rectifies the issue. That, or I'll play it vanilla with expansions and say screw it to mods. I'll regret looking at poorly designed faces and empty casinos but at least I'll be able to play the damn game.

[dubiousintent]

First, make sure you can get into the vanilla game with the DLC. Then prioritize your mod choices, and install them one at a time and test each before installing the next. Slow and careful modding will get you a reasonable game. Just realize up front that you can't have everything offered. Every mod (of any type) consumes more of a maximum ~3.8GB of game memory.

 

-Dubious-

[TheHoneyDipper]

Game on vanilla with all dlc and ultra high graphics runs a smooth 60 fps. No issue with save and load so far. Besides all NPCs either looking evil(Doc) or having raisins as eyeballs(Sunny) and the environment looking poop brown I'm going to take an educated guess that the mods went awry somehow someway. I appreciate the help dubious but I did not think modding would be so convoluted and messy. Especially with a mod manager that is suppose to keep things inline and shows your good to go. I'll keep tabs on future mods but I will more than likely play new vegas vanilla style. Thanks again for your input.