Jump to content

Maximum TACAN distance ?


Top Jockey

Recommended Posts

Hello,

I went very far from the Carrier, and at the F-14's HSI monitor I keep getting the TACAN direction needles / arrows and the range digits to the Carrier keeps updating also.

... I've managed to go 620 nm from the Carrier and the TACAN info kept updating.

 

- Caucasus Map

- F-14A

- CVN-74 (no Supercarrier)


Can a Carrier TACAN signal get that far IRL ?

Wasn't it supposed for the needles and the range digits to disappear after one gets too far away ?


 

Hangar
FC3 | F-14A/B | F-16C | F/A-18C | MiG-21bis | Mirage 2000C ... ... JA 37 | Kfir | MiG-23 | Mirage IIIE
Mi-8 MTV2

system
i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB

Link to comment
Share on other sites

Quote

Operating range is approximately 300 NM, if line of sight is given.

https://www.heatblur.se/F-14Manual/general.html#tacan-system-an-arn-84

 

Wiki says:

Quote

TACAN stations can provide distance up to 390 nautical miles.


Edited by draconus

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Rift S   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

24 minutes ago, draconus said:

 

Yeah, I had the far recolection that it could be around 350 or even less.

 

So, assuming that when out of range from the Carrier TACAN, the info on the HSI (needles and range), as well as the deviation bar at the VDI and HUD should disappear - just like when entering the wrong TACAN channel ?

This is probably a bug, as I've managed to get TACAN signal from ranges of more than 950+ nm.

 

Screen_231012_224336.jpg

 

Screen_231012_213757.jpg


Edited by Top Jockey
  • Thanks 1

Hangar
FC3 | F-14A/B | F-16C | F/A-18C | MiG-21bis | Mirage 2000C ... ... JA 37 | Kfir | MiG-23 | Mirage IIIE
Mi-8 MTV2

system
i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB

Link to comment
Share on other sites

6 minutes ago, Top Jockey said:

 

Yeah, I had the far recolection that it could be around 350 or even less.

 

So, assuming that when out of range from the Carrier the info on the HSI (needles and range), as well as the deviation bar at the VDI and HUD should disappear, this is probably a bug, as I've managed to get TACAN signal from even 950+ nm.

 

Screen_231012_213757.jpg

Screen_231012_224336.jpg

Have you tried that with other aircraft too?

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Link to comment
Share on other sites

1 minute ago, QuiGon said:

Have you tried that with other aircraft too?

 

Not yet.

Hangar
FC3 | F-14A/B | F-16C | F/A-18C | MiG-21bis | Mirage 2000C ... ... JA 37 | Kfir | MiG-23 | Mirage IIIE
Mi-8 MTV2

system
i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB

Link to comment
Share on other sites

Just now, Top Jockey said:

Not yet.

Would be interesting to know if it's a general DCS issue or a Tomcat specific issue. I might test that myself when I find the time to do so as I'm curious now.

  • Like 1

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Link to comment
Share on other sites

2 hours ago, QuiGon said:

Would be interesting to know if it's a general DCS issue or a Tomcat specific issue. I might test that myself when I find the time to do so as I'm curious now.

 

I've been testing with the Hornet in roughly the same circumstances as the Tomcat, and the 'behavior' seems more plausible.

... although with some doubts from my part, as I do not have the slightest idea as how it really works in IRL.

 

- flying at 40.000 ft or above, it appears to get a solid TACAN reference at distances from 430 ~ 450 nm and below

- at those distances, it can sometimes get alternate random range readings of many different values, as if it is having difficulty in receiving a good, steady TACAN signal

- near 390 nm distance and below it gets definitely steady

 

On the other hand, it can also receive the Carrier TACAN signal at distances as far as 900+ nm ...

- even if for only a very small time fraction

- it does give correct distance (range) of 880.9 nm from Carrier - as in screenshot below, bearing marker, TKR Carrier code

- sometimes an " S " blinks instead of the TKR code

- after those very brief moments, the bearing marker may be lost or not, and the range readings get alternate random values again.

 

Concluding:

Is it realistic that even for very brief moments, (in good weather, high altitude) the Hornet could capture a Carrier TACAN signal from that far away ?

 

 

 

screencapture02.jpg


Edited by Top Jockey

Hangar
FC3 | F-14A/B | F-16C | F/A-18C | MiG-21bis | Mirage 2000C ... ... JA 37 | Kfir | MiG-23 | Mirage IIIE
Mi-8 MTV2

system
i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB

Link to comment
Share on other sites

