ThiccXpert Posted March 31, 2019 Share Posted March 31, 2019 Hello, I have recently installed the large 3 pack NMCs Textures Mod along with a few other mods. When I began having game crashes, I was able to single out that this mod is the one causing random crashes in-game, on loading screens, and on saves. I'm sure it has something to do with the load order or how they're prioritized or something of the sorts, but as I am fairly new to modding Fallout through NMM (Vortex) and modding in general, my troubleshooting and googling has gotten me nowhere with being able to reliably run the game with NMCs active. I have attached my mods page as screenshots because they don't have a load order, but I have included my plugin load order page as a list below (excluding official game files). Any and all help along with educating me on this problem is greatly appreciated :smile: Load order past the base game files 10: Run the Lucky 38.esm11: NevadaSkies.esm12: NevadaSkies - Blueberry Nights.esp13: Glove_be_gone.esp14: Mission Mojave - Ultimate Edition.esp15: The Lucky 38 Empire.esp16: NewVegasExtendedMapMarkers.esp17: MannaroTB_HoloPipBoy4000.esp18: NevadaSkies - Ultimate DLC Edition.esp Link to comment Share on other sites More sharing options...
HadToRegister Posted March 31, 2019 Share Posted March 31, 2019 You should be using YUP - Yukichigai Unofficial Patch, instead of "Mission Mojave" Link to comment Share on other sites More sharing options...
ThiccXpert Posted March 31, 2019 Author Share Posted March 31, 2019 You should be using YUP - Yukichigai Unofficial Patch, instead of "Mission Mojave"Is this just a random suggestion or one that'll help with the stability of NMCs? Link to comment Share on other sites More sharing options...
HadToRegister Posted March 31, 2019 Share Posted March 31, 2019 You should be using YUP - Yukichigai Unofficial Patch, instead of "Mission Mojave"Is this just a random suggestion or one that'll help with the stability of NMCs? It's a suggestion that using the proper Unofficial Patch for FONV will stabilize your game because you're currently using the wrong one. As far as NMC goes, will your graphic card handle it, because it puts a lot of strain on the engine Link to comment Share on other sites More sharing options...
ThiccXpert Posted March 31, 2019 Author Share Posted March 31, 2019 You should be using YUP - Yukichigai Unofficial Patch, instead of "Mission Mojave"Is this just a random suggestion or one that'll help with the stability of NMCs? It's a suggestion that using the proper Unofficial Patch for FONV will stabilize your game because you're currently using the wrong one. As far as NMC goes, will your graphic card handle it, because it puts a lot of strain on the engine You should be using YUP - Yukichigai Unofficial Patch, instead of "Mission Mojave"Is this just a random suggestion or one that'll help with the stability of NMCs? It's a suggestion that using the proper Unofficial Patch for FONV will stabilize your game because you're currently using the wrong one. As far as NMC goes, will your graphic card handle it, because it puts a lot of strain on the engine Yes, I'm running a 1070 ti and a 2600x Link to comment Share on other sites More sharing options...
dubiousintent Posted March 31, 2019 Share Posted March 31, 2019 While it is possible, I really doubt NMC is causing your random CTDs. So, while I will address it, let's look at the more likely culprits first. We REALLY need to see your sorted "load order" as produced by "LOOT"; to include the main game and DLC files. With modded games its the sequence, not merely the list of mods, which is the cause of many problems. LOOT's sort gives a good first approximation, correcting the most obvious issues and is sufficient for most players. You can make minor adjustments to the order and tell LOOT how to remember them. It's in the on-line documentation under "Metadata". Instructions on how to copy it's list for posting are in the "How to ask for help" article, and "Checklist Item #11' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. * 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.Please see the 'Vanilla Load Order' entry in the 'First Timer Advice' section; and the '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.* 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. It's so common you might as well deal with it now. Please see the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu') entry in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.* You can also get "out of memory" errors from the graphics system (which is separate from exhausting system memory), even with the game 4GB enabled. The video pipeline is known to have "memory leaks", and these occur faster with "beautification mods". Here the cause is a combination of larger image sizes ("higher resolutions", aka "hi-rez"), hi-rez texture packs for skin, hair, clothes, weapons, and landscape; along with mods that increase the number of NPCS in a given cell. (All those hi-rez texture "personal accessories" get multiplied by the number of Actors.) Please see the wiki "Display resolution versus Image Size" article. While "ENBoost" can help, you may need to switch to lower resolution/ smaller sized images or even lower quality in your game graphics configuration."Texture packs" don't usually show up in the "load order". Because "Texture/Mesh" replacement mods replace vanilla versions of those files, you absolutely have to toggle "ArchiveInvalidation (AI)" 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 "texture problems". This is usually evidenced by red "!" icon for missing meshes, and solid colors for missing textures, or "messed up" textures. This "ArchiveInvalidation" mechanism is incorporated in all the currently used mod managers, so there is no need to (and problems arise if you do) install older mods to provide that capability. ONLY USE ONE METHOD of AI, especially if you have multiple mod managers installed. Otherwise they will conflict, as they use their own "arbitrarily chosen" names for the AI BSA files. (There is not a standardized name used among them all.) 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. I recommend anyone read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to play a modded FNV or it's been more than a year since you last did so.-Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts