Jump to content

Recommended Posts

Posted

Zo I've been practicing landing on the USS Tarawa with the harrier, and i've having issue with the proper comms to use for a case 1 landing. I get as far "as see you at 10" readback, then I land and get a improper communication message for my rating.

Is this just a bug from the supercarrier module? Or something else?

  • 2 weeks later...
Posted
Zo I've been practicing landing on the USS Tarawa with the harrier, and i've having issue with the proper comms to use for a case 1 landing. I get as far "as see you at 10" readback, then I land and get a improper communication message for my rating.

Is this just a bug from the supercarrier module? Or something else?

 

I don’t have the super carrier module and all I am getting currently is the standard ATC replies for a ground based airfield. A few patches back we were getting sea based carrier ATC replies so I don’t know what happened.

  • 5 months later...
Posted

I have the same issue. I get as far "as see you at 10" then nothing more. After landing the message "no proper comms".

 

Is there a solution? Or is it WIP?

System Specs: AMD Ryzen 7 5800X, RX 6900 XT, 64GB RAM // Tobsen CM Kollektiv, VPC CM3 Throttle, VPC WarBRD Rudder Pedals, VPC T-50 CM2 + WarBRD Base  VR: HP Reverb G2

Helis: UH-1H / KA-50 3 / Mi-8 / Mi-24P / SA-342 / AH-64D / OH 58D / CH-47F  Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C II / AV-8B / AJS 37 / MIG-21bis  / F-16C / F-15E / F-4E 

Maps: Nevada / Persian Gulf / Normandie 2.0 / Syria / South Atlantic / Sina / Cold War Germany  WWII: Spitfire / WWII Assets Pack  Tech.: Combined Arms / NS430 / Supercarrier    

Waiting for:  BO-105 / G.91R / Tornado IDS / Eurofighter

Posted

I am using the Tarawa for landing.

 

 

System Specs: AMD Ryzen 7 5800X, RX 6900 XT, 64GB RAM // Tobsen CM Kollektiv, VPC CM3 Throttle, VPC WarBRD Rudder Pedals, VPC T-50 CM2 + WarBRD Base  VR: HP Reverb G2

Helis: UH-1H / KA-50 3 / Mi-8 / Mi-24P / SA-342 / AH-64D / OH 58D / CH-47F  Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C II / AV-8B / AJS 37 / MIG-21bis  / F-16C / F-15E / F-4E 

Maps: Nevada / Persian Gulf / Normandie 2.0 / Syria / South Atlantic / Sina / Cold War Germany  WWII: Spitfire / WWII Assets Pack  Tech.: Combined Arms / NS430 / Supercarrier    

Waiting for:  BO-105 / G.91R / Tornado IDS / Eurofighter

Posted

It doesn't matter, you are using SC ATC (some parts of SC ATC got through to the non SC users AFAIK), and it's not working yet with the pattern the Harriers are using. Also, Tarawa landing operation has been not really working for a while now.

 

The "best" thing you can currently do is fly the pattern with out comms at all until that gets fixed.

  • Thanks 1
  • 1 month later...
Posted

You don't change it, it is "simulated" only. You just remain on the same frequency and continue the approach until something gets changed in SC ATC

Posted

Hm, but on the same frequ nothing changed after this message. The only thing i was able to select was "F1 abort inbound"

Specs:
12th Gen Intel(R) Core(TM) i9-12900K   3.20 GHz,  RAM 128 GB, Win11 Home, RTX3080Ti

  • 2 years later...
Posted

I think all comms is a core issue not module.

  • Like 1

The only way to make sense out of change is to plunge into it, move with it, and join the dance.

"Me, the 13th Duke of Wybourne, here on the ED forums at 3 'o' clock in the morning, with my reputation. Are they mad.."

https://ko-fi.com/joey45

 

Posted

Best you can do is use MOOSE and the AIRBOSS script. Specifically has a Tarawa plug-in that is actually pretty good. The Tarawa comms, in the base game,  are broken at the moment. 

  • Recently Browsing   0 members

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