Inconsistent datalink contacts

[WelshZeCorgi]

Ever notice that sometimes the datalink contacts are refreshed constantly, staying on the TID without disappearing, yet sometimes, the datalink contacts popup for a few seconds, then disappear for a few seconds, then pop up again for a few seconds (in their new position along their predicted flight path) then disappear again, slow strobing like it needs a redbull? What's causing that and is there a way to fix it?

Edited March 9, 2021 by WelshZeCorgi

[BreaKKer]

6 minutes ago, WelshZeCorgi said:

Ever notice that sometimes the datalink contacts are refreshed constantly, staying on the TID without disappearing, yet sometimes, the datalink contacts popup for a few seconds, then disappear for a few seconds, then pop up again for a few seconds (in their new position along their predicted flight path) then disappear again, slow strobing like it needs a redbull? What's causing that and is there a way to fix it?

AWACS datalink refresh rate

[Northstar98]

7 hours ago, WelshZeCorgi said:

Ever notice that sometimes the datalink contacts are refreshed constantly, staying on the TID without disappearing, yet sometimes, the datalink contacts popup for a few seconds, then disappear for a few seconds, then pop up again for a few seconds (in their new position along their predicted flight path) then disappear again, slow strobing like it needs a redbull? What's causing that and is there a way to fix it?

 

I've always thought it was due to update rate of the RADAR, and maybe HB's implementation is assuming that they aren't sending a persistent track file, and are instead just giving you what the RADAR of your host is seeing at a particular moment.

 

The other thing, though a little unrelated; shouldn't NTDS combine different sensors and then give you one picture? Instead of having multiple hosts each with a picture of just hat the host is seeing? So if you have a CBG for instance and an E-2, instead of each ship being an individual host, and when you tune into them you only see what they see, their sensors would datalink to a central host and then that's what you'd use and see on the TID. If that makes sense.