Jump to content

Carrier TCN missing on MFCD and HUD


euthyphro

Recommended Posts

I'm having the same issue. Seems like it went away after the last update.

 

Can't confirm, working without issue for me

i7 - 9700K | 32 GB DDR4 3200 | RTX 2080 | VKB Gunfighter Mk II /w MCG Pro | Virpil T-50CM2 Throttle | TrackIR 5 | VKB Mk. IV

 

AJS-37 | A/V-8B | A-10C | F-14A/B | F-16C | F-18C | F-86F | FC3 | JF-17 | Ka-50 | L-39 | Mi-8 | MiG-15bis | MiG-19 | MiG-21bis | M2000-C | P-51D | Spitfire LF Mk. IX | UH-1H

Link to comment
Share on other sites

Was doing traps last night. No issues using missions that were created many months ago.

Asus Z690 Hero | 12900K | 64GB G.Skill 6000 | 4090FE | Reverb G2 | VPC MongoosT-50CM2 + TM Grips  | Winwing Orion2 Throttle | MFG Crosswind Pedals

Link to comment
Share on other sites

Works fine for me. Are you sure that you're tuning in the correct channel and band etc and that the unit actually has TACAN activated? Also, there are limitations on which TACAN channels are valid, because some of them interfere with the datalink. The limitations are different for A/A and T/R. Wags mentioned it a while ago in the Hornet mini updates.

Try something like 70X T/R and see if it works.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

Are the limitations simulated?

 

Yes

i7 - 9700K | 32 GB DDR4 3200 | RTX 2080 | VKB Gunfighter Mk II /w MCG Pro | Virpil T-50CM2 Throttle | TrackIR 5 | VKB Mk. IV

 

AJS-37 | A/V-8B | A-10C | F-14A/B | F-16C | F-18C | F-86F | FC3 | JF-17 | Ka-50 | L-39 | Mi-8 | MiG-15bis | MiG-19 | MiG-21bis | M2000-C | P-51D | Spitfire LF Mk. IX | UH-1H

Link to comment
Share on other sites

Tnx. Where I can find details about that?

 

With the search function in this here forum ;)

 

https://forums.eagle.ru/showpost.php?p=3821502&postcount=139

 

Edit: I'm hijacking the thread, do you know how to set up tcn dme/dme between two F-18?

 

Tacan Yardstick channels have to be 63 apart, e.g. Lead aircraft 5Y, then flight needs 68Y to get ranging information.

i7 - 9700K | 32 GB DDR4 3200 | RTX 2080 | VKB Gunfighter Mk II /w MCG Pro | Virpil T-50CM2 Throttle | TrackIR 5 | VKB Mk. IV

 

AJS-37 | A/V-8B | A-10C | F-14A/B | F-16C | F-18C | F-86F | FC3 | JF-17 | Ka-50 | L-39 | Mi-8 | MiG-15bis | MiG-19 | MiG-21bis | M2000-C | P-51D | Spitfire LF Mk. IX | UH-1H

Link to comment
Share on other sites

With the search function in this here forum ;)

 

https://forums.eagle.ru/showpost.php?p=3821502&postcount=139

 

This post was back in March. I've made 50+ missions since then and have used 25X for the Stennis in most of them. It is still working working in missions built before the last update, but it's not working in missions built since. Help. :)

Hm, I don't remember if I made any new carrier ops missions lately. Certainly working with older missions. I'll make a new one today and test it, if I have time. Although I use 74X for Stennis, so it might just be an issue of your chosen channel. A campaign I downloaded a few weeks ago uses 37X for the carrier and that works still. I'll test with 74X and 25X.


Edited by Harker

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

I tested in a new mission on Caucasus. I could tune in to the carrier in T/R mode on 25X and to a tanker on 13Y just fine, getting accurate range and bearing info. AWACS was present and the datalink connection remained up the whole time. I shouldn't be able to get any info on those channels. So that's interesting, I guess...

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

I've noticed lately that the TACAN has a tendency to "freeze" in MP. It's an easy fix. Turn the receiver off, then turn it back on again.

 

 

I've seen this. I've seen TCN not work for some carriers randomly in MP and some work fine and have had all carriers work fine. The latest test I've been doing is to make sure to have the frequency dialed in prior to turning on the receiver or when changing carriers to shut off TCN then clear and change frequency then turn it back on. Has worked well so far but not nearly enough testing done to call it a work around.

Link to comment
Share on other sites

Got to see it again today in MP. I had the TACAN dialed in on the UFC, HSI on the left DDI, TCN boxed on the DDI and was 2-3 NM aft of the carrier turning in for landing and the signal just up and disappeared.

 

 

 

 

I got the signal, just no TACAN beacon or heading selection on my HSI.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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