reported Atflir doesn't undesignate in certain circumstances when using TOO

[Bri01]

Tested it with gbu38. You cannot undesignate target

[Tholozor]

Got a track?

[ponch17]

I have the same from last update .. if i Want use helmet system to designate a ground tgt i got this circle with somme Lines around it then i can select my tgt . But impossible to undesignate with NWS switch to get this circle again to select an other tgt . 

[BIGNEWY]

Please attach short track replays showing the issue. 

thanks

[MarcT-NL]

I can confirm. ATFLIR and Lightning are.... behaving differently. Can't undesignate anymore.

I'll make a track totday, but it's realy not that difficult to reproduce I think. I experienced it on a MP-server btw.

[MarcT-NL]

Apparently it's the GBU-38's. As soon as the TPOD designates a target, those coordinates are in the JDAM's memory. If you undesignate, you undesignates the TPOD, but not the JDAM's memory. The FA-18 doesn't know how to handle that and keeps displaying the target from the JDAM's memory. Those are the symptoms anyway.

Might be a bug, or actually designed like that (which would not even surprise me). It works fine with LGB's for example. I expect the same bug with the JSOW's, but haven't tested it yet.

No difference between ATFLIR and Lightning2, no difference between SP and MP.

undesig at gbu12 sp.trk undesig at gbu38 sp.trk

Edited May 6, 2022 by MarcT-NL

[BIGNEWY]

One of our closed beta testers has reproduce and reported

thank you