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
-search for errors in the logs about mod loading at game launch
-read the error logs after crash (steamApps/Ludeon/Rimworld/RimworldWindata/output.log) to see if some mod ressource is mentionned
-go to AppData/LocalLow/Ludeon/Rimworld/Config, open Prefs and set <pauseOnError> to "True" , if the game now pause instead of crashing open the ingame developpment console from Options during this pause and search for the error in the logs (not the best method : will only work if the game crashed because of a repeated error creating an endless loop, also you may get a lot of pauses due to minor errors that wouldn't have crashed the game)
-if still no clue uninstall mods one by one and see if the crash still occurs untill you find the mod that was triggering it