Matrix Games Forums

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 very 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

1. Load the attached scenario.
2. Start the simulation normally using “Start New Game”
3. Observe the Red side strike missions attacking Blue targets.
4. Note that some strike packages become stuck around waypoint 3 and remain indefinitely in the Form-Up state.
5. Run the same scenario directly from the Editor.
6. 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.

Incidentally, the SEAD escorts do not automatically fire at the radar in the attached mission, even though they should according to WRA. I suspect this is related to the following issue:

https://forums.matrixgames.com/viewtopic.php?t=417142

The issue persists in CMO v1.09 Build 1876. Aircraft assigned to strike missions continue circling at waypoint 3 (“hold end”) until they hit bingo fuel and return to base, unless the scenario is run directly from the editor.

I’ve just installed build B1877. The same problem persists. I’m surprised that no one else has reported this issue or encountered it themselves. In a standard simulation, this makes conducting air operations virtually impossible for me, as a core element of the game isn't working. I’ve uploaded a video of the problem here:

https://youtu.be/tItOodtf2qU

I reported this issue but it seems i have the wrong version even though i was running the official version. not sure they took it seriously or not but you explained it better

https://forums.matrixgames.com/viewtopic.php?t=417393

jason oates wrote: Wed Jun 10, 2026 8:28 pm I reported this issue but it seems i have the wrong version even though i was running the official version. not sure they took it seriously or not but you explained it better

https://forums.matrixgames.com/viewtopic.php?t=417393

In your save, the F-35s proceed on their mission and attack the targets when you run it in B1825 or in the last beta.

And this happens both in normal play and in the editor.

Perhaps the bug is not happening because they are not escorted.

I have tried several times and the result is always the same.


The last official version is 1.09.1825.15

@Nikel: Did you try out my test scenario on the "red" side on your machine? If so, what behavior did you observe?

I can try reinstalling CMO and reapplying B1877, but I haven't noticed any error messages or crashes. Otherwise, everything seems to be working. The official version v1.09 – Build 1825.15 also worked without this issue.

Uzabit wrote: Wed Jun 10, 2026 10:12 pm @Nikel: Did you try out my test scenario on the "red" side on your machine? If so, what behavior did you observe?

I can try reinstalling CMO and reapplying B1877, but I haven't noticed any error messages or crashes. Otherwise, everything seems to be working. The official version v1.09 – Build 1825.15 also worked without this issue.

In your scenario I see the bug you reported

The bug seems to be related with 8 min holding time in 3 Hold End.

If you remove the take off time, they will proceed with the mission.

When the ACs are airborne, they will also proceed with the mission if you click on "Clear time" in the flightplan editor.

These are the flightplans compared with and without the take off time, or when you click on "Clear Time".

When you play in the editor the 8 min hold also happens, however this time is reduced as the scenario advances (the third pic below), what does not happen in normal play, remaining at 8 min.

Hey Nikel, thanks for checking.

The flight plans are automatically generated, meaning I don't set the hold time.

Of course, I can manually influence the AI's behavior by editing the flight plan or unassigning and reassigning the flight on the player's side.

The big problem is that if enemy strike packages with launch times have been set, manual intervention isn't practical and would ruin the scenario design.

You are right, of course.

We fixed an error related to this scenario for the next update.

Sorry, this is not fixed in the newest Build 1892.

Planes on strike missions with active Take-Off Time are still stuck at waypoint 3 (Hold End) and won't continue their missions.

Just curious if the missions were generated before or after you applied the patch. I noted that changes in logic won't be applied to existing plans, but only new ones.

Just created a new scenario with the last build and the problem is the same.


There is a 8 minutes Hold on Waypoint 3 Hold End.

- If you play in the editor, the 8 minutes are progressively reduced until 0 and the mission continues.

- If you play through "Start New Game", the 8 minutes remain forever and the mission cannot continue.


However I do not see the fix in the changelog.



Videos comparing both modes of playing.

I reply for the record to help the developers.

The issues seems to appear in flight plans (Strike or Patrols with flight plans) that include HOLD START - HODL END WPs. An "Assembly" WP substituting for those two seems to solve this particular problem.

Nikel wrote: Sat Jun 27, 2026 2:11 pm Just created a new scenario with the last build and the problem is the same.


There is a 8 minutes Hold on Waypoint 3 Hold End.

- If you play in the editor, the 8 minutes are progressively reduced until 0 and the mission continues.

- If you play through "Start New Game", the 8 minutes remain forever and the mission cannot continue.


However I do not see the fix in the changelog.



Videos comparing both modes of playing.



EP.gifNP.gif

Can you share that scenario?

I tried just launching the MDSP tutorial about ToT. Create the mission with the F-15, click on generate flightplans, everything works fine.

I also tried with a blank scenario, added two sides a couple of targets and 4xF-15. Then in player mode I create the mission and run it with no issues.

blu3s wrote: Mon Jun 29, 2026 8:57 am Can you share that scenario?

I tried just launching the MDSP tutorial about ToT. Create the mission with the F-15, click on generate flightplans, everything works fine.

I also tried with a blank scenario, added two sides a couple of targets and 4xF-15. Then in player mode I create the mission and run it with no issues.

Here it is.

But don't you see it happening in Uzabit's scenario?

Thanks, and yes I can repro with that one, but I can't see the logic why some works but not others. Btw, all of them have been added to the ticket 0017386

I got same problem with u. especially during multi dimension tutorial. thats really annoying