[REPORTED]FARP comms broken?

I started the deployment Campaign (about time!), and I noticed the FARP comms might be broken...

Up until now I always departed from an actual airbase, so I'm not familiar with FARP procedures, but it seems something's wrong.

No matter the mission, if I select the FARP frequency and open the ATC menu, I can see the "Abort takeoff" option, which is ok (since the mission starts with the engines running and everything's ready); but after I take off, the ATC menu for the FARP stays the same forever, with just the "abort takeoff" option, no matter what I do.

I can sucessfully communicate with ATC as I'm able to "abort takeoff" (even when I'm already airbone). So it's not a radio problem; it's useless anyway since now I can only request permission for startup and I cannot declare inbound.

It's not a big deal, I know. I've been able to complete the first 5 missions with the FARM comms broken; though it's quite annoying having to locate it at night if you can't declare inbound so they turn on the lights...

Has anyone experienced this? Is it just the campaing or does it apply to all FARPS?

its a bug still hasnt fixed for months unfortunetely

For a reason I can't understand, you need to establish contact with the next ATC instance in the list for inbound and azimuth request, even if it has a different name. And you can't use that one for startup and takeoff clearance.

They use the same frequency though.

It's like this in most missions. Don't ask me why.

wait...what? Really?!?!

I'll give it a try, just in case. It still smells like bug, though...

More like a mission-builder-workaround due to an by-ED-longtime-ignored-bug...

I started the deployment Campaign (about time!), and I noticed the FARP comms might be broken...

 

Has anyone experienced this? Is it just the campaign or does it apply to all FARPS?

Haven't checked if that is a current bug with the radio system, but that campaign you mention definitely has missions where the radio frequencies and or names are missing from the FARPS so would cause issues, and may not even have a command vehicle / building near the FARP to provide radio comms.

I have a fixed version of it up on the ED user files section if you wanted to give that a try. (Fixed version has english voice overs instead of russian accent).

https://www.digitalcombatsimulator.com/en/files/1744245/

Except from changelog:

---------------------------

Mission - DEPLOYMENT 01 (Fam Flight).miz

---------------------------

- Triggers

- Added Win and Loss messages.

- Added English Voice Overs.

-

- Waypoints

- Aligned - All (on road waypoints) for vehicles to actual road

-

- Fixed Airport Coalitions

- Units

- Moved - FARP-VETKA to align to support structures and added a SKP for ATC

- Fixed - All FARP's radio frequencies to 127.5mhz as some were missing - HAD TO RELOAD FARP'S

- Fixed - (Ka-50 Player) missing textures by reselecting skin

- Fixed - All vehicles and aircraft Missing Skill levels

- DCSW v1.5x compatibility

- Works Fine

------------------------ DONE

---------------------------

Mission - DEPLOYMENT 02 (Escort).miz

---------------------------

- Triggers

- Added Win and Loss messages.

- Added English Voice Overs.

-

- Waypoints

- Aligned - All (on road waypoints) for vehicles to actual road

- All CAS aircrafts set to cas -a -x and Engage in zones set.

- Added "Switch waypoint" commands to make all attack aircraft loiter around Battle area

-

- Fixed Airport Coalitions

- Units

- Moved - FARP-VETKA to align to support structures and added a SKP for ATC

- Fixed - All FARP's radio frequencies to 127.5mhz as some were missing - HAD TO RELOAD FARP'S

- Fixed - (Ka-50 Player) missing textures by reselecting skin

- Fixed - All vehicles and aircraft Missing Skill levels

- DCSW v1.5x compatibility

- Works Fine

------------------------ DONE (Lot of working on message timing and ambush stuff)

Regards, Ian.

Hey MadDog! Your modified version was one of the first things I tried, but the FARP comms problem is still there.

As I said, it's not the comms are misconfigured; I'm able to call for aborting take off, and the FARP acknowledges the message. It's simply that once you are airborne, the "Abort takeoff" command never dissapears; so you can't do nothing but that.

Still need to check Holton181's workaround abot contacting the "next entry" in the ATC list...which is *weird*

I can vouch for the selecting the next ATC option. Happened to me in the first deployment mission. Was able to select the second ATC option then the inbound messages were populated properly.

Hey MadDog! Your modified version was one of the first things I tried, but the FARP comms problem is still there.

 

As I said, it's not the comms are misconfigured; I'm able to call for aborting take off, and the FARP acknowledges the message. It's simply that once you are airborne, the "Abort takeoff" command never dissapears; so you can't do nothing but that.

Roger that, just tested myself, comms is broken as you said.

FYI

https://forums.eagle.ru/showthread.php?t=180191

I run some tests yesterday, a single FARP structure (i.e. 4 pads) + required trucks.

Starter Mi-8 cold. One instance in radio menu. Could request startup, takeoff/hover and abandon takeoff. But not azimuth or landing, even if I flew some NM away.

Added a second FARP structure (i.e. 2x4 pads), same name and frequency. Two instances in the menu, both with request startup avaliable.

Selected one and on that one request takeoff/hover + abandon takeoff became avaliable, the other stayed as request startup untill I had moved some distance, then it turned to inbound and azimuth (the first stayed as abandon takeoff).

After landing the second one stayed abandon landing, first one turned to request takeoff.

The FARP structures can have different names and different frequency even if they are next to each other and share all assets. I've seen it in various missions.

Can't really understand why it is like this and why it hasn't been corrected for so long.

2020 and this bug is still in btw

I have asked for an update on the FARP comms issues.

 

Only seeing request take off and abort, no inbound option once airborne.

 

Thanks

I have asked for an update on the FARP comms issues.

 

Only seeing request take off and abort, no inbound option once airborne.

 

Thanks

pls add another bug to the list:

FARP 4x and 1x (Single Helipad) the comm menue is broken. Singlepads are only dots in the F5 Radio menue, all other airports and 4x Farps are there, the Singlepads are only dots and no names like Torba, or Kalaitka, Dallas....

Simple Testmission: place a red or blue FARP with 4 pads and place a Singlepad too. place a heli on one and open the F5 ATC Menue.

On 4/8/2020 at 11:48 AM, BIGNEWY said:

I have asked for an update on the FARP comms issues.

 

Only seeing request take off and abort, no inbound option once airborne.

 

Thanks

inbound comms also no reply in my case with KA50

Ok I use Vaicom so I never put the comms menu.. but I tried and seems that startup and take off are admited. BUT once you are airborn, the press of the key to make appear the coms is not showing it. Once you land anywhere and on ground they appear again (I thought that tracks would save in single mission but it seems only saves in multiplayer)

edit: no problem I have seen that the comms menus appears with ralt+/

Hi, 

Just thought I'd ask if any progress has been made on this issue please.

Stay safe and safe flying everyone.

5 hours ago, KoalaDoraemon said:

Hi, 

Just thought I'd ask if any progress has been made on this issue please.

 

Stay safe and safe flying everyone.

Hi! Like I answered in the thread about the Ka-50 mission. It works fine, as long as you select the correct frequency!

Cheers!