theodu74 Posted December 1, 2020 Share Posted December 1, 2020 Hi everyone, I've been playing on my New Vegas character for a while, and found out that this extremely loud neon sound could be fixed easily just by removing an option in my bashed patch. So I did, but Wrye Bash just crashed at the end of the process. (It ended, then a white box called Bashed Patch opened and nothing happens so I have to force close it.) I launched my game to see if it was fixed, indeed the neon sounds were much more tame, however a LOT of things had changed, the nights were extremely dark, but the game also got more laggy. I tried doing another bashed patch to revert back to it's previous state, but it crashed just the same. I tried disabling every merge option in the patch, isolate specific mods, but even with 0 mods loaded, the patch just won't merge properly, and I also tried reinstalling wrye bash but to no avail. Anyone has any idea of what I can do to fix my patch ? Also noticed that some mods seem to be inactive with that half functional bashed patch, no mod added creatures, no inventory sorter, those worked just fine before. Link to comment Share on other sites More sharing options...
dubiousintent Posted December 1, 2020 Share Posted December 1, 2020 (edited) Problems with Wrye Bash while creating a "Bashed Patch" file should be addressed to the WB team. They will want to know the details about how (and at what stage in the process) you got it to crash. (If they cannot reproduce the same problem, it is unlikely they will be able to resolve it.) Please make note of and include the requested information on the first page of that thread (like which version of WB you are using along with your "load order" including mods which do not appear in the LO like NVSE and DLLs). The information requested in the wiki "How to ask for help" article is always a good starting point. That you are unable to simply create a new patch file with the old settings suggests the problem might be unrelated to WB, and instead something like "insufficient free disk space". Any time the free disk space drops below 10% of disk capacity, Windows starts to have problems. Clean out your "trash can" and run "chkdsk". -Dubious- Edited December 1, 2020 by dubiousintent Link to comment Share on other sites More sharing options...
Recommended Posts