Resolved Oddities with Latest Updates (3.1.6, 3.1.6a)

[adb1x1]

Not really sure this is a bug with the SS update or if it is a combination of the update and some other gremlin in my latest play-thru.

I updated to 3.1.6 (or 3.1.6a for the pieces at that revision) but didn't really play for a few days. Played for a bit and thot I'd check the number of active scripts (an ongoing issue this time around). Using FallrimTools, I tried loading the latest save and got the error 'Error while reading "Save......", 'Error while reading the Papyus section'.

Figured it was just a corrupt save, so I started the game. The save loaded, but sometimes that doesn't mean there are no problems. So I loaded a pre-update save, then saved it, tried FallrimTools, and got the same message. Did this several times with different saves, and had the same issue.

Went back to 3.1.5, loaded the same pre-update save, saved, and the error went away. No issues with subsequent saves either. I haven't seen any posts about it, so hopefully it's an isolated incident.

 

[Samutz]

That error from Fallrim Tools comes up every once and while for me too. When that happens I usually wait a few minutes in game and then save again. Most of the time the new save will work. I think it's just that there's something going on with the scripts that Fallrim doesn't know how to read and that it's not necessarily corrupted.

 

[eldiabs]

I've tested this extensively and sent save files to both kinggath and the creator of fallrim tools. Don't know if they've figured out the reason for the error yet, but it is directly related to sim settlements plots. If you go and refresh some plots, that read error will go away and you'll be able to open the save with fallrim tools again. Doesn't seem to be anything beyond that. Everything still works as far as I can tell. But I do think if you let it go on and on from one settlement to the next it can lead to crashes in settlements. So I've made a constant habit of refreshing a couple of random plots whenever I show up at a settlement. No major settlement crashes for me at least.

 

[adb1x1]

Hum, ok. I've had a number of issues on this last playthru. I suspect it started with Sanctuary Hills. I probably should have gotten thru all the initial quests for the 5 before starting a ROC city there.

Anyway, I hadn't noticed it before and didn't see it until the 3.1.6 update (I've had way too many active scripts over and over and have had to clean saves quite a bit). Before going back to 3.1.5 it would happen with every save, even after cleaning a good save and saving in game. Must be something going on in my game in the background with 3.1.6 since 3.1.5 stopped it.

More than once, I wish I had just started over after seeing 400+ active scripts not long after Sanctuary (but I waited a while before going to Concord, so I had done quite a bit). After I got those cleared, I hoped.....but sometimes doing over is better than changing the bandaids!

 

[Cranky Cat]

I first had that exact thing come up for me when checking my saves with FallrimTools after 3.1.6 but only if I was in a settlement. I went back to my first save where the error didn't come up just to be safe. I never saw it before 3.1.6 either. I don't normally have unattached instances but I like to check if I have issues.

I thought of sending the save to the author of Fallrim Tools as well but did you hear back?

 

[eldiabs]

More than once, I wish I had just started over after seeing 400+ active scripts not long after Sanctuary (but I waited a while before going to Concord, so I had done quite a bit). After I got those cleared, I hoped.....but sometimes doing over is better than changing the bandaids!

Sounds like you had a script/s that hung up and caused everything else to back up. I've been watching this in my load order as well. Sad thing is, it's not just a single mod causing the issue. I've even seen vanilla scripts cause this. For example emsystemturfscript which is a vanilla script tied to fallout.esm did it for me recently. Another time it was enhanced blood textures. Pack attack did it really bad on one of his latest updates, and I've seen some of the sim settlements scripts do it as well when under heavy load from other mod or vanilla scripts firing. The only way around it from my experiences is to make lots and lots of saves. If you're going in and out of settlements a lot you need to make saves before and after you leave. Check them in fallrim tools. If a bunch are running, don't leave the settlement, wait around a bit for kinggath's scripts to finish up. Seems he's been building a lot of checks in to make sure they finish, but they can get delayed or locked out by other mods running scripts...even vanilla scripts can do it, unfortunately. You really shouldn't see more than 1-15 scripts firing off normally (I'm averaging 4-10 most of the time with over 300 active plugins), with the occasional heavy load from sim settlements doing it's thing, but those usually go quickly. Other than the plot refresh thing, it all appears to work most of the time. But the save save save thing is a huge deal.

I thought of sending the save to the author of Fallrim Tools as well but did you hear back?

Yup, I did almost as soon as I submitted the bug. You need to submit it via the skyrim bug page, however. I'm sure he'd appreciate more than one person sending that specific read error in if it's related to sim settlements plots like mine was. Might help them hammer out what's going on.

 

[OwenHo]

If you do notice excessive scripts after any update it would be a good idea to go somewhere quiet like Home Plate and just let your character stand there for 15-20 minutes to see if the scripts clear up. With this update there were a bunch of fixes that may have backed some games up. Please let me know if any of the suggestions in this thread have helped.
Thank you

 

[adb1x1]

I apologize for not responding sooner. Been playing another game for a bit and haven't checked back regularly. I had tried several of these suggestions before, but I just decided to stay with 3.1.5 until I updated to 3.2. I had 70+ active scripts before updating, and decided to clean those up beforehand (something I had not done when I moved to 3.1.6). Except for a couple of times after, the issue hasn't reoccurred, but I've only played 2-3 hrs. I've had a lot of active-script issues this playthru for some reason. Started, as I mentioned at Sanctuary. I'd been better off to start it all over.
Thank you all for the help!

 

[OwenHo]

I'll mark this as resolved and place it in the Archive.
Thank you