TACAN is broken on specifically Sinai.

[ChaosRifle]

On Sinai specifically is seems (I have not witnessed it on other maps, only Sinai), tuning to a TACAN channel for a carrier, or airfield (only tested Azzaqaziq) will return the wrong location. It appears to be a floating point error, where the closer you get, the less error there is.
The beacons drift around as you get closer, and slowly drift onto the actual location. This is minimal for airfields, only a few lengths of the runway off, but for the supercarrier this is extremely bad, and the beacon can be off by well over 80nm and as you get closer can move towards the right spot at over mach 10. This also breaks ACLS (automated landing) on the carrier because it requires an accurate tacan beacon, and even when right on top of it, it is still off by a little bit.

Notable reproduction information:
Testing done on a server, on Sinai, in an F18 Hornet, using TACAN for terrain/tech locations (airfield/carrier). for airfields I have only tested Azzaqaziq.
Easiest way to see it is be greater than 150nm from location(supercarrier is the worst one by far), tune to tacan, fly towards the beacon, watch the HSI page in the hornet and see the tacan beacon moving around in ways it simply should not.
71X on Teddy.

Edited September 17, 2023 by ChaosRifle

[Minsky]

You need to provide a track.

Just tried this in SP and MP, and carrier's TACAN worked perfectly fine on both occasions.

Sinai_Tacan.trk

[HawkEXO]

Tacans work for me in Mirage F1 and A4

[Recoil16]

I agree with Minsky that you should supply a track, or at the very least tell us which specific TACAN channels you're seeing this on. Sinai currently has multiple duplicate TACAN channels (all reported I believe), so if you're on one of them you may be seeing different TACAN stations "fighting" with each other.

[Hinkey]

Found the other thread on this issue. My problem was assigning TACAN 71X to a carrier which is already in use on the map.

Edited January 9, 2024 by Hinkey