correct as is F/A-18 Comms Menu Bug - ATC not available

[PrimetimeCasual]

It's entirely possible that I'm doing something wrong here, but nevertheless.

 

This happens in created fast missions, or missions I throw together in the ME.

 

I'm in the Hornet, easy communications are ON, the airport is set to BLUE, but all the ATC options are dark grey, i.e. unavailable as if they are not in range, and don't respond to any calls. Both when I'm on the ground at the airport, and in the air.

AWACS - works.

Flight - works.

Ground crew - works.

JTAC - works.

 

The radio also selects the correct channels (easy comms), it's just as if ATC (and ONLY ATC) is on strike...

 

[MAXsenna]

Which keybind are you using?

Sent from my MAR-LX1A using Tapatalk

[PrimetimeCasual]

General -> Open Communications Menu

[MAXsenna]

General -> Open Communications Menu

Right, that only works on the ground. In the air you have to use the radio(s). Comm1 and Comm2.
Cheers!

Sent from my MAR-LX1A using Tapatalk

[PrimetimeCasual]

vor 1 Stunde schrieb MAXsenna:

Right, that only works on the ground. In the air you have to use the radio(s). Comm1 and Comm2.
Cheers!

Sent from my MAR-LX1A using Tapatalk

 

I actually didn't know that, thank you.

I thought comms menu was comms menu, no matter where, for "easy communications". Guess I'll do the switch properly then and disable easy mode.

[AvgWhiteGuy]

Lost COMMS & COMMS Menu  - All Aircraft
Updated to latest version last week, all seemed good.
Yesterday lost all COMMS menu but had made NO changes.
Keyboard ' \ ' (Open COMS Menu) does nothing
Warthog HOTAS does nothing
OrbWeaver Keyboard mapping does nothing.
Batumi BLUE, No Ground Crew, No ATC
Voice Attk-Viacom recognizes commands...but something about 'nobody available'

@Primetime Casual...sound similar...everybody on strike or in the <profanity>ter?

Anybody got an idea...please

@Moderator...sorry about <profanity> but it is a US Military term, along with FUBAR

[Trigati]

Lost COMMS & COMMS Menu  - All Aircraft
Updated to latest version last week, all seemed good.
Yesterday lost all COMMS menu but had made NO changes.
Keyboard ' \ ' (Open COMS Menu) does nothing
Warthog HOTAS does nothing
OrbWeaver Keyboard mapping does nothing.
Batumi BLUE, No Ground Crew, No ATC
Voice Attk-Viacom recognizes commands...but something about 'nobody available'
@Primetime Casual...sound similar...everybody on strike or in the ter?
Anybody got an idea...please
@Moderator...sorry about but it is a US Military term, along with FUBAR

You are probably using the old Viacom Pro which is not compatible with 2.8
At least that’s what your symptoms sound like.

Find more info and help here https://discord.gg/adnyEnP4


Sent from my iPhone using Tapatalk

[MAXsenna]

Lost COMMS & COMMS Menu  - All Aircraft
Updated to latest version last week, all seemed good.
Yesterday lost all COMMS menu but had made NO changes.
Keyboard ' \ ' (Open COMS Menu) does nothing
Warthog HOTAS does nothing
OrbWeaver Keyboard mapping does nothing.
Batumi BLUE, No Ground Crew, No ATC
Voice Attk-Viacom recognizes commands...but something about 'nobody available'
@Primetime Casual...sound similar...everybody on strike or in the ter?
Anybody got an idea...please
@Moderator...sorry about but it is a US Military term, along with FUBAR

Post in the VAICOM sub forum and we'll sort you out. Make sure you use the latest community update of VAICOM, and you haven't hidden the comms menu under the preferences tab in the control panel.
Cheers!

Sent from my MAR-LX1A using Tapatalk

[AvgWhiteGuy]

@MAXsenna.....In the meanwhile, can I retreat to the last 2.7xxxx Beta version?

[MAXsenna]

@MAXsenna.....In the meanwhile, can I retreat to the last 2.7xxxx Beta version?

Yes, the last official VAICOM version supports DCS 2.7
Only the community version supports DCS 2.8, but not 2.7
Cheers!


Sent from my MAR-LX1A using Tapatalk