2021-03-02 17:57 EST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002791FSSCPFREDpublic2020-05-04 22:05
Assigned ToGoober5000 
Product Version3.6.16 
Target VersionFixed in Version 
Summary0002791: Error checking and better handling of invalid wing arrival anchors needed
DescriptionI've hit an int3() twice in the last couple of days just by changing ship classes in FRED and resaving the mission. If you have ships set to arrive via docking bay and you change the ship class they are arriving from to one that doesn't have a docking bay it FRED does not catch it. All you get is a program has stopped responding and if you break into the debugger you are at an int3() in mission_set_arrival_location() line 6366 in missionparse.cpp. This should be changed to a warning and handled gracefully.

Also hit the same int3() by having 2 bay paths with the same name which is another thing that should be checked for.
Steps To ReproduceDrop a cap ship with fighterbay in FRED. Add a couple of fighter, create a wing, assign them to arrive via the fighterbay with a n second delay. Save mission. Test to make sure it works. Open ships editor, change cap ship to one without a fighterbay or anything else like a sentry gun. Save mission again. Run. Wait n seconds, Crash.

For the duplicate name part just edit any pof and rename one of the bays to be the same as any other. Will show up with the correct number of bays in FRED (if there are 6 bays and 2 are named the same you still get 6 in FRED). Set the wing to arrive via the modified cap ship. Run, wait n seconds, crash.
TagsNo tags attached.
Attached Files




Goober5000 (administrator)

This is a pretty easy fix; sorry it took seven years!



Goober5000 (administrator)

PR merged.

-Issue History
Date Modified Username Field Change
2013-02-08 16:55 FUBAR-BDHR New Issue
2013-02-19 20:54 Goober5000 Assigned To => Goober5000
2013-02-19 20:54 Goober5000 Status new => assigned
2020-04-28 02:21 Goober5000 Status assigned => code review
2020-04-28 02:21 Goober5000 Note Added: 0016986
2020-05-04 22:05 Goober5000 Status code review => resolved
2020-05-04 22:05 Goober5000 Resolution open => fixed
2020-05-04 22:05 Goober5000 Note Added: 0016990
+Issue History