Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Usually this thing is caused by some other mods, so...
1) Is there a Combat Extended in your mod list? (this mod is CE incompatible)
2) Are you using storage mods, such as LWM's Deep Storage? If yes, make sure that the storage is accessible (not in a locked room, for example) and is not reserved by other pawn. Also, try to make some small stockpile for the missiles only and try to load the launcher again.
I made a missile and tried to load it, but
'xxx found no nearby unreserved shell for steel Cursing Missile Launcher (stationary)' and the missile cannot be loaded into the launcher.
How can I load the missile?
For this you will have to install the Vanilla Furniture Expanded: Security. As i wrote in a my mod description, if you will install VFE:S, then the missile launchers will be able to send the missiles to other locations.
To be exact, select the missile launcher (the building), and then look at square buttons (where is a commands like "Hold fire", "Target here", "Deconstruct", "Uninstall" and so on) - one of these will be the long range fire button.
@ spam.this
I rarely play this SOS, so i am not sure, but probably yes, it is possible. I will try to do this.
@Witch ~
This error is a result of an intentional edit of configs, and will not negatively affect the gameplay. I tried to make the stationary launcher to be, well, stationary (non-minifiable). I tried to make it work somehow else, without this error, but the only working options was that one which causes this message to appear in the log.