can not reproduce OB 2.7.11.22211 - Hornet A2A Radar lock does not undesignate (updated)

[StixxAus]

A locked air target cannot be undesignated.

Lock and track air target in either RWS or TWS and/or STT
Bug will not undesignate, HUD symbology maintains tracked target, radar keeps target bugged.
You can select next target but not undesignate them, only cycle through.

You have to manually move bug to new air space outside of scan to undesignate or move aircraft outside of gimbal limit of the radar.

Tested in Stable and targets can be undesignated.
No mods installed and using the same joystick profiles on both OB and Stable.
 

Edited April 7, 2022 by StixxAus

[Tholozor]

Press RSET on the right side of the attack format to clear the L&S target. The NWS/Undesignate button will step the L&S target through ranked track files if not in STT, this is by design.

Edited April 1, 2022 by Tholozor

[AusGoose]

Just to clarify what StixxAus is saying, the issue is the STT not un-designating. Even when the radar target has been destroyed, the lock remains on a non-existent target irrespective.

Thanks for the input Tholozor but there has been a miscommunication here; can confirm not being able to 'unlock' a radar contact is certainly not by design.

Thanks!

Edited April 3, 2022 by AusGoose
Spelling

[StixxAus]

This is still an issue with OB 2.7.11.22211

F/A-18 A2A radar contact in STT will not undesignate when selecting NWS/Undesignate.

[Tholozor]

On 4/3/2022 at 1:49 AM, AusGoose said:

Thanks for the input Tholozor but there has been a miscommunication here; can confirm not being able to 'unlock' a radar contact is certainly not by design.

 

The original report did not mention STT before it was edited, leading to the misunderstanding. Without a track to watch I had to take it at face value.

[StixxAus]

trk file attached.
Flown with current stable build.

F18 No Lock Drop.trk

[MARLAN_]

I'm not seeing any issue, although I'm on the latest OB, I've never noticed an issue with this in previous versions which is now the current stable.

Note that "lock" very specifically means to be in STT, nothing else (there is no "soft lock" or "hard lock" it's a community misnomer). What most say is a a "soft lock" is just a designation (L&S) and the undesignate switch while certainly a little bit confusing, doesn't actually remove designations, it steps through them (If no L&S exists, create one on the priority track; if an L&S exists: step to the next priority track; if both L&S and DT2 exist: step between them.)

Undesignate should return to search when actuated during STT, STT RAID, Spotlight, AACQ or ACM -- in all other modes (RWS, VS, TWS, TWS SCAN RAID) it should step through track files.

[BIGNEWY]

The team and I have tried to reproduce but have been unable. 

 

[Hobel]

On 4/1/2022 at 4:48 AM, StixxAus said:

A locked air target cannot be undesignated.

Lock and track air target in either RWS or TWS and/or STT
Bug will not undesignate, HUD symbology maintains tracked target, radar keeps target bugged.
You can select next target but not undesignate them, only cycle through.

You have to manually move bug to new air space outside of scan to undesignate or move aircraft outside of gimbal limit of the radar.

Tested in Stable and targets can be undesignated.
No mods installed and using the same joystick profiles on both OB and Stable.
 

 

When you are in the TWS, the only way to solve the target is the OSB reset button. Or scan somewhere else, but this creates other "uglinesses"
Whether this is so in the real F18 I do not know,

In general, however, this is a very unattractive solution.

[StixxAus]

A fresh reinstall of DCS + modules has resolved the issue for me.
I had no 'mods' installed and it was occurring in stable and open beta (before it went stable).

 

[AusGoose]

Last I checked the issue was still present for me.

Ill see if I can reproduce it, and then what a reinstall does. Definitely was an issue I had too, but good that a reinstall fixes it.

Goose

[Teriander]

I came to see if others were having this issue as well and it looks like I'm definitely not alone.

 

I can not believe ED says they can not reproduce this issue.  It happens to me every time on the GS server.  Destroyed bandits will sometimes remained locked even after the bandit has crashed into the mountains.  Breaking lock is impossible unless I cycle ACM modes.  Undesignate will not break the lock of the destroyed target.  

It is random, but it definitely happens.  A new bug since 2022.  NEVER had this issue on previous F-18 patches.  

[Hobel]

On 4/15/2022 at 7:28 AM, StixxAus said:

A fresh reinstall of DCS + modules has resolved the issue for me.
I had no 'mods' installed and it was occurring in stable and open beta (before it went stable).

 

okay and with which funtkion do you drop the lock now?

Both in TWS or RWS, which button do they use there?

[Tholozor]

3 hours ago, Hobel said:

Both in TWS or RWS, which button do they use there?

Press RSET.

[Hobel]

15 minutes ago, Tholozor said:

Press RSET.

yes I know as I have also written above.

Because above he also writes something about NWS/Undesignate. which did not work.

Now I just wanted to know again exactly what did not work before and now works again.
That does not go out from his previous  texts namely exactly

Edited April 23, 2022 by Hobel

[Tholozor]

Gotcha, misunderstood the question.