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
Does this mean that the 30mm Chaingun and Gimbal rotor will no longer work with the MART script? Because I had it working with the other Ordnance mod. I'm not sure if it has anything to do with this mod in particular because it seems to have broken two of my tanks completely as no weapons will work now. Not even when I removed and replaced them with different weapons or reloaded the server.
It might be an issue with WeaponCore itself, I'm unsure. But I'm really unsure of how to fix my issue right now. Can you help me, please?
Although, the Vanilla version of the 30mm Chaingun and the other weapons included in the Vanilla version pack 100% work. The MART script even recognizes the Gimbal/FLIR rotors/hinges and accepts them. The weapon is also included in the MART group and works with it.
But when I try to use any WeaponCore weaponry, it just doesn't fire. Could it be that there's some kind of conflict between your mods and AWG's mods? Since WeaponCore seems to work perfectly fine for weaponry on other vehicles that do not have anything from your mods included on them.
It just seems that two of my vehicles are completely corrupted and no WeaponCore guns will work on them. Even when I remove all the items/blocks from your mods and remove the mods themselves from my world.
But I don't know because I saw that DarkStar had pushed an update for WeaponCore last night and after that update happened -- the problem started. This also happened on another tank that didn't have anything from your Ordnance pack in it but it used some components from your Aircraft pack (FLIR camera/FLIR rotors + hinges). Then I noticed you released this mod. Did you guys release these updates together or something?
That's why I suspect it may be your mods that have caused these issues for me. I worked really hard on my tanks and I really don't want them to be broken forever. So I am hoping you'll help me out here. :(
EDIT: I just tested the "dumb firing" mode on AWG's weapons, and they allow me to fire the weapon. It's just when I try to use the toggle "mouse-click" option, it doesn't respond at all. That's really the only issue, it seems.
So, currently, the only fix for this is to use the shoot on/off mode with DEBUG and Override enabled in the options for that gun.
removing a mod with functional blocks on your build makes a blueprint with it not be spawnable.
if you really need to use MART, use tools/cameras/spotlights to make the turret usable. Weaponcore guns are not weapon blocks, but Sorters, which cannot be read by MART or similar scripts unless the script is specifically catered for WC
The problem isn't that I can't get weapons from your mods to work. The problem is that I can't get weapons from AWG's mods to work. AWG's guns uses WeaponCore and is compatible with MART (because I've been using them for over 6 years with zero issues).
I'm just trying to figure out if there's some kind of clash between your mod and AWG's mod. WeaponCore seems fine by itself. I don't think it's your mod, and that it is likely AWG's mod that hasn't been updated or something.
The reason why I suspect it may have something to do with your mod is because the only tanks that are affected are the ones that had the gimbal rotors/hinges added to them. There may be a clash of some sort.
I do apologize for bothering you with this and I appreciate the responses so far, Const.
since using SorterDefinition is way more performant so i opted for that in this version. ALL my guns in this pack use SorterDefinition.
as for other MART turrets not working, try outright removing the programmable block and replacing it with a fresh one.other than that, i don't know what else
Oh, no. That's the really weird thing. The turrets 100% work. I can move the azimuths and elevations. Nothing is wrong on that front. It's simply just when I want to set up the toolbar ability for the guns to "Toggle Mouse Shoot [Mode: MouseControl]", it doesn't seem to let me shoot at all. That's really the only issue that I have. If I use override options to "dumb fire" weapons, they work just fine. This same exact situation applies to your WeaponCore weapons as well.
Something really weird just happened while I was testing, though. Your machine gun started firing on the tank where all WeaponCore weaponry were working just fine while I was inside a different tank (where WeaponCore weapons weren't working) trying to fire your weapon on that one... I'm using a remote control block for both. But they weren't connected in any way.
It's also important to clarify that I didn't include any of your weapons into the MART group. They were independent of it and still didn't work anyway. They worked perfectly fine on the other tanks, though.
Maybe I need to recreate all the MART groups again or something. I'll have to see. But it's just two tanks that seem to be affected and no other vehicles have this issue at all. That's what's really perplexing me.
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2881810268
"Mod not loaded because of errors"
No definition 'MyObjectBuilder_AmmoMagazine/CAPRadarMag'. Maybe a mistake in XML?
2022-11-14 21:24:48.414 - Thread: 1 -> MOD_CRITICAL_ERROR: Consty Aircraft Pack - Ordnance (Weaponcore) 1.0
2022-11-14 21:24:48.414 - Thread: 1 -> in file: H:\SteamLibrary\steamapps\workshop\content\244850\2881339118\Data\Weapon and Ammo\MAWS.sbc
2022-11-14 21:24:48.414 - Thread: 1 -> MOD PARTIALLY SKIPPED, LOADED ONLY 3/6 PHASES, Following Error occured: