安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
獎勵
9 
sounds like you have wc incompatible weapons in your world you want to use.
any non wc weapons (so weapons not made to work with weaponcore) wont have a working ai due to se only beeing able to use one weaponframework at a time and thus a modded weaponframework will force the vanilla weaponframework to go to sleep.
this does not happen with weaponframeworkaddons (for example vanilla+, rearths advanced combat system) as these just extend the functions of the vanilla weaponframework instead of replacing them.
if you are only using wc compatible weapons and it still happens it could be a case of file corruption or another mod causing a mod conflict, i postet the "standard first aid list" designed to handle such stuff a few posts down the line.
not as far as my informations go, though we had some cases where the se update caused file corruption on the se end of things and thus in turn problems with mods.
depends on the weapon you use, though if its just the vanilla weapons replaced by the ionternal replacer of wc itself it shouldnt differ much from vanilla.
some moddes setup weapons so they are more effective against small grids than large grids or vise versa and without more informations on it its hard to tell what is going on.
- make a testworld just with the affected mod and one of the other mods as a mod conflict test, don't forget the mod requirements.
- (s) make a file integrety check for space engineers itself.
- (s) delete all modrelated data of the affected mods 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).
- (s) delete all modrelated data of the affected mods in the workshop folder 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).
that can have multiple causes ranging from file corruption over mod conflict and f1error up to using the wrong version of se itself.
if you can provide more informations it can atleast be tried to narrow it down.
i would suggest going over the "standarf first aid list" to sort out mod conflcit and file corruption and if that one doesnt help put together logs and an example world (a world with no mor mods than absolutly neccessary to reproduce a problem and with a premade situation for problem reproduction) and provide them via the discord linked inside the moddescription.