The LOS horizon is 213nm at 40k ft alt but the VHF can propagate much longer due to the atmosphere effects/scatter. As for the signal that strong, I doubt it.

  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Rift S   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

22 minutes ago, draconus said:

The LOS horizon is 213nm at 40k ft alt but the VHF can propagate much longer due to the atmosphere effects/scatter. As for the signal that strong, I doubt it.

 

Ok, so should this issue be a bug report or what ?

Hangar
FC3 | F-14A/B | F-16C | F/A-18C | MiG-21bis | Mirage 2000C ... ... JA 37 | Kfir | MiG-23 | Mirage IIIE
Mi-8 MTV2

system
i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB

Link to comment
Share on other sites

10 minutes ago, IronMike said:

Looks like a DCS issue, I remember not receiving TACAN in the F-14 until in range before.

 

So might it be (in my case) related to be currently using a Open Beta version ?

Hangar
FC3 | F-14A/B | F-16C | F/A-18C | MiG-21bis | Mirage 2000C ... ... JA 37 | Kfir | MiG-23 | Mirage IIIE
Mi-8 MTV2

system
i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB

Link to comment
Share on other sites

Idk, I also tested F-15E and got signal degradation around 360nm and max around 400nm from CVN-74 TACAN. Much shorter to ground station (140-170nm) but it could be some LOS issue.

F-14 otoh has no limits to TACAN either with CVN-74, S-3 (Caucasus) or ground station (PG) - I stopped testing over 500nm.

@latest beta

F-14 PG GND TACAN.trk F-14 S-3 TACAN.trk F-14 CVN-74 TACAN.trk

  • Thanks 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Rift S   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

2 hours ago, draconus said:

Idk, I also tested F-15E and got signal degradation around 360nm and max around 400nm from CVN-74 TACAN. Much shorter to ground station (140-170nm) but it could be some LOS issue.

F-14 otoh has no limits to TACAN either with CVN-74, S-3 (Caucasus) or ground station (PG) - I stopped testing over 500nm.

@latest beta

F-14 PG GND TACAN.trk 109.91 kB · 0 downloads F-14 S-3 TACAN.trk 73.25 kB · 0 downloads F-14 CVN-74 TACAN.trk 208.6 kB · 0 downloads

 

Thank you @draconus

Those are my conclusions also, even tried on typical quickstart not much edited / not very old (past open beta versions) missions.

 

If, in most cases the F-14 can get the Carrier's TACAN signal until near ~ 560 nm or so, on other missions for resons I don't know it can get the Carrier's TACAN signal from more than 960 nm.

 

I suppose ED or Heatblur could look at this.

Hangar
FC3 | F-14A/B | F-16C | F/A-18C | MiG-21bis | Mirage 2000C ... ... JA 37 | Kfir | MiG-23 | Mirage IIIE
Mi-8 MTV2

system
i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB

Link to comment
Share on other sites

The rule of thumb is (1.22 * sqrt of the delta height in feet). This returns the distance in miles, either divide to convert distance to NM or use 1.06 as the coefficient in the formula.

Is the curvature of the earth modeled, or is it “flat” in DCS? The TACAN emitter is located on the mast on the carrier, at least 200 feet above the water as well. Guessing that isn’t modeled either. I’ve not checked to see if TACAN is masked by terrain either. TACAN operates on frequencies limited to line of sight. 


Edited by Victory205
  • Thanks 2

Fly Pretty, anyone can Fly Safe.
 

Link to comment
Share on other sites

12 hours ago, Victory205 said:

Is the curvature of the earth modeled, or is it “flat” in DCS? The TACAN emitter is located on the mast on the carrier, at least 200 feet above the water as well. Guessing that isn’t modeled either. I’ve not checked to see if TACAN is masked by terrain either.

The curvature is modeled for radars, for radios - idk. LOS is modeled for both.

  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Rift S   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

The huge indicated range to TACAN in the Hornet was a known bug, but I haven't experienced it lately.  What wyou did was you tuned the TACAN and you got some ridiculous range from it, then you turn off the TACAN and turn it back on  and the range was then correct.

@Victory205:  I do think terrain masks TACAN.  I've experienced it in the NNTR map for one--ducking behind a mountain and I'd lose the TACAN and it would come back when I crested it.  It think I saw it happen in the other maps too.

v6,

boNes

  • Like 2

"Also, I would prefer a back seater over the extra gas any day. I would have 80 pounds of flesh to eat and a pair of glasses to start a fire." --F/A-18 Hornet pilot

Link to comment
Share on other sites

  • Recently Browsing   0 members

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