[Fixed]1.08 Build 1676 Enemy Mission Start Times Ignored

[Tred]

Hi All.

Before I do a bug report I thought I'd better ask first: Is there something about the new mission features I don't know about that would cause CPU Side Mission Start times to be ignored?

I have a large scenario I've been trying to finish playing for ever a year now. With every update, the computer AI (North Korea) has always stuck to mission time triggers. But with the newest update less than two minutes in, they are firing everything disregarding the mission start time triggers (Scud's, other Missiles, looks like even my 'ground incursion' mission). This has never happened with any previous update.

I'll try to reset the missions with the new update and see if that does it, but wanted to ask to see if I'm missing something with the new update, or it might be a bug, or what.

Thanks.

[blu3s]

Yes, this is a bug and it's fixed for the next CMO update

[Tred]

Hi Blue. Did you mean that this was supposed to be fixed for 1706? Or the next official update? I recently upgraded to the 1706 beta but it's still happening to me on there.

Thanks.

[blu3s]

Hi Blue. Did you mean that this was supposed to be fixed for 1706? Or the next official update? I recently upgraded to the 1706 beta but it's still happening to me on there.

Thanks.

Yes, this is working on 1706, but please update the scenario where it's not working so we can take a look

Thank you

[Tred]

Okay, I don't know what's going on here. Below is a very large scenario I created a long time ago with a little bit of everything in it and designed to play in my micro-managed style.

In the scenario you'll notice that North Korean missile strikes, ground incursion, artillery barrage etc. are not supposed to trigger until well over an hour into the game, which begins at 0600 zulu. It always worked fine until Build 1676 when the reported bug occurred. I upgraded to 1706 recently, and those missions still fire just a few minutes into the game now like they first started to in 1676.

But it gets stranger: I had assigned individual units within groups (for example all the missile complexes) to specific missions, and if you click on them individually you see they are listed as assigned to those missions. But things get all confused if you look at the mission box and the list of units assigned there. They no longer correspond.

I tried rebuilding the missions. I tried replacing all the specific units and reassigning them individually again like I always used to do (ie right-clicking on the unit and assigning missions that way rather than in the mission editor box) but it no longer works that way. Even in 1706.

And this issue looks specific to this scenario. I tried a little test scenario after you said this was fixed in 1706, and that worked just fine. So I'm baffled as to what the problem is here.

Thanks.

Preempting North Korea.zip

(5.49 MiB) Downloaded 3 times

[Nikel]

Monster scenario, note that there are missions with hundreds of targets and it is not recommended by the devs, the engine will struggle.

I see that the missions are not active, they are firing for other reason, Engaged Offensive (Standoff).

EOS.png (91.66 KiB) Viewed 87 times

[Tred]

It is a monster of a scenario. One day I hope to actually be able to play it through. Lol. It runs slow, but never had this issue before.

I wondered if opportunity targeting was making the missions fire prior to mission start time. Doesn't seem to be it. That would be a different bug. But there are several strange things happening in it. For instance the long range missiles targeting US bases in Japan, allocated to four different targets manually, are all firing at Iwakuni instead...without waiting for the mission start time to begin.