[1900.18] (Re-uploaded due to error) Mission execution error

[erick33]

Due to some errors in the scenario, I have reproduced the exact same issue and am reporting it again.

After conducting multiple tests, it appears that there is a difference in mission execution times across certain bases. I could not figure out the cause of this discrepancy, especially since I did not configure anything differently in the mission settings.

To resolve this, I created a separate strike mission for the same target and set the maximum attack distance to 2000nm. While this made the mission execution times consistent, a new issue arose: the aircraft transitioned into the "Engaged Offensive" state, preventing the strike mission's course from being plotted. (This specific issue is not included in the attached scenario, but you will be able to observe it if you try reproducing it yourself.)

An issue has been identified where a common mission assigned to aircraft across multiple bases executes normally at certain bases, but aircraft at the other bases fail to sortie entirely.

Steps to Reproduce:

Open the attached scenario and switch to the China side.

Run the simulation.

Observe the "CSG-11 strike," "CSG-2 Strike," and "CSG-12 Strike" missions assigned to bombers across multiple bases.

The missions execute normally at two of the bases, but bombers at the remaining bases do not sortie at all.

This issue was discovered after making several troubleshooting attempts (e.g., reassigning aircraft, recreating missions from scratch) to fix a previous bug where aircraft would immediately RTB right after taking off when the mission started.

[Raptorx7_slith]

They're being engaged by ASBM's and shared amongst a few other missions

[erick33]

They're being engaged by ASBM's and shared amongst a few other missions

Even if we remove the ASBM mission and exclude other miscellaneous missions, you can check the exact same results. I will upload a scenario shortly that clearly demonstrates there is a problem.