Jump to content

Recommended Posts

Posted

as tittle,Carrier John Tacan need to be set AA and it can track the Tacan channel!

somebody said i didn't set it well,but i did,it happens to me,anyone of you met this?:cry:

Posted

The carrier TACAN is set as an advanced waypoint action on the carrier's first waypoint OP. Never encountered the Stennis requiring A/A mode.

DCS Wishlist: | Navy F-14 | Navy F/A-18 | AH-6 | Navy A-6 | Official Navy A-4 | Carrier Ops | Dynamic Campaign | Marine AH-1 |

 

Streaming DCS sometimes:

Posted
In all missions I've made so far Stennis requires T/R + A/A to be set for TCN to work.

 

some mission i made,just like yours,need TR and AA both on,so it can contact!:book:

Posted

Odd, it works just fine here...

Spoiler

Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero
VPC MT-50CM2 grip on VPForce Rhino with Z-curve extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings
Win11 Pro 24H2 - VBS/HAGS/Game Mode ON

 

Posted

T/R works fine here. But there is an issue, i had to actually make the carrier move. Just adding TACAN in ME command wasn't enough.

X-Plane 11.5x / DCS 2.5.6 / P3Dv5 / Aerofly FS 2 / War Thunder

 

Win10-x64 | ASUS Z390 Maximus VI | Intel i7-9700K @3.6GHz | Corsair Vengeance LPX 32 GB DDR4 | 6TB SSD Samsung 850 Pro | 2TB M2 PCI 4x | ASUS GTX 1080 ROG STRIX 8GB DDR5X | TM Hotas Warthog | Saitek Combat Pedals | Oculus Rift S

Posted

CVN-74 Default TACAN channel does not work

 

Hello

 

Steps to reproduce the possible bug:

-Place CVN-74 in Mission Editor

-Check the advanced waypoint default option - should be Activate TACAN channel X1

-Fly the F-18

-Turn ON the TACAN, T/R, set to X1

 

The Aircraft Carrier is not visible on the HSI

 

 

However it works for any other X channel if set as an advanced option in Mission Editor for CVN-74

Posted

I can confirm this bug.

 

Tacan channel 1X do not work as standard.

- I did not check if you remove the text and make a new tacan 1x channel if that work.

 

In the editor do the following to make it work.

Select the carrier stennis and select advanced waypoint.

Delete the TACAN channel X1

make a new command and select Tacan channel 55X instead.

 

If you program tacan channel 55X in the F18c then it will work.

Also the default radio for the carrier is 127.500 but you cannot see this anywhere.. It would be nice if this info was visible ingame when clicking on the carrier.

Posted (edited)

I had this bug after today's update as well.

 

Step to reproduce:

1. Create empty mission

2. Add carrier on map (it automatically gets TCN 1X action assigned)

3. Add Hornet

4. Fly, select TCN 1X, no receive, select AA, receive.

 

I checked the mission file and found this

 

["action"] = 
{
["id"] = "ActivateBeacon",
["params"] = 
{
	["type"] = 4,
	["frequency"] = 1088000000,
	["callsign"] = "TKR",
	["channel"] = 1,
	["modeChannel"] = "X",
	["bearing"] = true,
	["system"] = 4,
}, -- end of ["params"]
}, -- end of ["action"]

 

I checked a different mission where I had manually removed and re-added the activate beacon action and it includes the following param, that is missing above

 

["params"] = 
{
["frequency"] = 1016000000,
["type"] = 4,
       [u][b]["AA"] = false,[/b][/u]
["callsign"] = "CV74",
["channel"] = 55,
["modeChannel"] = "X",
["bearing"] = true,
       [u][b]["system"] = 3,[/b][/u]
}, -- end of ["params"]

Edited by Ahmed
  • Recently Browsing   0 members

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