Gothpunk4Christ Posted November 11, 2017 Share Posted November 11, 2017 Yeah, I don't use it myself as it included a few mods I did NOT want, and fewer that I did so I really can't say if it really does or does not help, except that I remember ONE person saying it may have. But then, because of the nature of this bug, everyone's experience may be different. Link to comment Share on other sites More sharing options...
walshy71 Posted November 11, 2017 Share Posted November 11, 2017 (edited) What the hell is SNO? Edited November 11, 2017 by walshy71 Link to comment Share on other sites More sharing options...
Gothpunk4Christ Posted November 12, 2017 Share Posted November 12, 2017 (edited) Skyrim Nexus Overhaul. It's my shorthand, idk if it's actually called something else. *edit* I've just been informed it's actually called Nexus Skyrim Overhaul. Oops. Edited November 14, 2017 by Gothpunk4Christ Link to comment Share on other sites More sharing options...
Deleted133263User Posted November 13, 2017 Share Posted November 13, 2017 (edited) IDK if everyone here uses a Bashed Patch, but you may want to check out the most recent development version if plugin Headers and records being anything less than 44 is anything to do with it. From the sticky post : Skyrim Special Edition users of Wrye Bash 307.beta1Recommend you use the Utumno-WIP version 307.201711041935 (grab the Installer) which has now solved all issues with plugin Headers and Records which were not Version 44. The current consensus is that running SSE with any plugins that are not v44 slowly starts to cause problems with your game, so oldrim plugins not properly converted, AND that includes any Bashed Patch created with previous versions of Wrye Bash. When you have the development version of Wrye Bash installed, go to the mods tab, right click the Bashed Patch and rebuild it. Rebuilding it will correct any Header or Record versions to be correct for this game in the Bashed Patch - Other plugins with incorrect versioning for this game are your lookout. Apologies if this has already caused any issues, the problem could not be anticipated by Wrye Bash development, and it took time to correctly understand and solve it. This issue only applies to Skyrim Special Edition Wrye Bash.When 307.beta2 or 307 non beta goes live eventually .. Use that instead. Edited November 13, 2017 by Guest Link to comment Share on other sites More sharing options...
Gothpunk4Christ Posted November 14, 2017 Share Posted November 14, 2017 IDK if everyone here uses a Bashed Patch, but you may want to check out the most recent development version if plugin Headers and records being anything less than 44 is anything to do with it. From the sticky post : Skyrim Special Edition users of Wrye Bash 307.beta1 Recommend you use the Utumno-WIP version 307.201711041935 (grab the Installer) which has now solved all issues with plugin Headers and Records which were not Version 44. The current consensus is that running SSE with any plugins that are not v44 slowly starts to cause problems with your game, so oldrim plugins not properly converted, AND that includes any Bashed Patch created with previous versions of Wrye Bash. When you have the development version of Wrye Bash installed, go to the mods tab, right click the Bashed Patch and rebuild it. Rebuilding it will correct any Header or Record versions to be correct for this game in the Bashed Patch - Other plugins with incorrect versioning for this game are your lookout. Apologies if this has already caused any issues, the problem could not be anticipated by Wrye Bash development, and it took time to correctly understand and solve it. This issue only applies to Skyrim Special Edition Wrye Bash. When 307.beta2 or 307 non beta goes live eventually .. Use that instead. So this may indeed be the issue after all. That would explain why some of us have issues with some things, and some with others, and not entirely repeatable. I do rely heavily on bashed patches, and that would also explain why, though my starting scripts are so low, I have issues, though some people run more intensive mods than I do, but don't have issues. This MIGHT also explain why, though, some other people were still having issues when we tested the WB patches, if they were still using form 43 mods in there, inducing a false positive elsewhere. Bug was still happening without WB patch so it must not be that... while still running form 43's elsewhere... makes sense. But I thought some people may have tested that... memory's fuzzy on this huge honking thread... Link to comment Share on other sites More sharing options...
thatrabidhobo Posted November 14, 2017 Share Posted November 14, 2017 Might explain why I have yet to come across the bug in 200 hrs of play... I haven’t bothered bashing anything except level lists. I also havent spent the effort in converting some mods from 43 to 44. I was going to wait until my next playthru before bashing/converting mods. Was going to try skse at that time, too. Link to comment Share on other sites More sharing options...
Gothpunk4Christ Posted November 14, 2017 Share Posted November 14, 2017 I run a lot of leveled lists though, and that's pretty much the only thing I bash. So you're saying you run form 43s and bashed patch leveled lists and you DONT get the bug? Link to comment Share on other sites More sharing options...
thatrabidhobo Posted November 15, 2017 Share Posted November 15, 2017 (edited) Correct. I use 5-10 form 43 mods, but I donât have access to my PC today to verify if any of those are bashed into the leveled lists, and I doubt they are. Not converting is a bad idea, I know, but I was already enjoying the playthru and didnât want to start over. I took my chances and had no problems except for one spell causing CTD. Im not saying all this as if I know some secret about modding. Iâm just trying to help alleviate false positives. Edited November 15, 2017 by thatrabidhobo Link to comment Share on other sites More sharing options...
Gothpunk4Christ Posted November 15, 2017 Share Posted November 15, 2017 No that's fine, keeping me from getting my hopes up that there may be an actual fix soon is all. Actually had time to game the other day and have been avoiding SSE till this gets sorted out. Or at least till racemenu comes out so I can tweak my followers some more. Link to comment Share on other sites More sharing options...
Deleted133263User Posted November 15, 2017 Share Posted November 15, 2017 (edited) I dont think you can judge this 100% or even determine false positives, I personally have never had the problem, but over the last 12 years I have learned to avoid new mods with dodgy practices because many a mod author wants to be first on the scene to have a good idea, or replicate a previous bethesda game idea for a newer game with similar mechanisms, and have a bit of fame. Eventually of course their comments get locked and the author is non-communicative when the details of their failing become common knowledge. So I avoid mods I have a feeling maybe have not followed best practices, and until this version of Wrye Bash came out have been avoiding using the Bashed Patch for a while (its only about three weeks ago this issue with the bashed patch was realised to be a possible problem, and Utumno is doing his best to get a new beta out officially). Historically we have had a version of Snip which was very good for Oblivion, but for games following that it was not correctly ported accommodating newer record compression methods, so it caused corruption in mods.Fallout 3 came along, and a heap of authors made a lot of mods which were corrupt, which was hard to detect until more recent versions of xEdit came along, and so determining what exactly was to blame was not only hard, but the resulting problems were random and variable due to what else was in anyones load order as to whether they would actually see any problems in game = The Fallout 3 community is riddled with issues that are hard to resolve. Even Skyrim LE has a few snip related problems by stubborn authors who were adament in their assumptions that there was nothing wrong with snip, here's a bunch of fixes for the most prevalent ones. Hopefully anyone converting any of the originals of those to Skyrim SE, used the fixed version of the plugins instead. Now we have an issue where original mod authors from Skyrim LE have gone, and pretenders to the throne who dont have much of the original authors knowledge are apparently getting permission to duplicate mods to Skyrim SE, but probably not following advice of best practices that we know about so far to convert them. Arthmoor has witnessed first hand the problems which can manifest not only from his various load orders in development, but also other users who have gone through troubleshooting processes with him regarding plugin Header and Record versioning .... Conclusion is the issues can develop randomly, may take a long time, and can be variable results when people with similar load orders are compairing notes when problems started. Top tip, dont use any mod not converted properly, and use the new development Wrye Bash linked above so that Bashed Patch is also not part of the picture causing potential problems, and new authors without a clue give them a diplomatic kick up the arriss :smile:, to stop corruption of our mod libraries. Quite a lot of them could do with cleaning with the most recent xEdit too, "improved record definitions" includes detecting records in Skyrim SE better. .. Or if you dont care about a long term save, have fun with everything tempting out there, just dont be raising bugs with anyone because your included plugins will just be wasting peoples time trying to nail an issue which is practically impossible to solve. This inconclusive topic is probably a good example. :tongue: Edited November 15, 2017 by Guest Link to comment Share on other sites More sharing options...
Recommended Posts