reported TDOA - Weird visual bug

[_SteelFalcon_]

MP track from a testing session with some friends.

Somehow the SA-6 symbology gets stuck to the edge of the HAD page, no matter the range scale.
the dashed line of #1 ends at the location of the SA-6 but for me it was always stuck at the edge of the display.

Even when nobody was commanding TDOA anymore, the symbol remained stuck in place despite changing direction

Unsure how to relably replicate however. I was pretty far away at the point where TDOA was commanded the first time

CAC_TEST_GBAD_Regiment-20231019-205656.trk

Edited October 19, 2023 by _SteelFalcon_

[Lord Vader]

Hi @_SteelFalcon_

Thanks for bringing this to us. I've raised this internally for analysis.

[Tomahawk]

Recently when flying Mission 9 Part 2 of the Weasels over Syria Campaign I had some issues with the HAD.
It had happened before once in Mission 5.

During Mission 9 it happened twice at pretty much the same time. Both times I restarted the mission. The problem happened a third time later in the mission and was suddenly gone after a few minutes.

I would lock up a target and then TMS left for TDOA. In some instances the track was suddenly lost. The HAD started showing weird bullseye positions and the HAD was not usable anymore. It still updated and showed emitters but I couldn't lock them up anymore because I had no Cursor. The error happens around 1:30:30 (Time on the clock in the DED) in the attached track.

Tomahawk

fail2.trk

Edited November 4, 2023 by Tomahawk

[dutchili]

Same in multiplayer. I could not get it to work.
I locked a SA-6 radar via the HAD page, TMS left long to send it to my human wingman. I got the TDOA HUD symbology. Wingman got 'data received' audio message and TDOA HUD symbology ("- - >") pointing towards the target. 
However, the lines on the HAD page were not showing. We did sometimes see a solid white line from own ship to 'nowhere' or a blue dashed line from master to target. But never the expected white dashed line from slave to target.
Wingman was unable to lock the target. Neither ever got the TD-M or TD-S indications.

@BIGNEWY Seems broken.

[BIGNEWY]

We will take a look. 

thank you

[pchRage]

nullThis was an odd one, sorry I do not have a track, was in MP, Sinai...

4-ship flowing towards target area.  a SnowDrift popped up on HAD.  I TMS UP'd it, got a lock, and then proceeded to TMS Left long to send TDOA.

The wingman lines started to connect to the locked emitter, and then the SD dropped off the HTS/HAD (ie it went dark, etc). 

Kaboom!  My HAD bricked.  the cursor disappeared, and there was that -2 billion values for the cursor-to-bullseye value (red circled in screenshot).

I tried TMS down, I tried changing THREAT classes, EOM/PB/etc modes.  I tried locking a target in TGP , FCR... I tried cycling to NAV, A2A, nothing worked.

I even powered off the HTS hardpoint, turned it back on, waiting till it spun back up.. and it was still bricked.

 

[Lord Vader]

Hi @pchRage

Unfortunately without a proper track we simply cannot analyse what's happening. We've tested TDOA recently and couldn't observe what you describe.

[pchRage]

Thanks.  When i have time ill try setting up a sp msn where i can use a radio cmd to deactivate the sam while tdoaing and see if i can get a repro

[sasquatch98]

I just had this exact same issue multiplayer on Syria although my target was a hawk but bricked in exactly the same way. I don’t have track file for it but I’ll try to reproduce in sp to get one. 

[WHOGX5]

On 3/19/2024 at 11:54 AM, Lord Vader said:

Hi @pchRage

Unfortunately without a proper track we simply cannot analyse what's happening. We've tested TDOA recently and couldn't observe what you describe.

We just had 9 aircraft brick their HADs when performing TDOA in our mission tonight. So this issue definitely exists. Exact same symptopms with cursor bullseye being several millions of miles away.

[Lord Vader]

Again, if you guys can get us tracks, as short and as concise as possible, it would help us trace the issue. 

[Moonshine]

has already been reported here:

and similar issue here:

[Moonshine]

Are you still in need for a track replay? The first post linked shows the same issue and already has a track attached to it plus is marked as reported.

[BIGNEWY]

We are good now it seems, I have merged the threads and a report has been made. 

thank you