Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Use the bisection method. What you do is you turn half of all your mods off and leave the other half on. In your case do you turn 128 off and leave 127 on. If it crashes then do the opposite and turn those on that you've turned off, and turn off those you've turned on. If it stops crashing then your problem is with those that are now turned off. You then do the same again, but with just 64 mods, then 32 mods, and so on.
Also, since you didn't just install 255 mods all at once (I assume) should you try to remember since when the crashes started and what the mods were you've installed at the time. Usually this will give you a good hint. Then read the mod's description carefully and possibly the post section, too, to see if anybody else has noticed issues.
Finally, if you do find out the mod or mods that cause you the crash then send the author a message.
Great advice! I will try the bisection method you described once I complete my university work for the day. Thank you!
I used to get a crash as soon as I crossed the cell border to swans pond. It didn't matter what direction I came from, as soon as my foot crossed one of the cell borders the game would crash. Turned out to be associated with the fast load mod. Don't know why as I wasn't loading a save game. The lesson is that the ways that the game can crash are numerous.
The half-and-half thing is a good idea.
I run a script lag latency detector mod. As soon as I see the latency go above zero I know that I am entering the twilight zone. Ditto with fps going too low. I have bulldozed a few blocls of Boston and rebuilt them which kills fps. When I enter one of these areas I stand still for a few seconds which gives the game a chance to catch up on processing (as recommended by the Sim Settlements site.)
Other signs are events not triggering. Settlers standing around or slow to react to assignment are caused by cpu being overloaded by too much processing.
Missing textures. Interiors not displaying fully seem to be caused by ini settings.
Highly advisable is to update your ini settings to give scripts more time to run and to increase the number of scripts that can run and not be dropped (dropped = deferred). The game may be looking for some data but the script that creates it hasn't run and so the game crashes. The idea is to give the game adequate hardware resources. If that means cutting down on non-essential nice-to-have mods then do it.
simsettlements.com/web/wiki/index.php?title=Performance
I also increase the interior cell buffer size over the default.
But I'd do the half and half thing first because running dodgy mods = continual trouble.
Thank you for your reply and advice!
Which script lag latency detector mod are you using? How do you increase the interior cell buffer size over the default?
I did the recommended changes from the Sim Settlements performance section as well as the ini changes to allow scripts more time to run.
I disabled all of my mods again and I am going to try to cut down on them and re-enable them in groups again to see what happens. I have a nagging suspicion that it is a script-intensive mod such as Disparity, Grim, etc.
I was looking at another post on how to extract my papyrus script crash logs but I do not really know how to read them even with a program I downloaded that parses them and does not show repeated events.