[UNABLE TO REPRODUCE] SA Page too laggy/ghosts at low altitudes

[Raijin]

Since last update I've noticed more than usual lag and ghosting in the SA page.

Sometimes showing (for long periods) the bandit in front of me, while he is already behind.

 

This track is one I got just for report purposes.

The issue can be noticed after I shot missiles on a Mirrage 2000. There was a friendly and 2 mirrages.

 

In another day (no track) I was trying to surprise a bandit at @14 (I was on the deck) and after I climbed the mountain that separated us (1-3nm) SA showed me cold and in front of me, while he was in fact turning into my 6. Checked tacview and there was no one nearby.

 

TRK FILE: https://drive.google.com/open?id=1mfxkgZCtxSvtkcAeUx_ii5j8yT1P0HjC

 

Regards,

[Bobik2002]

I think signal and radios can't go over mountains.

 

Odesláno z mého Mi A1 pomocí Tapatalk

[Raijin]

I think signal and radios can't go over mountains.

 

Odesláno z mého Mi A1 pomocí Tapatalk

 

That's a different thing Bobik. If for any reason Awacs cannot know where the contact is, it should just take it away from SA (or blink),,,

 

In this case, it shows the trackfile teleporting around. That shouldn't happen even if he was buried into the ground.

Edited July 19, 2019 by Raijin

[Raijin]

FYI, It was not that severe before this update. (we had similar problems few updates ago too)

[Harker]

There's a delay between the contact moving, being detected by the AWACS and having its position being updated on the Datalink and then you getting the update over Link-16. Also, a contact is not immediately considered lost if it's not detected in a single radar sweep and its position is extrapolated, based on its previous heading and speed. It'll flash as lost and disappear once it reaches the non-detection limit (could be a few seconds, could be more, I don't know).

 

Thus, a maneuvering target that may also happen to avoid AWACS detection for a sweep will look like it's jumping from one place to the next, on the SA page.

 

I may be wrong with the above analysis, but I wouldn't rely on the SA page much for actively engaged WVR targets. They're turning around, dogfighting etc and their position is not updated quickly enough to match their maneuvering.

[Raijin]

There's a delay between the contact moving, being detected by the AWACS and having its position being updated on the Datalink and then you getting the update over Link-16. Also, a contact is not immediately considered lost if it's not detected in a single radar sweep and its position is extrapolated, based on its previous heading and speed. It'll flash as lost and disappear once it reaches the non-detection limit (could be a few seconds, could be more, I don't know). Thus, a maneuvering target that may also happen to avoid AWACS detection for a sweep will look like it's jumping from one place to the next, on the SA page.

I may be wrong with the above analysis, but I wouldn't rely on the SA page much for actively engaged WVR targets. They're turning around, dogfighting etc and their position is not updated quickly enough to match their maneuvering.

 

It's funny how everyone on the forums assume they know more than u.

 

IT"S WARPING in locations where it couldn't be physically considering their speed and altitude.

[Banzaiib]

It's funny how everyone on the forums assume they know more than u.

 

IT"S WARPING in locations where it couldn't be physically considering their speed and altitude.

 

100% this... it's like at work when someone reads the first line of an email and then responds without looking at the whole thing or the attachments...

[Bobik2002]

And what about lags of your PC internet or server?

 

Odesláno z mého Mi A1 pomocí Tapatalk