Strike Mission GUI Bug (Confounded Buttons on Target Page)
Posted: Fri Mar 17, 2023 11:23 am
On the Targets page of the strike mission GUI, I believe that the Focusing on Strike Targets / Opportunity Scrambling button is confounded with the Targets Destroyed: RTB/ Continue Mission button.
In the attached scenario, I have one mission to represent each of the four permutations. My observations:
-the FST GUI option maps to RTB behavior. (Missions 1 and 4)
-the OS GUI option maps to CM behavior (Missions 2 and 3)
-The Target Destroyed: RTB GUI option maps to OS behavior.
-The Target Destroyed: CM GUI option maps to FST behavior.
For the last two, you can confirm what I am saying by checking what the "Target Destroyed" button selection does to the ...strikemission.Strike.StrikePrePlan Lua variable for the associated mission. (CM -> StrikePrePlan = Yes, RTB -> StrikePrePlan = No). The FST/OS GUI button seems to have no effect on StrikePrePlan.
I admit that the example suffers from low fuel situations; in my own testing I've occasionally thrown in a tanker make things less urgent.
Perhaps it matters that I use English/US localization?
In the attached scenario, I have one mission to represent each of the four permutations. My observations:
-the FST GUI option maps to RTB behavior. (Missions 1 and 4)
-the OS GUI option maps to CM behavior (Missions 2 and 3)
-The Target Destroyed: RTB GUI option maps to OS behavior.
-The Target Destroyed: CM GUI option maps to FST behavior.
For the last two, you can confirm what I am saying by checking what the "Target Destroyed" button selection does to the ...strikemission.Strike.StrikePrePlan Lua variable for the associated mission. (CM -> StrikePrePlan = Yes, RTB -> StrikePrePlan = No). The FST/OS GUI button seems to have no effect on StrikePrePlan.
I admit that the example suffers from low fuel situations; in my own testing I've occasionally thrown in a tanker make things less urgent.
Perhaps it matters that I use English/US localization?