Jump to content

Recommended Posts

Posted

Try first removing the awacs and then recreating it. Remember to set the D/L on (frequency 127)

PC: i7-13700K - Gigabyte RTX 5080 GAMING OC - 64GB DDR5 6400 - VPC MongoosT-50CM3 - VKB GF pro - MFG Crosswind - Msi MPG321UR-QD + LG OLED 32GS95UE - TrackIR5 - Quest 3

Posted (edited)
I loaded up an old Nevada mission, added Hornets & TomCats.

Problem... TomCats receive Datalink info & the Hornets Do Not !! From AWAC...

 

Link 4 seems encoded into the Tomcat, so is unaffected.

 

The Hornet's Link 16 needs AWACS to have their data link enabled "EPLRS(on) -a" in 'Advanced Waypoint Actions'. Older missions have this missing as it's a new option for AWACS, etc.

 

The easiest way to do this is to change your E-3A's to E-2D's and then back to E-3A's as this lets them keep their routes, orbits, etc. and add the datalink automatically.

 

attachment.php?attachmentid=209093&stc=1&d=1555878588

 

IIRC you may also need to add "EPLRS(on) -a" to any AI F-15C, F-15E, F-16C, etc. if you wish them to be F/F donors to the data link.

 

Link 16 enabled units : https://forums.eagle.ru/showthread.php?t=233587

 

Note: If there are still issues, you might need to check for conflicting TACAN channels (i.e. from tankers), as they used to cause datalink issues as well.

Screen_190421_211807.thumb.jpg.2a59d70cb53e90f20d7969988b59a162.jpg

Edited by Ramsay

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...