安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题











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.
they are based o nsorters t allow for more functionf of wc to work properly, so if soem files are missing or get corruptet they fall abck o nbasic sorter ebhaviour, besides that inventory sorting scripts allways think that they are sorters.
try if checkign the games fiels via steam file itnegrety check for the agems avaible i nthe steam library and the standard first aid list helps you.
IE For the most part, you fire them pre-emptively
Will investigate the fire issue.
And if there is a block behind it, the jammer will fail to fire.
SA's Logo is effectively a demonic snake.
---
Per the Update Log: This now is survival capable.