[LOGGED][Build 1774] There is a bug where the mission is triggered despite the required conditions not being satisfied

[erick33]

In the scenario, I created a combined CSG Strike mission against the enemy carrier group. The mission was assigned to the aircraft on the carrier, and it was configured to activate when the distance to the target was 490 nm.

However, during actual gameplay, I observed that the mission started even when the target was still about 570–600 nm away. I am reporting this issue for your review.

If you load the attached scenario in Editor Mode, switch the perspective to China, and observe the situation, you can verify the behavior described above.

[blu3s]

The mission has no max strike radius

[erick33]

The mission has no max strike radius

It seems the file attachment was incorrect, but the same issue still occurred even after setting the maximum strike radius. I tested it several times with both 490 nm and 400 nm, and the same behavior happened each time.

[blu3s]

I'm unable to repro the issue in the scenario attached or in a scenario from scratch.

Time passed and all the flights are still landed and no flight plan has been generated.






Can you try to recreate the issue in an isolated scenario?

[erick33]

I'm unable to repro the issue in the scenario attached or in a scenario from scratch.

Time passed and all the flights are still landed and no flight plan has been generated.






Can you try to recreate the issue in an isolated scenario?

Even though I reset the mission in the same scenario, the same issue continued to occur (Mission_auto_start file). However, during multiple test runs, I was able to identify an important clue. When using an ELINT satellite, the satellite detects enemy ship emissions but displays their location very inaccurately, showing a wide boxed-area instead of a precise position. In this situation, the system incorrectly assumes the target is within range, even though the actual location is much farther away, which appears to cause the mission to trigger improperly.

After deleting the ELINT satellite, this issue disappeared, and the distortion of the mission route also stopped. (I am attaching the Cut through dealock_start.save file.) Should this be considered WAD?

[blu3s]

That's an interesting case, thanks for pointing it.

Dimitris recently fix that if the contact of the mission has a very large AoU the mission shouldn't triggered so that might help to avoid the mission being triggered.

I tested a simple scenario with the max strike radius and known contacts and mission only launches when contact is at range

[erick33]

That's an interesting case, thanks for pointing it.

Dimitris recently fix that if the contact of the mission has a very large AoU the mission shouldn't triggered so that might help to avoid the mission being triggered.

I tested a simple scenario with the max strike radius and known contacts and mission only launches when contact is at range

Is this fix applied in Build 1774?

[blu3s]

No, it's in the new beta, B1776

[erick33]

No, it's in the new beta, B1776

Thank you for checking! I hope you have a great day.

[erick33]

That's an interesting case, thanks for pointing it.

Dimitris recently fix that if the contact of the mission has a very large AoU the mission shouldn't triggered so that might help to avoid the mission being triggered.

I tested a simple scenario with the max strike radius and known contacts and mission only launches when contact is at range

Unfortunately, testing has shown that the issue still persists: missions are being triggered due to wide-area unit detection by the ELINT satellite. It may be because the same scenario was used for testing, but I wanted to report it for your reference

[Dimitris]

Logged #17514