reported Randomly unable to contact the ground crew or anyone on radio?

[jubuttib]

Just wondering if anyone else has run into this behavior so far. I'm on the MT client, haven't started trying to replicate this consistently yet so no tracks yet, an early inquiry basically.

Sometimes during a mission I just randomly seem to lose my ability to contact anyone via the radio menu system, including ground crew. Even if initially I am able to contact the ATC for startup, I might not be able to ask them for taxi or takeoff after I finish the startup.

And by "not able to contact" I don't mean like I have the wrong frequency or the cockpit is closed for the ground crew, I mean that selecting the options in the menu doesn't do anything, not even trigger my pilot's line.

Today for example I landed after exhausting all my munitions, taxi'd to parking, opened my cockpit and asked the ground crew to refuel and rearm me. Usually I'd hear the "requesting refueling" and "requesting rearming" lines, which the ground crew either copies or says they're "unable to comply", but I don't get anything, just silence. Same when trying to contact ATC or AWACS, my pilot stays silent and there's no response either.

This doesn't happen always, and never at mission start (I have so far always been able to at least contact the ground crew enough to rearm and take off the wheel chocks), but sometimes between a few minutes or even an hour I just lose the ability to communicate.

Anyone else run into similar issues?

[Pyrocumulous]

I have been seeing this as well. I often entirely lose Comm2, but can use Comm1 for the same frequencies. I believe I am able to trigger this failure by calling Ground Crew before radio traffic is complete. For example, requesting permission to Start Up and then immediately requesting ground crew to remove wheel chocks.

[Pyrocumulous]

Attached is a quick demonstration of this bug: make call to ATC, while that conversation is occurring, make ground support call. This will break whichever radio was used for the duration of the mission. You will not be able to hear your transmission, nor the response, and nothing actually occurs (that is: it's not just missing audio).

av8b-comm_break.trk

[Aurora juutilainen]

Having the same issue, unable to contact ground crew more than once. After the first time the comms menu does not show up

[Bobstar]

1 hour ago, Aurora juutilainen said:

Having the same issue, unable to contact ground crew more than once. After the first time the comms menu does not show up

Same....

[SkidmarkOneOne]

So when I start up a Harrier on any server, if I am really fast, I can access the Comms menu one time, but after that, never again.  I've tried verifying and doing a repair on the files, that did not change anything.  I then tried to rebind the key to various other keys on my keyboard, then onto my Winwing throttle, that also did not help.

This is not an intermittent bug, it's constant and recent.  

[Flappie]

Have you ever used VAICOM pro on your PC?

Please attach your Export.lua script (from Saved Games/DCS.../Scripts) and your dcs.log (from Saved Games/DCS.../Logs).

[SkidmarkOneOne]

I don't know what VIACOM is, so no?

 

How do I attach these scripts?

[zildac]

I've just come across the same issue on the new TTI Sinai map in the AV8. It's the first time I’ve flown the Harrier since the most recent patch and there is definitely something up with the comms menu. It'll display one time, and then it's somewhat random whether it can be called up again. This was not an issue prior to the most recent OB (am also using MT).

Never used VIACOMExport.lua

dcs.log

Edited June 12, 2023 by zildac

[Sprool]

Same issue here, in MP servers you can only contact the ground crew once, then the comms menu fails to come up. This is regardless of if the plane is running or cold, cnopy open or closed, radios on any frequency. Just since the last update.

In SP or quickstart its not an issue, which may point the problem towards having easy comms switched off in most MP servers?

[Sprool]

Aided by my fellow expert i found the bug disappears when you press L Ctrl and Num + , or L Ctrl and Num - to switch fom fwd to aft radio comms. It brings up the comms menu again.

[Gunnar81]

23 hours ago, Sprool said:

Aided by my fellow expert i found the bug disappears when you press L Ctrl and Num + , or L Ctrl and Num - to switch fom fwd to aft radio comms. It brings up the comms menu again.

This affects all comms from what I can tell and not just contacting the ground crew. Even trying to bring up Comm 1 often requires toggling Comm 2 to get Comm 1 to come up as a menu. Hopefully this will get reported as a Bug and will get sorted out ASAP.

[Armageddon666]

Hello. I was having a similar bug after I updated to open beta 2.8.6.41066. I found myself unable to invoke the communication menu at some time in game. I found out that each time I go to the F10 map then back to the cockpit, the communication menu cannot be invoked anymore. This seems to happen only with the Harrier module.

[Gunnar81]

7 minutes ago, Armageddon666 said:

Hello. I was having a similar bug after I updated to open beta 2.8.6.41066. I found myself unable to invoke the communication menu at some time in game. I found out that each time I go to the F10 map then back to the cockpit, the communication menu cannot be invoked anymore. This seems to happen only with the Harrier module.

@AlphaJuliet Can we get this investigated into and/or relayed to Raz?

Thx.

[Flappie]

On 6/12/2023 at 9:49 AM, SkidmarkOneOne said:

How do I attach these scripts?

Click the "choose files..." link down below.

[Flappie]

I see you're not the only ones reporting this. Here's a thread from RAZBAM subsection:

 

[71st_Mastiff]

The A10A same issue, it seems the coms will react intermittently. Might effect all models across the board 

[wess24m]

same here, I think this qualifies as a bug.

[WipeUout]

Same problem here, comm menu showing on the first key/button press but not showing after.

[FusRoPotato]

I can get the menu to show again by hitting com1 PTT, but in order to get it to show again, I have to hit com2 PTT. Basically alternate back and forth to open the comms menu. Weird bug, perhaps there is something wrong in the control commands file like an overlapping definition.

[Special K]

Can any of you guys provide a dcs.log of such an incident please?

I'd like to see if any error is logged. If you can create one with debug logging enabled, that would be appreciated.

[Auntystatic]

I can recreate this on severs and in ME with normal comms switched on, seems to work fine with easy comms switched on

[zildac]

I posted a DCS.log here, same issue:

 

[zildac]

On 6/13/2023 at 11:11 PM, Flappie said:

I see you're not the only ones reporting this. Here's a thread from RAZBAM subsection:

 

Yeah. I need to test if the issue is isolated to the AV8 only, not had time as yet.

 

Update:

OK, so this isn't a problem in the Hornet. In the AV8 once you select radio (COM1 or COM2) you cannot call up the radio menu for that same radio UNLESS you pull up the menu for the other radio. For example: Select COM1 -> Request Taxi from menu - COM1 radio menu will not display again unless you pull up the COM2 radio menu,  then try COM1 radio menu again and the COM1 menu will display. Something is most definitely broken. I have only tested the AV8 and Hornet and as mentioned the issue is not present in the Hornet. Latest OB and MT.

Edited June 15, 2023 by zildac

[zildac]

OK, so this isn't a problem in the Hornet. In the AV8 once you select radio (COM1 or COM2) you cannot call up the radio menu for that same radio UNLESS you pull up the menu for the other radio. For example: Select COM1 -> Request Taxi from menu - COM1 radio menu will not display again unless you pull up the COM2 radio menu,  then try COM1 radio menu again and the COM1 menu will display. Something is most definitely broken. I have only tested the AV8 and Hornet and as mentioned the issue is not present in the Hornet. Latest OB and MT.