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
If you spend that much time on the forums, then you should probably also know that a) you need to read every mod page thoroughly, including the posts and bugs sections before downloading, and b) test only a few mods at a time. So by the time you're done with your test run, you should have close to 100 or more hours in. With 400 mods, probably closer to 200-300 hours. Pretty fair bet that it's stable for a new game at that point.
Judging by how many #254s you have it seems like you never ran something to sort out load orders. Every mod should have their own load number, including the CC ones.
Or is that how MO2 and LOOT does it? Only used Vortex, so it looks weird, and I dont like weird in my load orders :P
My second guess...
I think that is the issue he is using conflicting mods somewhere in that.
My third guess...
He is running SS Conqueror, that is a VERY heavy scripted mod. If some of those mods are adding to that burden and he is trying to do something like run 75FPS...you get the idea.
If you want more help with CTD then you got to keep track of where you where and what you were doing when each happened because that can narrow it down quite a bit.
OS: Windows 7/8/10 (64-bit OS required)
Processor: Intel Core i7-5820K or better
Memory: 8 GB RAM
Graphics: GTX 1080 8GB
Storage: 58 GB available space
I have used
SKKMobileWorkshop.esp
112 70 CheatTerminal.esp (as it can be used to "fix" some quest bugs)
17 11 WorkshopFramework.esm
plus whatever requirements they have without issues.
What I have found when using the metrics display from my GPU software is the longer the game runs the larger amount of ram it reports as being used. With a large mod list you may actually be running out of ram after it runs a few hours.
It happens that someone might have time to go through all your mods. It is like a building a custom car model. Only the lead engineer knows every component. And that person is you. You have added many additional components to improve the car, so that it's different than the stock model. You come to a mechanic, telling that the car is not running well after a while and is giving us a list of components being used.
What many usually do is to go through it and point out known problematic mods that might be a culprit of your CTD. That is how mechanics works: they use their experience and focus on some components that might be the culprit. But since your mod list is huge, it require time to find potential conflict because you have to know what mod X does and if the mod Y, further in the load order does not conflict with X. We are volunteers and it is our choice to invest time in this matter or not.
Perhaps you can answer on these questions:
1. Did you have thought to enable papyrus logging[www.creationkit.com] for a while to see if it does not "spew" errors before crashing? It might give you some pointers such as issues with "stack frames"
2. Since many mods are purely "cosmetic", I suggest to focus on some mods that relies on heavy scripting. Cosmetic mods are rarely causing crashes unless they work on same records. But in that situation, the game should not load at all AFAIK.
3. What's in the bashed patch? Is it built correctly?
4. I need some details on the CTDs. Does it happen on all location or just in a settlement area? Or when you are going through your items? The answer might give you an indication.