Jump to content

Recommended Posts

Posted

Hi, I have been adapting one of the Syria F14 missions included in the release so I am flying the Hornet instead. Changed the jet no issue, nothing else......however, when tuning the tacan, mother was not showing up, just got the spinning indicators round the HSI...all obvious things checked carefully. In ME, tacan was showing turned on at that waypoint in advanced conditions.

 

What would prevent a tacan beacon from being picked up in the jet ? Also had this in another mission where I added a player jet to the carrier.

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.

CVW-17 Profile Background VFA-34.png

Posted

Hi, does it have to be directed at a particular flight? I thought it just emitted and anyone tuning to that frequency will pick it up?

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.

CVW-17 Profile Background VFA-34.png

Posted

Well, i'm a totally noob and i think you are right, but i can use tacan only when i put my flight ID in the advanced condition; i don't know why, but make a try...

Maybe someone can explaine me why you need to specify a particular flight ID...

 

(sorry for my english...)

Posted

 

here is a video of me seting up a quick and dirty mission you can see how to set up the tacan and ICLS

in the advance action tab your not for the tacan your not setting the flight you are.

you need to set it the unit ID # of the carrier

you telling the mission editor what unit the tacan signal is pointing to / centered on

yep its redundant the way ED dose it having to go to a tab that is for only one unit and tell it use the only unit here to set it, probably this because how the mission editor passes code around under the hood

Posted
yep its redundant the way ED dose it having to go to a tab that is for only one unit and tell it use the only unit here to set it, probably this because how the mission editor passes code around under the hood

It's that way because the carrier can be, and usually is, part of a group. Since waypoints and actions are shared by the entire group, the mission editor needs to know which individual unit that TACAN signal should be bound to.

Posted
It's that way because the carrier can be, and usually is, part of a group. Since waypoints and actions are shared by the entire group, the mission editor needs to know which individual unit that TACAN signal should be bound to.

 

Now i understand, thanks.

  • Recently Browsing   0 members

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