gsparks3
commented
1 year ago Okay, had this happen in another game, and this time I grabbed the log and autosaves. AECM was crit out rather than having its location destroyed, but the effects were similar. Still version 0.48.
Autosaves are, in order, the beginning of the firing phase (prior to the AECM being crit), the physical phase after the AECM was crit, and the movement phase of the next turn after the AECM was crit (latter is provided to easily allow moving the unit to demonstrate that its AECM is still providing effects on other units). The unit in question is the Firestarter FS9-OZ (custom unit).
megameklog.txt autosave_2023-09-23_15-41-34.sav.gz autosave_2023-09-23_15-45-38.sav.gz autosave_2023-09-23_15-46-33.sav.gz
Description
During a campaign game, a custom Omni Firestarter with an Angel ECM in ECCM mode in the arm had said arm destroyed by a Homing Arrow IV shot. We noticed that despite the system being marked as destroyed, and the unit no longer being indicated as an ECCM Source on the tooltip, it was still generating a visual overlay, and in fact still providing the Angel ECCM effects (confirmed by moving it to cover allied units jammed by an enemy Angel ECM, which became unjammed).
Unit display confirms item destruction, tooltip confirms lack of ECCM Source.
Custom enemy Wolverine providing Angel ECM field and jamming units.
Allied units become unjammed after "phantom Angel ECCM" moves into range, complete with visual overlay.
Files
Savegame with issue is provided. The unit in question is controlled by player "18th Division". Can reproduce all images above from this savegame. autosave_2023-04-22_14-58-53.sav.gz Logs were not saved - apologies. Similarly, I do not have a save prior to the arm being destroyed.