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
The issue is not that people don’t want to help, the issue is that they can’t, because logs don’t always contain information that can explain bugs or incompatibilities. Sometimes, logs have so much conflicting information that the only thing you can say for certain is that this particular mod list is lost beyond repair. There’s more to say, but Steam’s limit won’t let me to.
RimThreaded has always been very unstable and incompatible, which is probably why they don’t have a version for 1.5. My point is, if you don’t understand what you’re installing or how to use it properly, that’s on you.
The bottom line is:
1. Do due diligence and know incompatibilities.
2. Be careful about bloating your mod list with content you don’t actually need, because statistically speaking, you will get a broken list eventually.
3. Sort with RimPy/RimSort.
4. In case of issues, find the misbehaving mod via binary searching (also known as bisection).
If you are running 200+ mods stay far away from this and mods like it including rim threaded.
Put them in a larger space.
I don’t think there’s a mod can help with that, but you should probably give Performance Fish [github.com] a try.