AI time-based missions not firing//Aircraft will not RTB when ordered

[alghblag]

Hi there. Two problems I'm having with this scenario:
1. I set a lot of missions up for the AI, intending them to begin at a certain time, but they do not start.
2. Player aircraft will not reliably RTB when ordered. They will respond to the order for a few seconds, then revert to 'Unassigned.'

Mission attached. I am a longtime CMO player but a first-time creator, so I may be setting things up wrong, but I cannot figure out how. Thank you for your help!

[Raptorx7_slith]

What version of the game are you playing?

[alghblag]

Version 1.07.1527

[blu3s]

It looks like that scen is over the limit of what CMO can handle, can you isolate the missions and create a more manageable save?

[thewood1]

The number of complaints about performance and issues in that scenario lend it be used as an example of why we can't have nice things.

[alghblag]

Can you elaborate on what might exceed CMO's capabilities here? The point of the scenario is to be enormous, but I played the 2022 version (very slowly) without trouble a few years ago. This version is actually slimmed down by several thousand AU, and the RTB issue only appeared to crop up with the 1527 version update.

I'm a longtime CMO player but novice creator, so the time-based missions might just be due to my bad setup, although I can't tell how. The RTB thing seems to be a genuine bug.

I'm trying to figure out how to attach the in-play version where both problems are actively occurring but even a ZIP file exceeds the forum's limits!

[thewood1]

"I'm trying to figure out how to attach the in-play version where both problems are actively occurring but even a ZIP file exceeds the forum's limits!"

I think thats a pretty good sign of reaching practical limits. All building over-sized scenarios like that will do is force the devs to eventually put a hard limit on number of units. Especially when you start consuming support resources because you broke something.

[blu3s]

Basically what we need to investigate a problem is the simplest scenario where the problem occurs so that it is easily reproducible. In a scenario with thousands of units it is quite complicated to investigate why something happens, that's why I asked for a simplified version where the problem occurs.

There is no hard limit on units as it depends on the system, what those units do etc, but in the end it's all about common sense. Command is now much more accurate and its performance is much better than in previous versions, but it is true that in certain key simulation phases it is “slower” because it needs that accuracy to work as it should.

[alghblag]

I see. I will set up a smaller scenario and see if either problem replicates, much appreciated.