[FIXED] v1.08 B1676 Mission Start Times Ignored

[Tred]

Hi all.

I've never had this happen before so I'm assuming it's a bug in the latest update. Now, the computer side is ignoring the start times for activating missions.

In this test (and in a custom scenario I've been trying to finish without annoying bugs for a year now), the North Korean Scud's and Nodong missile strike missions are set to activate at specific times, but instead they launch after a few minutes. Is there a new mission setting I don't know about?

Hope I do this right...

Test.scen.zip

(19.54 KiB) Downloaded 1 time

[Tred]

Is nobody else seeing this problem? Makes me think I'm missing a new mission setting I don't know about or something.

[thewood1]

I was just playing and watching missions on the AI side for Bersama Lima in Standalone scenarios. They missions all fired at specific times set by the designer with no issues. So they at least work in that scenario. I also have my benchmark scenario running with no issues on the AI side as far as I can see.

I'll look at yours if I get a chance.

Edit...just realized my benchmark was activating through an event with Time or Detection so its an invalid test. I'll check your later tonight.

[Nikel]

It is a bug (both in 1674 an 1676), just tried in 1662 and works correctly.

Changed the Scud Strike mission because it was not a land strike (it is an air intercept), once changed it works.

[blu3s]

Yes, confirmed bug, is fixed for next release

[Tred]

Thanks everyone. I looked at my big personal scenario and it appears other missions (A ground incursion I have set up and an artillery barrage) are also not waiting until their mission start times anymore either. I assume it's all the same bug.