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
When I tried to go deeper, then found next:
System.Linq.Enumerable:ToList<Thing>
When I tried to stacktrace it I freezed to death and was forced to restart xd
TLDR: Seems like it's just performance of very extreme cases.
https://mega.nz/file/wfwQyIxB#Y9g3hQQ_dPYOkYKeRrmZ-svETZq6s-hbwmmLLjuk828
So, I decided to turn mod on again for my new save.
Crashes while using simple and fine nutrient taps(was using 2 at the same time for colonists and prisoners with Small vat)
Couldn't really figure out any more details.
https://gist.github.com/HugsLibRecordKeeper/21c23c9d7be92447e1cc9b5f04daa1ad
This ^ currently more important to test on new save.
1: make a second save, just in case.
2: basicly make screenshots/notes how your nutrien network is build (hopfully, not to complex befor encountering this bug)
3: remove this mod
4: load the game and set all the chemfuel taps to 150 (or your desired number)
5: just in case, devmode build a few more taps, set all of them to numbers you want and uninstall them for later use.
6: save, reactivate this mod
7: dev mode rebuild the whole nutrien system and never ever touch the setting of the taps again (selecting them is fine, just don't change their setting, and if you do, i hope you folowed 5)
Hucket Bat, basically the issue was originating from my fix of VEF error that wasn't fixed for a while regarding +1 and +10 not working on pipes in v1.5. So it was applied to v1.6 automatically, but VEF finally fixed it in v1.6 and fix no longer was needed. Thus removing no longer needed fix from v1.6 removed the issue.