Build 1868: Strike missions frequently stall in Form-Up phase during normal gameplay, but work in Editor mode
Posted: Sun May 24, 2026 5:36 pm
Bug Report
Game Version (Public Beta): 1.09 – Build 1868
Database Version: DB3K v517
Severity: Major
Frequency Very frequent / highly reproducible (Example is attached)
Subject
Strike missions with escorts frequently stall in the Form-Up phase during normal gameplay, but work in Editor mode
Description
Strike missions - especially those with escorts assigned - appear to behave inconsistently depending on whether they are executed from the Editor or during normal gameplay using “Start New Game”
In normal gameplay, strike packages frequently become stuck around waypoint 3 and remain indefinitely in the Form-Up phase. From my observations, the issue seems to occur more often when escorts are assigned to the strike mission, although the missions occasionally execute correctly for unclear reasons.
What makes the issue particularly confusing is that the same missions generally work correctly when launched directly from the Editor. Because of this, the problem was not immediately obvious during scenario creation and testing inside the Editor. It only became apparent during normal playtesting, when the strike packages never arrived at their targets.
This behavior is highly disruptive because it can completely prevent strike missions from executing during gameplay.
Steps to Reproduce
Attached Files
Additional Notes
Game Version (Public Beta): 1.09 – Build 1868
Database Version: DB3K v517
Severity: Major
Frequency Very frequent / highly reproducible (Example is attached)
Subject
Strike missions with escorts frequently stall in the Form-Up phase during normal gameplay, but work in Editor mode
Description
Strike missions - especially those with escorts assigned - appear to behave inconsistently depending on whether they are executed from the Editor or during normal gameplay using “Start New Game”
In normal gameplay, strike packages frequently become stuck around waypoint 3 and remain indefinitely in the Form-Up phase. From my observations, the issue seems to occur more often when escorts are assigned to the strike mission, although the missions occasionally execute correctly for unclear reasons.
What makes the issue particularly confusing is that the same missions generally work correctly when launched directly from the Editor. Because of this, the problem was not immediately obvious during scenario creation and testing inside the Editor. It only became apparent during normal playtesting, when the strike packages never arrived at their targets.
This behavior is highly disruptive because it can completely prevent strike missions from executing during gameplay.
Steps to Reproduce
- Load the attached scenario.
- Start the simulation normally using “Start New Game”
- Observe the Red side strike missions attacking Blue targets.
- Note that some strike packages become stuck around waypoint 3 and remain indefinitely in the Form-Up state.
- Run the same scenario directly from the Editor.
- Observe that the strike missions execute correctly there.
Attached Files
- Strike-Mission Test 1.zip
Additional Notes
- Red side conducts three strike missions against Blue targets.
- The issue appears significantly more common when escorts are assigned to the strike package.
- The missions occasionally execute correctly even in normal gameplay, but the trigger for this difference is unclear.
- Because the issue prevents strike packages from reaching their targets, it is effectively game-breaking.
- In my opinion, this issue should be addressed with high priority.