Steam installieren
Anmelden
|
Sprache
简体中文 (Vereinfachtes Chinesisch)
繁體中文 (Traditionelles Chinesisch)
日本語 (Japanisch)
한국어 (Koreanisch)
ไทย (Thai)
Български (Bulgarisch)
Čeština (Tschechisch)
Dansk (Dänisch)
English (Englisch)
Español – España (Spanisch – Spanien)
Español – Latinoamérica (Lateinamerikanisches Spanisch)
Ελληνικά (Griechisch)
Français (Französisch)
Italiano (Italienisch)
Bahasa Indonesia (Indonesisch)
Magyar (Ungarisch)
Nederlands (Niederländisch)
Norsk (Norwegisch)
Polski (Polnisch)
Português – Portugal (Portugiesisch – Portugal)
Português – Brasil (Portugiesisch – Brasilien)
Română (Rumänisch)
Русский (Russisch)
Suomi (Finnisch)
Svenska (Schwedisch)
Türkçe (Türkisch)
Tiếng Việt (Vietnamesisch)
Українська (Ukrainisch)
Ein Übersetzungsproblem melden
what do you mean with "The structure of this mod is horrible"?
if it refers to the point that you cant mix wc based stuff with nonwc stuff that is something limited by se itself as it can only handle one weaponframe properly at a time, though you can still put subweaponframeworks on a weaponframework without the same probs as if you would put in multiple weaponframeworks.
let me guess you did use weaponmods that arent based on wepancore?
if yes that is due to weaponcore beeing a weaponframework and spacee gineers can properly handle only one weaponframework at a time so if you use weaponcore the vanilla weaponframework will basically be in passive mode.
you will need to choose if you want to use weaponcore based mods on nonweaponcore mods.
take a look here for some information about some of the compatibility problem: https://github.com/Ash-LikeSnow/WeaponCore/wiki/Player-Tips#december-2022-addendum-on-non-wc-weapons
also that is nothing that can be changed from modder side and it would need a keen side change for space engineers beeing able to hanlde multiple weaponframeworks properly.
if you think its a bug inside the bug report area on the wc discord, if you just need general help to narrow it down and sort it out inside the help area on the wc discord.
Autocannon turrets, large-grid rocket turrets, and interior turrets continued to operate, but large-grid assault cannon turrets and small-grid rocket turrets failed to track on new ships after 7 minutes of ship printing.
I'm running 20 ship printers, so the issue may be sim-speed related / preventing block initialisation. The log shows two null reference exception errors for a CoreSystem's ray casting function. I've had similar errors to this before mass-printing with the vanilla Offensive AI block, which caused me to remove it from all ships, so the issue may be beyond the mod.
If it would be useful, where is best to send the report to?
as far as i could find out the default weaponsettings are something defined by the modder or keen depending on who did make the weapon.
an yep its probably a good idea to turn target neutrals to of on default.
1: can you reproduce it with the vanilla weapons that get replaced with the internal replacer of wc?
2: did you already check for mod conflict and file corruption?
if 1 is true please make a report including example world with just weaponcore and requirements if, if its fals you need to go over to aryx as its then probably on that end.
if 2 is false please check for it, if its true default to 1.