2019-10-16 00:14 EDT


View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0003010FSSCPbeamspublic2015-05-22 01:35
ReporterJoshua 
Assigned To 
PrioritylowSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformR10541OSWindowsOS Version7
Product Version3.7.1 
Target VersionFixed in Version 
Summary0003010: Beams stay whilst ship casting them has been destroyed.
DescriptionI am aware of a ship being capable of shooting weapons whilsts it's in it's "Final detonation" sequence, but currently, beams are able to fully finish their firing sequence even though the ship firing has been destroyed. The beams "Stay on" for their predetermined time whilst the ship's model has already been reduced to fiery debris.
Additional InformationTested repeatedly in the "Rescue" mission of the "Incursion" campaign (as provided by the campaign restoration project")
TagsNo tags attached.
Attached Files

-Relationships
+Relationships

-Notes

~0016718

SmashMonkey (reporter)

Replicable. Inspection of beam.cpp shows that the check for beam firing only takes place during the beam warmup. There is no way to turn off the beams mid-firing (if the firing ship has been destroyed).

~0016720

MageKing17 (developer)

There is code that is supposed to serve this purpose, in beam_move_all_pre():

        // check if parent object has died, if so then delete beam
        if (b->objp->type == OBJ_NONE) {
            // set next beam
            moveup = GET_NEXT(moveup);
            // delete current beam
            beam_delete(b);

            continue;
        }


The object's type should be set to OBJ_NONE when it's deleted, which should happen shortly after OF_SHOULD_BE_DEAD gets set, which should happen if the ship is either vaporized or finished exploding.

Is the problem that beams aren't stopping during the process of dying? Because that seems like intended behavior.
+Notes

-Issue History
Date Modified Username Field Change
2014-02-18 14:59 Joshua New Issue
2014-08-17 00:38 Echelon9 Priority high => low
2015-05-22 01:04 SmashMonkey Note Added: 0016718
2015-05-22 01:35 MageKing17 Note Added: 0016720
+Issue History