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
Based off what I read for BetterGC it seems like that mod helps specifically with the issue that the game likes to hold onto world Pawns and keep them "active" even if you haven't seen or interacted with that pawn for a very long time. With so many Pawns causing "ticks" it can cause major slowdown and lag as you play further into a playthrough.
TLDR: I would figure out what performance mods work best for you through trial and error. Make sure to keep RocketMan at the very bottom if you have it no matter what and if you're testing with an active save always have a backup of that save in case things get funky and you don't realize it immediately
Then, place all 3 at the *VERY* bottom of your load order, and make sure that Rocketman specifically is *ALWAYS* the very last mod in your load order, no matter what. Even if another mod you use, hell even if a giant modpack you use tells you to put one of it's at the very bottom, don't.
Instead like this:
My 531 Other Mods
Better GC: Mothballing
Performance Optimizer
XYZ - (The Hypothetical mod from a huge pack demanding it be at the bottom)
Rocketman
Setup like this, my saves work fine.
Anyways, the point is, use the described load order at the end of your mods, and no matter how eddicted to mods you get, your optimizers will still work fine.
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).