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)
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
did you already check for file corruption or a newly introduced modconflcit?
if not try the standard first aid list (file paths may vary for servers or non windows users):
delete all modrelated data and redownload it to neutralize eventually data corruption by modupdate (files are findable inside the workshop folder of the steam library folder in which you have installed space engineers).
delete all modrelated data in the main and world specific storage folder and let it regenerate in case this got corruptet (findable under %appdata%\spaceengineers and %appdata%\spaceengineers\saves\yoursteamid64\yourworldname).
make a testworld just with the affected mod and one of the other mods as a mod conflict test.
check the world where you experience the problems for modconflicts by removing mods and readd them in a trial and error fashion with different orders of the mods till you found the conflict or if you have gone through all mods to find that there is no modconflict.