Lunarthrope Posted May 28, 2019 Share Posted May 28, 2019 Hello, anyone reading this, I have an issue. I have installed Wasteland Flora Overhaul into Fallout: New Vegas and it worked perfectly. One day however, with the mod installed and deployed, the game crashes on startup. Loot warned me to not clean the UDR records, yet I never cleaned it or sorted much at all. For a couple days, it worked, than suddenly stopped cooperating. If anyone can give me advice to fix this issue, that would be nice. I like this mod very much and it would be very saddening to not be able to use it. Clueless, Nathaniel Thompson Link to comment Share on other sites More sharing options...
dubiousintent Posted May 28, 2019 Share Posted May 28, 2019 If you add (or remove) any VWD/LOD textures (such as NMC, Vurt's WFO, or Ojo Bueno), please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen. Also recommend you read the 'LOD/VWD Texture Packs' section of the wiki "FNV General Mod Use Advice" article first. That said, I haven't heard of WFO suddenly starting to cause CTDs. 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. This most commonly is due to Windows system updates changing something. Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as if you are using a "regional language version" of the game (even if you are playing it in English); using the FNV4GB Patch, NVSE and it's related plugins; replacements for textures (specifically their larger image sizes: 1024x1024, etc.), animations, or "bodies", etc.; and "post-processors" like ENB or SweetFX. It saves us playing "20 questions" and gets you a more specific answer more quickly. (The usual turn-around on post and reply in an older game forum is 24 hours.)* See "How to markup images (etc) in forum posts and comments" article for how to use "Spoiler tags". LOOT already includes those tags in the "load order" it copies to your clipboard, so you can just paste it's list into your post. -Dubious- Link to comment Share on other sites More sharing options...
Lunarthrope Posted May 28, 2019 Author Share Posted May 28, 2019 Th If you add (or remove) any VWD/LOD textures (such as NMC, Vurt's WFO, or Ojo Bueno), please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen. Also recommend you read the 'LOD/VWD Texture Packs' section of the wiki "FNV General Mod Use Advice" article first. That said, I haven't heard of WFO suddenly starting to cause CTDs. 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. This most commonly is due to Windows system updates changing something. Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as if you are using a "regional language version" of the game (even if you are playing it in English); using the FNV4GB Patch, NVSE and it's related plugins; replacements for textures (specifically their larger image sizes: 1024x1024, etc.), animations, or "bodies", etc.; and "post-processors" like ENB or SweetFX. It saves us playing "20 questions" and gets you a more specific answer more quickly. (The usual turn-around on post and reply in an older game forum is 24 hours.)* See "How to markup images (etc) in forum posts and comments" article for how to use "Spoiler tags". LOOT already includes those tags in the "load order" it copies to your clipboard, so you can just paste it's list into your post. -DubiousI will try that, thank you. Link to comment Share on other sites More sharing options...
Recommended Posts