LucidLady Posted January 1, 2021 Share Posted January 1, 2021 Ok, so for the longest time i've only had one thing which causes me to CTD. Just one issue that I can't seem to figure out.One of my mods is referencing the LL_Ammo_Any base game records, but only while the game is actually running.It causes me to frequently CTD while trying to save. It's the literal only thing that makes me CTD.I have no idea how to narrow down which mod it could be. I simply have too many mods, and the CTDs are too inconsistent. It would probably take a year to go through my list, disabling 1 at a time, then waiting and spam saving until I get a CTD. So i'm wondering instead if there's some way to view which scripts are running in-game?Or, if there's a way to pause all scripts, do a save, and then re-start them? Link to comment Share on other sites More sharing options...
Guest deleted34304850 Posted January 1, 2021 Share Posted January 1, 2021 you may be able to use something like snaketail (if it's still going) to monitor your papyrus logs and see if that helps you. however, the mod you are trying to track down would need to externalise something to the logs, which may, or may not be the case. Link to comment Share on other sites More sharing options...
LucidLady Posted January 3, 2021 Author Share Posted January 3, 2021 you may be able to use something like snaketail (if it's still going) to monitor your papyrus logs and see if that helps you. however, the mod you are trying to track down would need to externalise something to the logs, which may, or may not be the case.Hmm, one more question.If I go into the Scripts folder in my Fallout4 directory, would I be able to search through each script text file in there for the LL_Ammo_Any reference? Link to comment Share on other sites More sharing options...
NoCashNoExp Posted January 4, 2021 Share Posted January 4, 2021 (edited) If this ctd bug happens when you save even on a fresh game then there's another solution I would like to propose. Instead of disabling 1 mod at a time, disable the first half your mod list then go into the game and test. If the bug is still there then you know that this mod in the first half and if it's not then it's in the lower half. Now, take the half that has the bugged mod and divide it into two halves and rinse and repeat. This will allow you to pinpoint the mod in a couple of tests depending on your mod list size. If you have 300 mods for example, the next list would be 150 mods and so on. Saves a ton of time. This is a searching strategy in computer science called binary search in case you're interested in reading about it. About the reading scripts part, you could go into your Fallout4/Data/Scripts/Source/User folder, open .psc files using any text editor and read the source code for scripts but some modders don't release the source code for their scripts meaning you might not find the offending mod using this method. Edited January 4, 2021 by NoCashNoExp Link to comment Share on other sites More sharing options...
LucidLady Posted January 4, 2021 Author Share Posted January 4, 2021 Hmm, I will certainly give that a go if the crashing starts back up.However, interestingly, I haven't had a single CTD on my newest playthrough. Before starting the playthrough, I went into each mod which had been touching the LL_Ammo_Any record and deleted any new mod-added ammo types that they introduced.There was only two mods that checked both of those conditions for me - Xander's Aid and Outcasts and Remnants.I had already removed any references those two mods made to the Ammo LL, but I wasn't using the new ammo types anyway so I figured why not try deleting them.Replaced the ammo types with base-game variants. I'm 11 hours into the new playthrough, over 4o saves, and zero CTDs. That's a hell of a streak. I'd typically expect a dozen or so CTDs-on-save at this point. I don't know why this would be a fix, if it actually has worked. If I get to the 48 hour mark without any CTD-on-save instances, i'm callin' it a win.But i'm certain that both Xander's Aid and OaR are at the most recent update, and I don't see any comments on either of those mod pages about this CTD problem.And the CTD issue seemed to affect my brand new computer at the same magnitude that it affected my old computer, so the problem's gotta be present "out of the box".I also have both of those mods installed on my friend's computer, and he doesn't have this CTD-on-save problem at all. And both of our computers are built out of identical parts.So like... idk. *shrugs* It might be a problem caused by a combination of two or more mods. Like, the mods on their own, individually, wouldn't cause the problem - but when put together in the same save, it does.That situation would make finding it (even with the method of disabling small chunks of mods at a time) even harder and not guaranteed to catch it.For now i'm just gonna keep playin' and pray to the game stability gods that I never CTD-on-save again.Perhaps a day will come where I don't flinch or hold my breathe when I hit the save button... Link to comment Share on other sites More sharing options...
Guest deleted34304850 Posted January 14, 2021 Share Posted January 14, 2021 do you use a mod called "damn apocalypse"?Reason I'm asking is this post seems to contain some items that resemble the game records you are having (or had) issues with; https://forums.nexusmods.com/index.php?/topic/6876357-damn-apocalypse/page-93&do=findComment&comment=87441463 Link to comment Share on other sites More sharing options...
LucidLady Posted January 15, 2021 Author Share Posted January 15, 2021 Never used that mod, no.Still totally cured of those problems tho, btw.However now i have a totally new bug that i have no idea how to find.Some of my far harbor rocks are glowing in big slow orange flashes.It's not gamebreaking, but it's hard to ignore. No clue what's causing it. Link to comment Share on other sites More sharing options...
Recommended Posts