Page 1 of 1

[Resolved] Strike mission target list order bugged (Build 1147.10)

Posted: Sat Sep 12, 2020 4:44 am
by Grazyn
So, reading "FIXED: #14120: Strike Mission target list not evaluated correctly" in the release notes made me think that strike missions had finally been tweaked to go down the list of targets in the order provided. This does not seem to be the case (or maybe this is not the meaning of "evaluated correctly"). Not only is the order ignored, it's also lost after you reload a save.

To reproduce:
>load scenario
>drag select all ground targets, create new land strike mission
>manually order the targets (e.g. school, radar, turbine, comms jammer, control tower, police station)
>memorize or write the list down for later
>check "pre-planned targets only" if unchecked
>add the 4 B-2s to the mission
>SAVE
>unpause and watch as the bombers engage the targets in a random (albeit somewhat consistent between reloads) order
>reload the save
>go to mission editor, notice how the list is now scrambled
>unpause, watch as the bombers also fail to follow the order of the now-scrambled list


RE: [Logged] Strike mission target list order bugged (Build 1147.10)

Posted: Sun Sep 13, 2020 10:08 pm
by Rory Noonan
Logged for investigation.

0014134

RE: [Logged] Strike mission target list order bugged (Build 1147.10)

Posted: Sat Oct 17, 2020 1:39 pm
by SteveMcClaire
Hi Grazyn -- the UI allowing you to order the strike mission targets is a general part of the mission editor UI that doesn't actually apply in this case. Strike mission targets are prioritized based on distance from the attacking unit (or from mission planner waypoints.) The order of the list isn't actually a factor.

So the near-term resolution for this issue is to remove the arrows that let you re-order the list when strike targets are being displayed, as these do imply the order is significant. I've also made the UI target list order consistent between reloads.

Giving the player the ability to specify a prioritized list of targets is under discussion, but this is a larger feature request. Thanks!