MBot Posted July 27, 2023 Posted July 27, 2023 AWACS datalink in DCS has a transmit range of about 180 NM. If the receiver is within 180 NM of the AWACS it can receive datalink contacts. But AWACS will not share any which are beyond 180 NM from itself, even though AWACS can detect them on its radar. The attached track starts with an enemy bomber 220 NM from the AWACS. It can detect the bomber as evident by making a BRA call. But the target is not shared via datalink to the player's F-14. Only after the bomber closes to within 180 NM of the AWACS will it start to share the datalink contact with the F-14. Datalink range should be relevant only for the distance between the AWACS and the receiver, not the distance between the AWACS and the target. AWACS should share any target which it detects with its own radar (which can be at distances up to 350 NM). Datalink.trk
MBot Posted August 30, 2023 Author Posted August 30, 2023 May I kindly ask if this has been acknowledged?
Flappie Posted March 30, 2024 Posted March 30, 2024 Hi @MBot. Sorry for not reviewing your thread sooner. Your track does not work anymore so I made my own, and what I see looks worse than what you described last summer: an E-3A only sends my Tomcat what's less than 100 nm away from him. Am I doing something wrong? E3A and F-14B.trk ---
MBot Posted May 10, 2024 Author Posted May 10, 2024 That is quite interesting. It seems that the datalink transmittal range is also somehow depending on the target's attributes. Indeed in your track I also see less than 100 NM. But if you make the bombers hot instead of cold, the first 3 are transmitted immediately. If you make them high, all six are transmitted. At first I though that it's because AWACS just doesn't see the low/cold targets itself, but even in your mission if I ask for a picture he reports 3 groups while he still only transmits the closest on datalink (under 100 NM). For a high and hot target I get 180 NM max. 1
Recommended Posts