Un-droppable allied-detected contacts.

[Knightpawn]

I would like to discuss a behavior that might be WAD or reportable and that is what I want to understand.

In scenarios where there are allies to the player, if an allied sensor detects an underwater contact (maybe this applies to any contact but my issue is with goblins) which, in the player's judgment, is not worth pursuing (eg obviously a false target or biologic, or - more importantly - a submarine with a then large uncertainty zone), if the player drops the contact the latter disappears for a moment and reappears as originally detected by the first allied sensor.

This is annoying because in an ASW patrol when a contact is detected in the patrol / prosecution zone the platforms assigned to the patrol try to engage and stop dispensing sonobuoys. In many cases when the uncertainty about the location of the contact has become large, it makes sense to "drop", and start searching all over again from scratch rather than hovering above a contact detected 1 hr ago.

Your views

[Nikel]

I have searched the forum, is it the same that was reported in this thread in CMANO times?


https://forums.matrixgames.com/viewtopi ... 9#p3638609


May you post a save?

[Knightpawn]

From a cursory look not exactly the same case.

One can drop a contact if that contact has been detected by a player sensor. But if the contact is from an allied sensor the allies are so kind as to continue reporting the contact regardless of the player's faded interest in it, or how old the contact is.

I understand my ally reporting a new detection of the same contact after my dropping it. But why cling to the past?

[blu3s]

Yes, when a contact is reported by other side, atm you are not able to properly drop it, since the allied side will share any uptades to that contact.

[Knightpawn]

Yes, when a contact is reported by other side, atm you are not able to properly drop it, since the allied side will share any uptades to that contact.

The nuance is that they don't share updates to the contact but their retained past image - the one I have dropped

[Nikel]

Is this the problem?

Saving the Third Temple, 1973 by BeirutDude.

DS.gif (8.62 MiB) Viewed 245 times

[Knightpawn]

I guess the following would be a good test algorithm.

• Have an ASW patrol of allied helos detecting a goblin contact (set RoE to hold so that they dont attack).

• The contract will be shared with the player.

• Tell the Helos to RtB.

• When they leave the area, the player drops the contact.

If the contact re-apprears for the payer, then it is not an update; it is the old retained knowledge of the ally that is communicated again.