2021-03-06 23:06 EST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002869FSSCPFREDpublic2019-10-13 14:56
Assigned ToGoober5000 
Product Version3.6.19 
Target VersionFixed in Version 
Summary0002869: Changing AI class of a group of ships can mess up departure cues
DescriptionChanged the AI class on 4 ships, 3 part of alpha wing and one individual ship. Saved the mission and received several warnings about ships needing a valid departure anchor. This was followed by the following warning: Ship name "<error>" referenced, but this ship doesn't exist.

Steps To ReproduceCreate new missions with 4 fighters as Alpha wing. Drop in a ship with a docking bay. Add a bomber. Set Alpha wing to depart via docking bay with a time delay. Do the same for the bomber. Save the mission.

Attached mission has the above done.

Select Alpha 2,3,4 and the bomber. Open the ship editor. Change AI class to general. Hit next or previous. Save mission (good idea to give it a new name).
Additional Informationr9673. The bug does not occur if the bomber is set to depart via hyperspace. I haven't tested changing any other values or departure combinations since it's almost 7am and even staying awake to do a test mission for this report was hard enough.
TagsNo tags attached.
Attached Files
  • ? file icon 2869.fs2 (6,753 bytes) 2013-05-11 05:56




FSF (reporter)

Issue still present in 3.7.5. The ship editor dialog takes over the departure location (hyperspace/docking bay) from the bomber (as that one is not in a wing), and subsequently applies it to all selected ships (see CShipEditorDlg::update_ship()). However, the departure anchor (the owner ship of the docking bay) is only applied if the ship is not in a wing. The ships in Alpha now have a docking-bay departure set without ship, causing <error> to be written to the mission.

Solution proposed in PR 595, only setting departure/arrival locations if selected ship is not part of a wing.


Goober5000 (administrator)

Fixed in PR 2108, the replacement PR for 595.

-Issue History
Date Modified Username Field Change
2013-05-11 05:56 FUBAR-BDHR New Issue
2013-05-11 05:56 FUBAR-BDHR File Added: 2869.fs2
2016-04-17 15:07 FSF Note Added: 0016827
2019-10-13 14:56 Goober5000 Assigned To => Goober5000
2019-10-13 14:56 Goober5000 Status new => resolved
2019-10-13 14:56 Goober5000 Resolution open => fixed
2019-10-13 14:56 Goober5000 Note Added: 0016931
+Issue History