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
Award
5 
possible he got caught up in some of the cleanup mentioned in the changelog
that would require the vanilla weaponframework to provide the neccessary informations and it was tried for years to get it working properly with the vanilla framework but the attempt was dropped when railguns came it as changes that came with the same update did break most of what was barely working (dmg was in most cases stopped but the shots did go through, delivered the full intertia to what they hit after the shield instead of to the shield and could still deform blocks) with it and it was at that point decided to drop the attempts to make it work with vanilla until the neccessary informations are avaible.
atm the vanilla weaponframework and all weaponframeworkaddons based on it (for example vanilla+, rearths advanced combat systems) are affectet by this lack of informations from the weaponframeworkside.
from experience the usual cause for that is the wrong emitter in use.
you need a station shield emitter and not a shield emitter or compact shield emitter on a station as the shield emitter and compact shield emitter are made to work on ship type grids and the station shield emitter to work on station type grids.
if that all isnt helping i postet the "standard first aid list" a few posts down and that one should help to sort the most common stuff out and if that one also doesnt help please report in on the discord linked inside the moddescription with logs and an example world (a world with no more mods than absolutly neccessary to reporduce a problem and a premade situation for problem reproduction) so that it can be investigated.
it shouldnt and usually its caused by a failed download of the modfiles, did you already sort that out?
- 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 the weapons dont fire on the missiles is usually due to using wc weapons together with nonwc weapons in the world cause one cant see the other.
also neccessary is to have a non console world (ds and wc arent console compatible) and make sure steam itself (not the steam friend system) is in online mode.
if that isnt the case on your end and you have only wc based weapons in use please go over the "standard first aid list" and if that doesnt help report in on the discord linked above with logs and an example world (world with no more mods than absolutly neccessary for problem reproduction and a premade situation for problem reproduction).