Recoil16

Already reported, thank you

The latest domestic AIP can always be found here: https://www.gov.il/he/Departments/Guides/aip?chapterIndex=1 The link in question says "פמ"ת בקובץ יחיד - הורדה" ("PMT in a single file - download", according to Google Translate). That being said, the current direct link to the PDF is here: https://www.gov.il/BlobFolder/guide/aip/he/aip_Full PAMAT 3-23.pdf

Just to be clear, while this will "fix" it in the sense that you can then use the TACAN, the problem is not actually with the Hatzerim TACAN. It is confirmed to be on 96X by Israeli Air Force documentation. It's rather the Wadi Al Jandali TACAN that is either on the incorrect channel, or (in my opinion more likely) it should not exist at all, as there is no antenna visible on real world satellite images where the Wadi TACAN is placed in game. So yes, while this is an interim "fix" you can do for yourself in the moment, this should not be the long term solution to be implemented for the map as a whole.

Yeah, as pointed out by Ahmed, this is not a bug, rather it is expected behavior that has (finally) been implemented after it was missing for so long. The DME component of a TACAN beacon is functionally the same as the DME component of a VOR/DME. @BIGNEWY I think we can close this as "correct as is".

An excellent point actually. DMS coordinates without decimal seconds as given here are only accurate to about 30 meters (in latitude, with longitude precision differing depending on the latitude but let's not get into that right now), which is 100ft as you say.

It's an easy way to show to the devs exactly how, where, and under what circumstances damage is occurring, which is presumably why Flappie is asking for it. A coordinate - while it points out the bump - doesn't do that.

Previously reported internally

Correct, and it has been reported. I'll see if it can be bumped again.

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.

I agree with ASAP, you should probably try something lower. 15k/215 KIAS (+/-) is a quite comfortable place, which is in line with the NATO AAR planning docs.

@tripod3 Line 60 of sensors.lua should read declare_sensor(TALL_KING) it currently reads declare_sensor(BAR_LOCK) Due to this small error, the radar does not actually properly detect targets, as it has no valid sensor.

This is previously reported internally.

You can find the 476th Nevada FLIP in their shared publications: https://www.476vfightergroup.com/content.php?381-shared-publications

Hey, in principle, yes, I just haven't gotten around to it in a while. I'll probably try to tackle it when I find some spare time next to other projects.

I wouldn't really be concerned with sim organizations (like virtual squadrons) using them without proper licensing, likely nobody is gonna care. But shipping them as part of a commercial product would be another thing.