(Beta 1728.2) Strike and escort missions fail to execute – aircraft never take off

[Uzabit]

Bug Report
Game Version (Beta): 1.08 – Build 1728.2
Database Version: DB3K v513
Severity: Major

---

Subject
Strike and escort missions fail to execute – aircraft never take off (Beta 1728.2)

---

Description
The current Beta Build 1728.2 appears to have serious issues with air mission execution.

While testing a scenario I’m developing on Build 1676 with the current Beta 1728.2, I initially noticed that the escort flights in a NATO strike package never launched. After further investigation, it turned out that none of the aircraft in the strike package — including both the strike element and the escorts - actually took off.

To confirm, I created a dedicated test scenario (Strike Test Build 1728_2) using DB3K v513. The mission was a simple “Strike – Land Strike” tasking: a strike package with escorts attacking an isolated target in the Nevada desert.
Surprisingly, in this test not a single aircraft launched. The mission engine generated flight plans but kept recalculating and updating them continuously. No aircraft ever departed Nellis AFB.

When I manually launched the aircraft, they took off but then drifted aimlessly with no navigation or mission behavior.

I then rebuilt the same scenario on Build 1676 with DB3K v512 (since newer saves aren’t backward compatible). Under 1676, everything works correctly - the aircraft launch on schedule, form up, and attack as planned. On Build 1728.2, however, the same mission logic results in complete inaction.

I verified the integrity of the Steam installation, and no issues were found. Unfortunately, these mission execution problems currently make Beta 1728.2 unusable for air operations, as a core game function fails or behaves unpredictably.

---

Update
After further testing, the issue seems to occur only when both of the following conditions are true:

• A Take-Off Time or Time on Target is set to a specific Zulu time.
• Escorts are assigned to the same mission.

If either of these conditions is removed - for example, if no specific timing is set or if the escorts are unassigned - the mission executes normally.

---

Steps to Reproduce

1. Load Strike Test Build 1728_2.scen (DB3K v513).
2. Ensure the mission has both a Take-Off Time or ToT set and escorts assigned.
3. Run the simulation - note that the entire strike package (strike aircraft + escorts) remains grounded while the mission plan recalculates repeatedly.
4. Manually launch the aircraft - they take off but drift aimlessly with no mission logic.
5. Remove either the escorts or the Take-Off/ToT setting - the mission then executes normally.
6. Compare with Strike Test Build 1676.scen (DB3K v512) on Build 1676, where all aircraft operate as expected.

---

Attached Files

Strike Test.zip containing:

Strike Test Build 1676.scen

Strike Test Build 1728_2.scen

Counterfire at Dawn – Shield over Thuringia.scen (WIP scenario; missions from NATO Mauler strike package with escorts do not launch under 1728.2)

---

Additional Notes

• Issue verified across multiple test cases on v1676 and v1728.2, and with both databases (DB3K v512 vs. v513).
• Steam installation integrity check passed with no errors.
• Behavior consistently reproducible - aircraft remain grounded or lose all navigation logic after manual launch.
• The issue affects both strike and escort elements within the same mission when timing parameters (Take-Off/ToT) are defined.

[Uzabit]

Update: It seems the issue is related to having either a Take Off Time or Time On Target set for the mission. When both timing parameters are removed, the mission triggers and executes normally.

[DWReese]

I have experienced this before. I believe that it is related to the method you assign the planes to the mission. If you are in the mission screen, and you highlight the unit and then use the arrow button to drop the planes down to the assigned area, then you can experience this problem. It has happened to me so many times hat I have given up doing that. But, if you go to the base, and highlight the planes at the base that you desire, and then use the assign mission button on THAT SCREEN, then the mission works every time. Hopefully, I explained it well enough.

[Uzabit]

I have experienced this before. I believe that it is related to the method you assign the planes to the mission. If you are in the mission screen, and you highlight the unit and then use the arrow button to drop the planes down to the assigned area, then you can experience this problem. It has happened to me so many times hat I have given up doing that. But, if you go to the base, and highlight the planes at the base that you desire, and then use the assign mission button on THAT SCREEN, then the mission works every time. Hopefully, I explained it well enough.

I have just tested assigning the aircraft directly from the Air Operations menu, with the same result as before. Upon closer inspection, the missions fail to execute only when both of the following conditions are true:

• A Take-Off Time or Time on Target is set to a specific Zulu time.
• Escorts are assigned to the same mission.

If either of these conditions is removed — for example, if no specific timing is set or if the escorts are unassigned — the mission executes normally.

[blu3s]

Thanks for the report

Logged 17013